On Wed, 2005-08-03 at 03:07 +0100, Andrew Stribblehill wrote: > > > wompom:/tmp# dpkg --remove xprint xprint-common > > > (Reading database ... 108631 files and directories currently installed.) > > > Removing xprint ... > > > Stopping Xprint servers: Xprt. > > > Removing xprint-common ... > > > Stopping Xprint servers: Xprt.
wompom:/tmp# find /etc -name '*xprint*' > /etc/X11/Xsession.d/92xprint-xpserverlist > /etc/init.d/xprint > /etc/default/xprint > /etc/rc0.d/K20xprint > /etc/rc1.d/K20xprint > /etc/rc2.d/S20xprint > /etc/rc3.d/S20xprint > /etc/rc4.d/S20xprint > /etc/rc5.d/S20xprint > /etc/rc6.d/K20xprint There are several facets to the problem. update-rc.d will not remove the symlinks if /etc/init.d/<script> is still present (the message appears at boot time because of the symlinks). But the init script is not removed by dpkg --remove, since it is a config file (--purge will clear everything up). debhelper colludes with this policy by not bothering to run update-rc.d in the postrm anyway on "remove", it only does it on "purge". > > > wompom:/tmp# /etc/init.d/xprint start > > > Starting Xprint servers: Xprt. > > > /etc/init.d/xprint: ## ERROR: Can't find "/usr/X11R6/bin/Xprt". > > > This is upstream's desired behaviour when the initscript is run with no binary present. That's the "|| exit 0" is not as straightforward as it might otherwise have been. I think the alternatives are 1) ignore upstream's design of the initscript and find a way of applying something like "$binary || exit 0" 2) Run "update-rc.d -f remove" for "remove" in postrm. This forces the symlinks to be gone, but might conflict with the idea of preserving config files. Do symlinks in /etc count as config files? I guess they must. I guess 1) is the better alternative for Debian. We can expect our own usual behaviour from initscript, unless upstream has a strong reason not to. I think in this case the error message is just a warning for an admin trying to start Xprint without the Xprt binary actually present. We deal with this in Debian by using Depends:. Drew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
