Mark Haney wrote:
> Well, I just dug through my logs and all I see if an instance where
> udev was updated (July 6th in my case and I do updates on my systems
> about every day) and it looked like it tried to restart and failed
> to bind to the address since it was already in use. I don't see
> where it actually failed, but that's the only entry in my log files
> since I did the upgrade.
>
> Do you see anything similar in your logs?
I don't see any failure to start sort of messages in any logs under
/var/log. I do see something that seems oddly timed though.
# grep udev /var/log/messages
Jul 8 20:15:36 panaeolus yum: Installed: udev.i386 071-0.FC4.3
Jul 8 20:55:36 panaeolus yum: Installed: udev.i386 071-0.FC4.3
Jul 9 13:30:10 panaeolus yum: Updated: udev.i386 113-2.fc8
Jul 9 13:46:44 panaeolus yum: Updated: udev.i386 113-2.fc8
# grep udev /var/log/secure
Jul 8 20:34:44 panaeolus sudo: tmz : TTY=pts/3 ; PWD=/home/tmz ; USER=root ; COMMAND=/sbin/udevd --daemon
IIRC, those times correspond to when I built some packages in mock,
for FC4 and later for rawhide. It's probably just a coincidence,
since I only had to restart udevd once, while I did mock builds
several times. But I'll try to keep an eye on it if it fails again
and see if I've done the same thing then.
--
Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
It's the good girls who keep diaries; the bad girls never have the
time.
-- Tallulah Bankhead
Attachment:
pgpCB4GGUExBG.pgp
Description: PGP signature
