Results 1 to 40 of 187

Thread: Automated primality testing with LLRnet for CRUS

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Target Butt IronBits's Avatar
    Join Date
    Dec 2001
    Location
    Morrisville, NC
    Posts
    8,619
    LLRnet-CRUS current status :
    Sleeping ...
    LLR network client 0.9b7 started
    Based on LLR version 3.5.0
    Loading library 'win32' ...
    winloop thread
    LLRMain started
    server dialog thread started ...

    I guess that's what you mean

  2. #2
    Target Butt IronBits's Avatar
    Join Date
    Dec 2001
    Location
    Morrisville, NC
    Posts
    8,619
    What does this mean?

    LLRnet-CRUS1 current status :
    Initializing ...
    LLR network client 0.9b7 started
    Based on LLR version 3.5.0
    Loading library 'win32' ...
    winloop thread
    LLRMain started
    server dialog thread started ...
    StartServiceCtrlDispatcher returns 0

  3. #3
    Free-DC's Prime Search
    Join Date
    Apr 2004
    Posts
    2,518
    I suggest to move all cores to port 300. I really don't know what's going on on port 100. That's the only server that is down at the moment.

    Sorry.

  4. #4
    Free-DC's Prime Search
    Join Date
    Apr 2004
    Posts
    2,518
    Everything back to normal, don't ask me what happened...

  5. #5
    So are we to use 100 or 300 for the rally?
    -:Beyond:-


  6. #6
    Free-DC's Prime Search
    Join Date
    Apr 2004
    Posts
    2,518
    Quote Originally Posted by Beyond View Post
    So are we to use 100 or 300 for the rally?
    100.
    llrserver has a memory leak so I need often to restart the servers. I forgot to do it last night.

  7. #7
    100 then.
    -:Beyond:-


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •