Re: [Sks-devel] FHS patch

[Yaron M. Minsky]

Why can't one do the backgrounding from the init script?

Also, what does one need to do to fork something into the background,
exactly?  

y

On Sat, 2003-12-06 at 13:05, Dan Egli wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Yaron M. Minsky wrote:
> 
> | I like the idea of following the FHS, but I have some requests.  I'd
> | like it to be easy for someone to set up the old behavior, so that
> | people currently using SKS don't have to update their setups.  One way
> | of doing this would be to have a flag, say "-fhs", that enables the new
> | behavior.  Perhaps using the fhs should be the default, so people using
> | the old system should be forced to add "-nofhs" to their list of
> | settings.
> |
> | The second thing is that this patch should include some modifications to
> | the README as well.
> |
> | All told, this looks like a good move.  SKS's setup has always been a
> | bit hacky.  Now the only thing left is to get some init scripts set up
> | and have the logging automated out of the box.  Actually, SKS already
> | does do a close/open cycle on SIGHUP, so it should be quite easy to set
> | up logrotate...
> |
> |
> 
> The other thing IMHO that would be nice is if sks would fork itself into
> the backgroun when using the db or recon paramaters. Even if I had to
> call it as sks db -fork or sks db -detach, it would be nice. Then I
> could setup some init scripts for sks rather than just having to call it
> from rc.local.
> 
> - --- Dan
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.2 (MingW32)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
> 
> iD8DBQE/0hpxtwT22Jak4/4RAigPAKCye4cxP87WoTuWMzf3Ppaxcxx4eQCgk+Cg
> U+vYkiJtc7Dt3bWbmuJKBGc=
> =vf1w
> -----END PGP SIGNATURE-----
-- 
|--------/            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