| Subject: Re: Files controling seti |
| From: raj@rijhwani.org (Raj Rijhwani) |
| Date: 07/01/2004, 12:38 |
On Monday, in article <kKnKb.38$dk6.51037@news.uswest.net>
Reply@here.not.email "AZ Woody" wrote:
I know I've seen references to files which you can place in the seti dirs
which will allow things like "stop after uploading results", etc, but can't
seem to find a list...
I have a machine which is running a linux-ramdisk version, and would like to
control a few actions - for example, so that I don't loose WIP when I need
to reboot...
As long as you back up the working directory before rebooting, and restore
it exactly as is to the ramdisk before starting the client you will lose
only the processing since the last checkpoint. If you kill the client
explicitly (default SIGTERM not SIGKILL) it will update those files, and
you lose nothing. I don't think you really gain anything by running on a
ramdisk. You'd be better off just running from a normal disk partition,
then you can reboot at will (since the reboot will first try to kill
all processes cleanly), and your progress file will be up to date.