I'm not truly clear on whether my experiences are truly a result of
xprint or the underlying Debian facilities.
xprint has ended up on my debian machine from time to time, without ever
directly requesting the package. This is fine, and not xprint's
problem.
However, xprint as an unpleasant (to me) habit of launching, and
therefore using up RAM i would rather put towards other purposes -- I
don't really believe in paper, and haven't owned a printer for over a
decade. This too is reasonable, even if I do not love it.
However, after xprint has already been installed, and after I have shut
down the process, and after I have edited the launch symlinks so that it
should not be started:
Skonnos:/etc# ls -l rc?.d/*print*
lrwxrwxrwx 1 root root 16 2005-04-28 01:56 rc0.d/K20xprint ->
../init.d/xprint
lrwxrwxrwx 1 root root 16 2005-04-28 01:56 rc6.d/K20xprint ->
../init.d/xprint
Xprint still starts itself on upgrade, or on attempted package
reconfiguration.
I am fairly certain there should be a way that I can consistenty
indicate that I do not wish Xprint to be running. Additionally, I
believe this should be a standard method which is common to all debian
service packages.
I could be myopic in simply not finding this method, but this
return-of-the-upgraded-service experience has not been isolated to just
xprint, so I believe one of the following is true.
- There is a general facility for this and I'm too stupid to see it.
- There is a general facility for this and some packages (including
xprint) are not using it.
- There is no general facility for this.
Hopefully this is of some use in considering the start/stop issue.
-josh
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
