Control: tags -1 + confirmed
Hello!
Looking at this from a new upstream release perspective we have
some changed cicumstances...
First off, the library no longer autostarts uuidd:
commit ea4f8845f0241c714f9487ece5bb6900fc18a9e0
Author: Petr Uzel <petr.u...@suse.cz>
Date: Thu May 3 21:01:59 2012 +0200
libuuid: don't exec uuidd
Executing the daemon from the shared library is not quite elegant
solution. Drop this functionality and require uuidd (should it be
needed) to be started from the initscript or by socket-activation.
References: http://www.spinics.net/lists/util-linux-ng/msg05967.html
Which was first included in upstream release v2.22.
Also, the uuidd became socket activated through using systemd:
commit 1b68c37927c193d10195b7f1ba03f9b6e3ff389e
Author: Petr Uzel <petr.u...@suse.cz>
Date: Thu May 3 21:01:58 2012 +0200
uuidd: add systemd unit files
Add systemd unit files which use the socket activation mechanism
of systemd. The uuidd deamon is started upon first request on the
socket and quits after 1 minute of inactivity.
(With an additional series of followup commits to improve the
systemd unit files.)
This was also shipped in upstream release v2.22.
The solution would be to ship the uuidd sysvinit script which
would give a way to start the uuidd.
This script creates the directory as needed.
(Note: this script is already available in the current v2.20.1.
See "misc-utils/uuidd.rc". The script is just not shipped in
the current package.)
Additionally after upgrading util-linux to >= v2.22,
shipping the systemd unit files (which then masks
out the sysvinit script) to use socket-activation for
those who run systemd init.
Regards,
Andreas Henriksson
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
