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. -- Michael T. Babcock CTO, FibreSpeed
- Re: Ensuring only one svscan per directory T\.
- Re: Ensuring only one svscan per directory Paul Jarc
- Re: Ensuring only one svscan per directory Rob Mayoff
- Re: Ensuring only one svscan per directory Karsten W. Rohrbach
