I just started running a recent build of mprime on a couple of linux systems, and noted an anomaly vis a vis primenet...
When mprime connects to primenet, its not updating date on the rest of the worktodo, only on the exponent actually in progress. case in point... 18665107 67 13.6 7.4 67.4 26-Mar-03 12:48 18-Mar-03 17:20 xeon1b 2790 v19/v20 18665149 66 13.6 17.4 74.4 18-Mar-03 17:20 xeon1b 2790 v19/v20 18665327 66 13.6 27.4 74.4 18-Mar-03 17:20 xeon1b 2790 v19/v20 18665333 66 13.6 38.4 74.4 18-Mar-03 17:20 xeon1b 2790 v19/v20 18665377 66 13.6 48.4 74.4 18-Mar-03 17:20 xeon1b 2790 v19/v20 18670741 66 13.3 48.7 74.7 18-Mar-03 23:20 xeon1b 2790 v19/v20 18763243 66 2.2 68.8 85.8 30-Mar-03 03:38 xeon1b 2790 v19/v20 I fired this client up on the 18th, and it downloaded the 60 days I told it to. its updated the exponent its working on on the 26th, and it checked out a new one on the 30th, but it hasn't updated the other values yet. I've tried using -c manually, it communicates, updates the WIP, but doesn't update the rest of the work*.ini file. -jrp _________________________________________________________________________ Unsubscribe & list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
