Re: endless loop at stage 2 of runit of run scripts of each service directories.

[Amrish Purohit <amrish.purohit@elitecore.com>]

[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]

Charlie Brady,
                      Thanks for  your kind suggestion.This help me a 
lot. i think this matter is not described in runit webpage.
currently i am working on runit to customize it on fedora. we should 
make effort for proper documentation so any one may not get any confusion.

Thanks again
Amrish Purohit
Charlie Brady wrote:
>
> On Mon, 11 Aug 2008, Amrish Purohit wrote:
>
>> here is the format of run script
>> ---------------------------------------
>> #!/bin/bash
>> exec /etc/rc.d/init.d/cpuspeed start
>
> Doing that will always get you into trouble. init.d scripts are always 
> designed to terminate quickly. That's exactly the opposite of what you 
> want. Any program which you exec from a supervise run script is 
> expected to keep running until you send it a signal asking for it to 
> stop.
>
> You will need to look through /etc/rc.d/init.d/cpuspeed and find out 
> what commands it calls, and find a way to call the same command in a 
> way where the command will not terminate (e.g. don't run it in the 
> background, or run it with an argument which tells it to run in the 
> foreground).
>
> [Try:
>
> exec /usr/sbin/cpuspeed
>
> Or just use a symlink to /usr/sbin/cpuspeed as your 
> /service/cpuspeed/run.
> ]
>

[-- Attachment #2: Type: text/plain, Size: 38 bytes --]

Scanned by Cyberoam AV Scanning Engine