On Wed, 28 Jan 2015 at 17:37:38 -0800, Vagrant Cascadian wrote:
> When runnning dnsmasq with systemd on a freshly installed system,
> without dbus installed, dnsmasq fails to start. It seems like dnsmasq
> should depend or at least recommend dbus if it needs dbus in order to
> function on a default install with systemd. Some ugly chain of "dbus |
> sysvinit-core | upstart" might also be worth entertaining...
There are three ways this could potentially be fixed:
* depend on dbus or optionally dbus | sysvinit-core | upstart
(systemd will think dnsmasq is ready when it claims its bus name,
as it does now)
* change from Type=dbus to Type=forking, add PIDFile, and stop using
--keep-in-foreground in '/etc/init.d/dnsmasq systemd-exec'
(systemd will think the dnsmasq child process is ready when the
parent process exec'd by the init script exits 0, and will
determine what the child process is by reading the PIDFile)
* change from Type=dbus to Type=notify, link to libsystemd, and call
sd_notify(0, "READY=1") when ready
(systemd will think dnsmasq is ready when it does that)
I can put together a patch for one of these options if the
dnsmasq maintainer is too busy (the first two are easy, the third
is slightly harder but not rocket science), but I'd like to know
which one you'd prefer.
S
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
