Process start up order

[steve4586]

Hi all,

I need to start a process (MusicIP) before my Squeezecenter. I have run update-rc.d on the startup script, but it is prefixed with "S20" which is the same as Squeezecenter.

will the MusicIP script (S20mmserver) run before S20Squeezecenter? Or does the MusicIP script need to be run with say S19mmserver, if so how do I do this?

Also, how do I know one process has started before another?

Sorry, but I am struggling with this!!

Many thanks

Steve

[razrlazr]

Re: Process start up order

I believe the spacing is to allow for other scripts to be inserted, renamed, etc. for timing purposes. The directory rc5.d contains links to the real script file in the directory init.d. As root or sudo you should be able to rename the script in rc5.d to a number (S19 would work) lower than the S number of the script that is to follow.

Hope this helps.

[steve4586]

Re: Process start up order

Thanks for the info. I thought it might be as simple as this, but I wasn't sure if I could just edit it.

Many thanks

[jankushka]

Re: Process start up order

will the MusicIP script (S20mmserver) run before S20Squeezecenter?

as it stands...no.
S20Squeezecenter will run before S20mmerver.
in asciibetical order, upper case "S" comes before lower case "m".

Or does the MusicIP script need to be run with say S19mmserver, if so how do I do this?

the simplest way is to turn "S" to lower case (i.e. S20squeezecenter).
you'll then get what you want, 'cause lower case "s" comes after lower case "m".
for consistency, you should do this in all rc?.d directories.
although ubuntu systems work at run level 2.
so the directory you should really worry about is actually rc2.d.

Also, how do I know one process has started before another?

well, this used to be very easy back at the time of plain sysvinit.
back then, it was sufficient to enable the boot process logging (in /etc/default/bootlogd).
sysvinit is being replaced by upstart.
we shall not comment on how long this is taking...
anyway, ttbomk, boot logging still doesn't work.

there is a way of setting up the boot process log.
but it's pretty complex.
i've found this, if you really want to have a go.

hth