Re: How to prevent daemons from starting at boot after update?

2012-11-27 Thread Adrian Fita
On 09/11/12 03:04, Tom H wrote: On Thu, Nov 8, 2012 at 5:59 PM, Adrian Fita adrian.f...@gmail.com wrote: On 09/11/12 00:32, Tom H wrote: On Thu, Nov 8, 2012 at 5:18 PM, Adrian Fita adrian.f...@gmail.com wrote: So the thing is this: I have some daemons that I keep them installed, but I don't

Re: How to prevent daemons from starting at boot after update?

2012-11-27 Thread Michael Biebl
On 27.11.2012 20:52, Adrian Fita wrote: I just did a cups package update (yes, I'm running Debian unstable) and noticed that the cups daemon was started after the upgrade. And indeed, looking in /var/lib/dpkg/info/cups.postinst, the daemon is started with invoke-rc.d cups start after every

Re: How to prevent daemons from starting at boot after update?

2012-11-27 Thread Adrian Fita
On 27/11/12 23:19, Michael Biebl wrote: On 27.11.2012 20:52, Adrian Fita wrote: I just did a cups package update (yes, I'm running Debian unstable) and noticed that the cups daemon was started after the upgrade. And indeed, looking in /var/lib/dpkg/info/cups.postinst, the daemon is started

Re: How to prevent daemons from starting at boot after update?

2012-11-27 Thread Jon Dowland
One option would be to install and use systemd. Afaik with systemd, one can use socket-based activation: that is, systemd listens on the socket that your daemons will use and only starts those daemons if something connects. You may need to manually configure that behaviour, I don't know whether

Re: How to prevent daemons from starting at boot after update?

2012-11-27 Thread Adrian Fita
On 27/11/12 23:47, Adrian Fita wrote: On 27/11/12 23:19, Michael Biebl wrote: On 27.11.2012 20:52, Adrian Fita wrote: I just did a cups package update (yes, I'm running Debian unstable) and noticed that the cups daemon was started after the upgrade. And indeed, looking in

Re: How to prevent daemons from starting at boot after update?

2012-11-27 Thread Michael Biebl
On 27.11.2012 22:47, Adrian Fita wrote: - my current runlevel is 2, I made sure that cups is indeed disabled: /etc/rc2.d/K02cups What does ls -la /etc/rc?.d/???cups say? If you properly disable cups via update-rc.d, the service is not run via invoke-rc.d. I've just tested this on my system.

Re: How to prevent daemons from starting at boot after update?

2012-11-27 Thread Adrian Fita
On 28/11/12 00:16, Michael Biebl wrote: On 27.11.2012 22:47, Adrian Fita wrote: - my current runlevel is 2, I made sure that cups is indeed disabled: /etc/rc2.d/K02cups What does ls -la /etc/rc?.d/???cups say? root@zero:~# ls -la /etc/rc?.d/???cups lrwxrwxrwx 1 root root 14 Nov 9 01:06

Re: How to prevent daemons from starting at boot after update?

2012-11-27 Thread Michael Biebl
what does `runlevel` say? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature

Re: How to prevent daemons from starting at boot after update?

2012-11-27 Thread Adrian Fita
On 28/11/12 00:52, Michael Biebl wrote: what does `runlevel` say? root@zero:~# runlevel N 2 And the installed sysv-rc package info: root@zero:~# dpkg -s sysv-rc Package: sysv-rc Status: install ok installed Priority: required Section: admin Installed-Size: 218 Maintainer: Debian sysvinit

Re: How to prevent daemons from starting at boot after update?

2012-11-27 Thread Michael Biebl
On 27.11.2012 23:59, Adrian Fita wrote: On 28/11/12 00:52, Michael Biebl wrote: what does `runlevel` say? root@zero:~# runlevel N 2 Interesting. As already shown, I can't reproduce your problem. Not sure if this is because you ship a policy-rc.d script. It might help, moving that file

Re: How to prevent daemons from starting at boot after update?

2012-11-27 Thread Adrian Fita
On 28/11/12 01:06, Michael Biebl wrote: On 27.11.2012 23:59, Adrian Fita wrote: On 28/11/12 00:52, Michael Biebl wrote: what does `runlevel` say? root@zero:~# runlevel N 2 Interesting. As already shown, I can't reproduce your problem. Not sure if this is because you ship a policy-rc.d

Re: How to prevent daemons from starting at boot after update?

2012-11-27 Thread Michael Biebl
On 28.11.2012 00:22, Adrian Fita wrote: As soon as I reinstalled policyrcd-script-zg2, invoke-rc.d is starting the services again. So, is this expected behaviour, or is it a bug that I should report? I've never used policyrcd-script-zg2 and have no idea what this package is supposed to do,

How to prevent daemons from starting at boot after update?

2012-11-08 Thread Adrian Fita
So the thing is this: I have some daemons that I keep them installed, but I don't start them at boot; I like to conserve my memory resources and only start the daemons when I really need them. I have disabled them with update-rc.d -f remove, but every time I update their package, they are added

Re: How to prevent daemons from starting at boot after update?

2012-11-08 Thread Tom H
On Thu, Nov 8, 2012 at 5:18 PM, Adrian Fita adrian.f...@gmail.com wrote: So the thing is this: I have some daemons that I keep them installed, but I don't start them at boot; I like to conserve my memory resources and only start the daemons when I really need them. I have disabled them with

Re: How to prevent daemons from starting at boot after update?

2012-11-08 Thread Adrian Fita
On 09/11/12 00:32, Tom H wrote: On Thu, Nov 8, 2012 at 5:18 PM, Adrian Fita adrian.f...@gmail.com wrote: So the thing is this: I have some daemons that I keep them installed, but I don't start them at boot; I like to conserve my memory resources and only start the daemons when I really need

Re: How to prevent daemons from starting at boot after update?

2012-11-08 Thread Tom H
On Thu, Nov 8, 2012 at 5:59 PM, Adrian Fita adrian.f...@gmail.com wrote: On 09/11/12 00:32, Tom H wrote: On Thu, Nov 8, 2012 at 5:18 PM, Adrian Fita adrian.f...@gmail.com wrote: So the thing is this: I have some daemons that I keep them installed, but I don't start them at boot; I like to