On Mon, Sep 07, 2009 at 01:44:03PM -0300, Henrique de Moraes Holschuh wrote: > > Yeah, I know that. And that is okay. However if it does not start a > > service (for whatever reason) it should say WHY. It does so for > > Well, I am not oposed to that at all, it would be useful to add a "verbose" > or even better, a very verbose "debug" mode to invoke-rc.d.
I'm not sure this is required. Actually invoke-rc.d has a --quiet switch which is described as "Quiet mode, no error messages are generated.". Actually this could get enhanced as "no error/warning" messages are generated and printing warning on such problems would become the default. After all I think that is wanted. But an additional --debug option would probably not bad either. > > Well, because I need to test somehow why it isn't starting a service from a > > maintainer script. As already said: An invoke-rc.d that basically does > > I am also not opposed to adding just the message you wanted as a quick fix > for the lack of a debug mode. Care to send a patch to this bug report? Actually, no. When I had a quick look at the script I haven't found the place where it failed. I really don't want to spend more time in debugging a shell script then neccessary. Sorry. Thanks anyway, Best Regards Patrick -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
