I've distfiles on a glusterfs server and is mounted to save bandwidth during regular updates. As part of regular maintenance after a @world update I restart the services (via app-admin/restart-services). After upgrading to =sys-fs/udev-init-scripts-33 this causes random process killing (most notably syslog-ng and sshd).
How to reproduce:
restart-services (restarts udev)
Connection to ssh.example.com closed by remote host.
Connection to ssh.example.com closed.
The killing combination is =sys-fs/udev-init-scripts-33 with sys-fs/udev
=sys-fs/udev-init-scripts-32 with sys-fs/udev = OK
=sys-fs/udev-init-scripts-3 with sys-fs/eudev = OK
I saw the same behavior where sshd died when unmounting an NFS filesystem. It is no longer an issue after downgrading to sys-fs/udev-init-scripts-32.
I "resolved" it by migrating to eudev. Now even udev-init-scripts-33 works fine.
This has been plaguing me since Feb as well and I just found this bug. I can't give proof positive it is fixed, but I can say that it only seemed to happen on machines that were old enough the udev was still the default when they were installed. My newer hardware runs eudev and none of them had issues.
Most of mine manifested in ways like
- random lvmetad crashes
- sshd would crash when (among other things) mounting filesystems. This was particularly painful on headless machines.
Thanks Tomáš for the fix/workaround!