-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Simon.

Many thanks for the offer of help, not having to wade into the
intricacies of systemd is a big win for me.

The current arrangements are "something which was made to work without
big code changes" so I'm not wedded to using the dbus method at all,
and most installations of dnsmasq won't need dbus, so removing the
compulsory dependency is good. That eliminates option one.

Of two or three, I'm not sure and I'll take your advice. Two needs no
code changes and adds no dependencies, and that's good, but if there
are advantanges to going with three, then I can handle that by making
the libdbus code conditionally compiled.


Cheers,

Simon.




The current code is "Som

On 07/02/15 12:08, Simon McVittie wrote:
> 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
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJU2NJQAAoJEBXN2mrhkTWiQ2wP/3xrPZKauBip1lrQ+KMcoq+A
kcxyUkG7Culdmk+j6o1YXaqGGL10+hWc9Dc8Qf6keOQmSEwHcjpb/xhAYTk7TK0z
c//339hE+XhtQKMQRh3DlEx47NqAkAqI68/P9XaHmP7VDAmI/ngGmU4MubajW4NL
80D6Z2e0ej/wp3ks/vwcSzDtDg+Z7yI0wYPrGlmq2C2ke2NCpjzllLwPytVq22eM
VSHFxcwVERmiugIe456tMOAzt6Rhsi1rP+I+xDKwM+Pdo4f/Gw5ulS+DR4xc5maz
YQLFfwioGRyl95weltrLE96YKw4Ma/lF2BaXNne+cOYznbQHKGRkBegK05cN6eFQ
tYVa95IXw71/EJkfKQuVftIH7m4xoE/F/Q/Awa4qcVaH4LmzDK8xqVkUkKA73+UX
13kIl5gef3r9SEQoIOwUMiVefPT/uENMLded7C3DhlIX+0xtdI/IFiOQMJ5Momre
oqQ4ykKaa/P1fJxiGfkAfa716PK6oFvfeMYLFuPRCslJoJE5k/5Xpp74HymaSWjr
LlK04Q+t+EsjrWpuU7uGd+Vywb4QI/HOVO5onGyXo0cYiB+jpANvDzkG1sSvzAWx
rTXHYRcte4LkiJswuCOZeUsVXOvdICU4CGRsh4n3tC5y6CbsCT6vqSmKC+pRdFm5
i2THtdMze50+33HfIBZk
=OYQ2
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to