-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, Jan 06, 2017 at 02:47:32AM +0100, Sven Hartge wrote:
> 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.
See below.
> 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:
Well, yeah. I simplified. The usual machinery to make sure the thing isn't
running already and to sneak out of the process group applies: this ain't
really new stuff in the Unix world, after all.
>
> ,----
> | # 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.
Had they written the "...start" as they should have, they wouldn't need
this funny "&" at the end anyway, right?
- -- t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlhvV30ACgkQBcgs9XrR2kbqmwCfYq0Jyd/S/JpywAasqQrTkneI
wWgAnAm0GOzdTIYUW0FOWD9MahrDGXu/
=6MJ7
-----END PGP SIGNATURE-----
