Michael Biebl <bi...@debian.org> wrote:
>> [2] Once, for a customer: inserting the right storage medium (with
>> the right UUID) triggered a system backup.
> Please don't do that. udev is a not a service manager and starting (long
> running) tasks from a udev rule is bad.
I wish someone would clue in Dell into that.
> See also the udev man page:
> Starting daemons or other long-running processes is not appropriate
> for udev; the forked processes, detached or not, will be
> unconditionally killed after the event handling has finished.
Dell includes a udev-rule in its ISM-Packages for iDRAC like this:
,----
| # Dell USBNIC Device
| SUBSYSTEM=="usb", ATTR{idVendor}=="413c", ATTR{idProduct}=="a102",
ATTR{manufacturer}=="Dell(TM)", ACTION=="add", RUN+="/etc/init.d/dcismeng start
&"
`----
The idea is to start the iSM-Daemon once the idrac-usb-network device is
detected. But because of the problem you mention this fails horribly and
causes a 30 second delay during boot if used with systemd.
Urgh.
Grüße,
Sven.
--
Sigmentation fault. Core dumped.
