Re: Bug#357703: udev breaks syslog
On Tuesday 28 March 2006 18:15, Marco d'Itri wrote:
On Mar 28, Gabor Gombas <firstname.lastname@example.org> wrote:
How about restarting syslog (or it's equivalent) after relocating the
old /dev? glibc already has infrastructure for restarting services on
upgrade, maybe udev can borrow that.
Harder than it looks. There are multiple syslog daemons, how can the
package know which one is installed and needs to be restarted?
Look in /proc and find out which process has the log socket open? If that
process belongs to one of the packaged syslog implementations (there aren't
that many!) restart it.
That much is easy, but how do you turn a process ID into a script that
can be invoke-rc.d'd?
Well, I suppose one could hard code in a list of packaged syslog daemons
and the names of their init scripts, but that's pretty nasty.
IMO this is just foolishness caused by the hacks necessary to start udev
immediatly after the package has been installed, rather than after the
system is rebooted.
PGP key id 5EA01078
3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078