Hi, something that bothers me a bit... More and more system restart requests with each update (even if one doesn't use the package at the time). Is this necessary for dhclient and dhcp update packages to require restart? Wouldn't "service network restart" and "service dhcpd restart" in the install/upgrade scripts do the trick (after checking that the service is actually running)? Ssh used to do that since, well, as far as I remember.

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkqWxw0ACgkQ5hsjjIy1VknDsgCfasl1AnpQ74vKT/ZTK8l2WU6b CUAAoMKxJloW1IEiRGIVC9lRPLUYW/+C =Kqzr -----END PGP SIGNATURE-----

Dariusz J. Garbowski wrote: > > Hi, something that bothers me a bit... More and more system restart > requests with each update (even if one doesn't use the package at the time). This is a real shame. One of the selling points of Linux is that you *don't* need to reboot for every little upgrade (unlike a certain other OS I shan't name).

But I explained in the previous reply how to cycle the interface using either the network service or NetworkManager. I still view this as something more technical users will be familiar with and for the average user, simply rebooting the system is the easiest method.

On Tue, Sep 1, 2009 at 5:07 PM, Matthew Woehlke&lt;mw_triad(a)users.sourceforge.net&gt; wrote: > No, the easiest method is: > > "The following updates require their respective services to be restarted > for the updates to take effect. <List of services.> Proceed? [Yes] [No]" I don't think it makes sense to treat everything that presently has an /etc/init.d script equally. For example, if cupsd has no queue, it's probably safe for it to just restart itself at some period of time. Probably the easiest way to implement this would be a flag in the init script which says whether it's safe to "service restart" on updates.

For other things, an important question is whether the currently running desktop depends on it. If it does, it's not safe to have such a UI.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 26 Aug 2009, Dariusz J. Garbowski wrote: > Hi, something that bothers me a bit... More and more system restart > requests with each update (even if one doesn't use the package at the > time). > > Is this necessary for dhclient and dhcp update packages to require > restart? > Wouldn't "service network restart" and "service dhcpd restart" in the > install/upgrade > scripts do the trick (after checking that the service is actually > running)? > Ssh used to do that since, well, as far as I remember. Yes, 'service dhcpd restart' will work fine for dhcpd. For dhclient, it's not necessarily as simple as restarting the network service. If you are using the network service, that will work fine. If you are using NetworkManager, you'll need to either restart NetworkManager or have it down the connection you're using dhclient on and bring it back up.

I think that the selling point is over-sold. It is true in many case for servers, but desktops are a much more interconnected system where updating something deep requires a lot of restarts.. and yes you could come up with a to probably deal with a good many of without a reboot... it is often faster to reboot the box than work out that you need to restart daemon-A then Y then Z and then A again

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 2 Sep 2009, Dennis J. wrote: > On 08/27/2009 07:49 PM, David Cantrell wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On Wed, 26 Aug 2009, Dariusz J. Garbowski wrote: >> >>> Hi, something that bothers me a bit... More and more system restart >>> requests with each update (even if one doesn't use the package at the >>> time). >>> >>> Is this necessary for dhclient and dhcp update packages to require >>> restart? >>> Wouldn't "service network restart" and "service dhcpd restart" in the >>> install/upgrade >>> scripts do the trick (after checking that the service is actually >>> running)? >>> Ssh used to do that since, well, as far as I remember. >> >> Yes, 'service dhcpd restart' will work fine for dhcpd. For dhclient, >> it's >> not necessarily as simple as restarting the network service. If you are >> using >> the network service, that will work fine. If you are using >> NetworkManager, >> you'll need to either restart NetworkManager or have it down the >> connection >> you're using dhclient on and bring it back up. > > Why is a restart of NetworkManager necessary in this case? If > dhclient reinitializes the interface and gets the old dhcp data then > nothing really changes and NetworkManager shouldn't have to care. If > e.g. der IP changes then NetworkManager should detect that and > reinitialize the connection info on its end (after all the "new" > interface might not be connected to anything and thus have to be > marked as down anyway). It doesn't work that way. dhclient isn't a service with an init.d script. If you are using NetworkManager, dhclient is a child process of NetworkManager. You can't just restart dhclient since NetworkManager is controlling it. You have to either tell NetworkManager to down the interface, stop dhclient, and bring it back up -- or restart NetworkManager. Either way, the result is the same. If you are using the network service, dhclient is run when the interface is ifup'ed (so either restart the network service or ifup/ifdown the interface in that case).

- -- David Cantrell <dcantrell(a)redhat.com&gt; Red Hat / Honolulu, HI