Hi Lars and list members,
At 06:13 PM 11/24/98 +0100, Lars wrote:
>But sometimes it happened that mprime went mad
>due to the fact that it had to write intermediate files
>onto an nfs mounted remote disk, which sometimes
>failed because the network wasn't properly set up.
>It then tended to steal more cycles than would be expected
>from a 'nice' process (and didn't produce anything sensible anymore).
Are there any Linux experts that can clue me in on what
might have gone wrong and what code I would need to prevent
this in the future?
>I don't know if he was aware of this problem, but
>finally I had to obey because he insisted that
>his machine runs slower if mprime runs on it,
I'm sure Lars, a long-time GIMPS participant knows this, but others
might benefit:
The time between disk writes is adjustable, the default is
30 minutes. Lars was running mprime long before this was adjustable.
Version 17 now supports a Time= option in the prime.ini file.
This can be used to make mprime sleep during the work day. This might
be enough to convince an Administrator that mprime is safe.
If there are other ideas on how to make mprime or Prime95 less
intrusive please forward them to me by private email.
Regards,
George
