Michael T. Babcock([EMAIL PROTECTED])@2001.06.04 11:11:59 +0000:
> We ran into a misconfiguration on one machine where svscan had been
> added by one person to rc.sysinit and inittab by another, so two copies
> of svscan were being started.
> 
> I realise that this is a misconfiguration, but wouldn't it be possible
> for svscan to add a 'lock' file to the services directory so it only
> starts once?  I'm not sure stale locks would be easy to detect since
> svscan is usually a very low-numbered PID.
hmm, the supervise implementation does locking, so at least the impact
on the box should not be really noticeable (in fact, you will see errors
from the supervises starteted from svscan).
adding locking to svscan would be more of a cosmetic change i think.
/k

-- 
> Captain Hook died of jock itch.
KR433/KR11-RIPE -- WebMonster Community Founder -- nGENn GmbH Senior Techie
http://www.webmonster.de/ -- ftp://ftp.webmonster.de/ -- http://www.ngenn.net/
karsten&rohrbach.de -- alpha&ngenn.net -- alpha&scene.org -- [EMAIL PROTECTED]
GnuPG 0x2964BF46 2001-03-15 42F9 9FFF 50D4 2F38 DBEE  DF22 3340 4F4E 2964 BF46

PGP signature

Reply via email to