Please have a look at the wikipage http://fedoraproject.org/wiki/FCNewInit/Initscripts and change your initscripts to comply with the LSB standard. Especially check the exit status and add a LSB Header. E.g. starting a service should return with 0, if the service is already running and stopping a stopped service should also return with 0. Also check, if your service has to be _on_ per default, and turn it off in the old chkconfig line, if not. Thank you.
Well, I would say that xttpd should be okay if /etc/rc.d/init.d/function is correct. Actually I use "daemon $DAEMON", "failure" "status $PROG" etc... So if I have to fix up xttpd, *FIRST* I need the documents what funtions in /etc/rc.d/init.d/functions return. Any documents which explain this?
(In reply to comment #1) > So if I have to fix up xttpd, *FIRST* I need the documents > what funtions in /etc/rc.d/init.d/functions return. I meant "I need the documents what status the functions in /etc/rc.d/init.d/functions return".
A quick look in /etc/rc.d/init.d/functions reveils: success() returns 0 failure() returns the last return code for status() and daemon() just look in /etc/rc.d/init.d/functions.. fairly easy to read.
Umm.. for me killproc() seems wrong. http://fedoraproject.org/wiki/FCNewInit/Initscripts says the following case must be considered as success: * running stop on a service already stopped or not running However, service {gpm,xttpd} stop when {gpm,xttpd} is stopped returns the message [FAILED], and the exit status is 0.... From the scripts, these only calls killproc() .
Once closing as INSUFFICIENT_DATA. Actually, more explanation of initscripts side function, new proposal to packaging committee, and the proposal of what _must_ fix and what _should_ fix... seems missing for now.