Re: [Sks-devel] DB Close semaphor

[Yaron M. Minsky]

I don't really see the point of this feature.  Sending sks a SIGINT
causes it to checkpoint the DB, close all files and exit.  it seems like
the right thing to do is:

1. use kill to stop the two sks processes
2. do your backup (or whatever)
3. start up the processes again.

Is there any problem with this sequence?

y 

On Wed, 2003-11-26 at 11:25, Dan Egli wrote:
> Yaron,
> 
>         Did you ever add that semaphor file I suggested? THe file that, if
> present, will cause sks db and sks recon to close the database,
> close any sockets they have open, and just go into a kind of a "do
> nothing" loop till the file is removed? That would seem to me to
> be the best way to make a backup of the database. You just touch
> the file, wait 30 seconds, cp the database elsewhere, then rm the
> file.
> 
> The problem otherwise is that it's virtually impossible to create an
> automated backup script that does not risk database corruption.
> 
> --- Dan
> 
> 
> 
> _______________________________________________
> Sks-devel mailing list
> address@hidden
> http://mail.nongnu.org/mailman/listinfo/sks-devel
-- 
|--------/            Yaron M. Minsky              \--------|
|--------\ http://www.cs.cornell.edu/home/yminsky/ /--------|

Open PGP --- KeyID B1FFD916
Fingerprint: 5BF6 83E1 0CE3 1043 95D8 F8D5 9F12 B3A9 B1FF D916