On Sat, 10 Aug 2013 10:33:48 -0400, Tanstaafl wrote: > > On 2013-08-09 7:12 AM, Tanstaafl <tansta...@libertytrek.org> wrote: > >> Last - is simply restarting udev good enough, or should I go ahead > >> and reboot anyway before continuing with other updates?
Restarting worked for me on a server. On my laptop I switched over at the same tome as a kernel update, so I had to reboot anyway. > > Never got a response to this... > > > > I'd prefer to not reboot if I don't have to, but it isn't *that* big a > > deal if it is 'recommended'... > > Two other related questions... > > 1. Would it be correct to say that if you don't get an error when > restarting udev, you *shouldn't* (I know there are never any > guarantees) get an error when rebooting? That sounds reasonable. I find checkrestart to be useful in these situations. If it reports everything OK, you will be fine. > and > > 2. What happens if I > > /etc/init.d/udev restart > > and there is an error of some kind? Find someone to blame, but not me ;-) > Will it cause my mail server to come crashing down? Or will it keep > running until I can determine the error and fix it? > > Keep in mind - this is a server, and just runs > postfix/dovecot/apache/mysql... I don't see it being a problem, but in that case, a reboot should clear things. Just make sure you have a package of udev available in case things do go TU. -- Neil Bothwick COMMAND: A suggestion made to a computer.
signature.asc
Description: PGP signature
