Re: sarge apt and init daemons
In article [EMAIL PROTECTED], Phil Dyer [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Miquel van Smoorenburg said: If you want to keep updates from starting the daemon, just chmod 644 it. That sounds reasonable...and simple. :) thanks. Reasonable, simple, and wrong :) As long as one start or stop link is still present, update-rc.d will not change the configuration. So just remove all start/stop links except in, say, runlevel 5 or so. Since the default runlevel is 2, the service will not be started ever. OK, although both solutions work, (I guess - I haven't tried the second solution) it still seems kludgy to me. If I use the debian supplied tool to remove a service from startup _totally_, and I use a debian supplied tool to update the system, shouldn't the latter honor my current config? Nope. Because that is not how it works or has ever worked. Your expectation is skewed from reality (sorry). I don't think I should have to remeber to chmod this or fake out that. I have no problems doing either, it just seems odd that the best system update tool available can check to see if my conf files have been modified and let me choose whether to overwrite, but it doesn't check to see how I've configured services. It does. Mike. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge apt and init daemons
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Miquel van Smoorenburg said: OK, although both solutions work, (I guess - I haven't tried the second solution) it still seems kludgy to me. If I use the debian supplied tool to remove a service from startup _totally_, and I use a debian supplied tool to update the system, shouldn't the latter honor my current config? Nope. Because that is not how it works or has ever worked. Your expectation is skewed from reality (sorry). Hate to keep beating this. But my response is: Just because it's not how it's ever worked doesn't mean it's right. Can you give me reasoning as to *why* it works like that? Any docs you can point me to on this? My expectation, I guess, comes from other systems, like redhat, that won't turn on a service during an upgrade. Of course that was not perfect either, as I don't think up2date would restart the services you *were* running. I don't think I should have to remeber to chmod this or fake out that. I have no problems doing either, it just seems odd that the best system update tool available can check to see if my conf files have been modified and let me choose whether to overwrite, but it doesn't check to see how I've configured services. It does. It does... what? If it checked to see if I've turned off a service and prompted me for action, then I don't think I would have started this thread. :) Again, I'd just like some reasoning on this. - -- /phil -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (MingW32) Comment: Public Key: http://www.dyermaker.org/gpgkey iD8DBQFCeNNDGbd/rBLcaFwRAjTuAJ4pemYUBbKWHMpr2HOta5HBrD7pfACfRTHJ KY03OhAngJWTD7fbH14JKWA= =lejg -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge apt and init daemons
Phil Dyer wrote: Nope. Because that is not how it works or has ever worked. Your expectation is skewed from reality (sorry). Hate to keep beating this. But my response is: Just because it's not how it's ever worked doesn't mean it's right. Can you give me reasoning as to *why* it works like that? Any docs you can point me to on this? I'd also like to know the reason for this behavior. It seems to be that the most logical behavior would be: 1. On original install: debconf asks whether you want the services started. 2. On updates: if service is running, service is stopped, updates are performed, and service is restarted (i.e. current behavior) else debconf asks whether you want the services started (i.e. treat as original install) 3. On remove/purge: service is stopped before removing Is this not logical? Is there a reason that it doesn't work this way? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge apt and init daemons
/phil writes: It does... what? If it checked to see if I've turned off a service... It won't restart the service if you have left at least one K link in place. Debian provides several tools for turning services on and off. My favorite is sysvconfig (since I wrote it). -- John Hasler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge apt and init daemons
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 John Hasler said: It won't restart the service if you have left at least one K link in place. Debian provides several tools for turning services on and off. My favorite is sysvconfig (since I wrote it). thanks, John. I'm checking out sysvconfig now. - -- /phil -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (MingW32) Comment: Public Key: http://www.dyermaker.org/gpgkey iD8DBQFCePwUGbd/rBLcaFwRAs5KAJ9/mZEW3PMqwieADroByFn3WD+9/wCfSbnk /JvrkJB2Wm0uv4gyXmoDRoI= =8QSx -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge apt and init daemons
In article [EMAIL PROTECTED], Phil Dyer [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Clymer wrote: The debian post install script probably doest go through the rc.* directories looking for runlevel entries since these are all just symlinks to a script in /etc/init.d/. All that it probably checks for is that the /etc/init.d/whatever script exists and is executable. Then, on the assumption that its generally a good idea to stop and start daemons when upgrading them, it does so. I just think it would be a good idea to not start something that's not running anyway. Check to see if the proc is running and if it is, restart. In a lot of cases, the service is stopped in the preinst script, and (re-)started in the postinst script. So your suggestion doesn't work. If you want to keep updates from starting the daemon, just chmod 644 it. That sounds reasonable...and simple. :) thanks. Reasonable, simple, and wrong :) As long as one start or stop link is still present, update-rc.d will not change the configuration. So just remove all start/stop links except in, say, runlevel 5 or so. Since the default runlevel is 2, the service will not be started ever. Mike. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge apt and init daemons
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Miquel van Smoorenburg said: If you want to keep updates from starting the daemon, just chmod 644 it. That sounds reasonable...and simple. :) thanks. Reasonable, simple, and wrong :) As long as one start or stop link is still present, update-rc.d will not change the configuration. So just remove all start/stop links except in, say, runlevel 5 or so. Since the default runlevel is 2, the service will not be started ever. OK, although both solutions work, (I guess - I haven't tried the second solution) it still seems kludgy to me. If I use the debian supplied tool to remove a service from startup _totally_, and I use a debian supplied tool to update the system, shouldn't the latter honor my current config? I don't think I should have to remeber to chmod this or fake out that. I have no problems doing either, it just seems odd that the best system update tool available can check to see if my conf files have been modified and let me choose whether to overwrite, but it doesn't check to see how I've configured services. - -- /phil -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (MingW32) iD8DBQFCdtxZGbd/rBLcaFwRAjvyAJ9NXXuX3nLJD6PUsXYXMBX8lMin6ACfR+9u 7Xi1JV5IJdVNqiWwsDn6k6E= =f3dP -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
