-   Debian (
-   -   invoke-rc.d daemon start does not do anything (

Menestrel 01-20-2006 10:15 AM

invoke-rc.d daemon start does not do anything
Whenever I do a: invoke-rc.d <insert init.d script here> start, nothing happens, but if I do a /etc/init.d/<insert init.d script here> start it works (the daemon is started)

However invoke-rc.d <insert init.d script here> stop works ...

I am using Debian Woody(the same problem occured on Debian Sarge)
Any help would be appreciated ...

SuSE 1983. 01-20-2006 02:21 PM

when u do invoke-rc.d <insert init.d script here> start, what does it tell you?!

Menestrel 01-23-2006 04:43 PM

just nothing, it just returns me to the bash prompt :(

SuSE 1983. 01-25-2006 01:03 PM


Originally Posted by Menestrel
just nothing, it just returns me to the bash prompt :(

And you are sure that it does nothing?
Im not expert but I would say that it works - because it just returns you to bash prompt!

Jelle 01-25-2006 01:24 PM

It is just a shellscript, you can read (and debug) it yourself. Are there symlinks in the rc directories pointing to it. If not It might not want to start. Failing silently still puzzles me a bit though, what does the return value contain?

Menestrel 01-25-2006 06:30 PM

Now, it does not work, it should say something like start dameon instead of returning me to the prompt. Here is an example, by taking a random daemon:

# invoke-rc.d apache2 stop
Stopping web server: Apache2.
# invoke-rc.d apache2 start
# /etc/init.d/apache2 start
Starting web server: Apache2.

So, maybe there is something wrong with invoke-rc.d, but I don't know who to debug it, nor do I know how to find out the return variable..., please guide me: I tried running a command like: y = `invoke-rc.d apache2 start` then echo $y and $y does not contain any value, but that probabbly isn't the way to find out the return value :scratch:

Jelle 01-26-2006 11:25 AM

Oh, Y see. You get the return value by inspecting the special shell variable '$?' directly after the command. I skimmed the file yesterday and it might be the case that there the script you are trying to start is not configured to start in the runlevel you are in (probably 3).

By the way: personally I don't see much point in giving an executable long name with dashes and dots, so usually I start the daemons from /etc/init.d directly. I am not being itched enough by it though, otherwise a smal shellscritp called 'service' would have found it's way on my system.

All times are GMT -5. The time now is 11:11 PM.