On Thu, 31 Mar 2005 18:23:15 +1000, Matthew Palmer wrote > On Thu, Mar 31, 2005 at 09:10:30AM +0200, Janos Holanyi wrote: > > Originally, php4-sqlite postinst gives false alarms which could be avoided: > > > > /usr/sbin/apachectl is not executable, exiting > > Restarting apache-ssl. > > That's not php4-sqlite producing those messages.
Practically, it is: if [ -x "/etc/init.d/$srv" ]; then if [ -x /usr/sbin/invoke-rc.d ]; then /usr/sbin/invoke-rc.d $srv restart else /etc/init.d/$srv restart fi fi # /etc/init.d/apache restart /usr/sbin/apachectl is not executable, exiting # ls -l /usr/sbin/apachectl ls: /usr/sbin/apachectl: No such file or directory > > The postinst script checks for executability of files in /etc/init.d/ but > > packages leave their files in there on package removal so it would be more > > proper to also check running instances before checking files in /etc/init.d > > to focus only on running servers to restart. > > No, it wouldn't be more proper. The restart action of an init > script is the only policy-guaranteed way of reloading the > configuration of a service, and it is not intended to only be run > when the service is already running. Is package removal (not --purge) not perfect then (leaving files around)? Regs Csani -- Open WebMail Project (http://openwebmail.org) Debian Project (http://www.debian.org) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]