On Thu, 14 Jul 2016 14:59:49 -0400, Lizhou Sha wrote:
> Hi Gregor,
Hi Lizhou,
and thanks again for your help!
> Indeed, socket activation would be nice. However, from my latest
> testing, the current packaged version of iodined has some bug wrt
> IPv6. Namely, systemd sockets are IPv6 by defau
Hi Gregor,
Indeed, socket activation would be nice. However, from my latest
testing, the current packaged version of iodined has some bug wrt
IPv6. Namely, systemd sockets are IPv6 by default, and on an IPv4-only
system, iodined will still think that the socket is IPv6. The upstream
master seems t
On Tue, 05 Jul 2016 17:52:07 -0400, Lizhou Sha wrote:
> Please find attached a systemd service file for iodined. This should
> serve as a drop-in replacement for the existing sysvinit script.
Thank you, much appreciated.
One question I (as a systemd noob) have is:
Shouldn't iodined use systemd's
Package: iodine
Version: 0.7.0-4
Severity: wishlist
Dear Maintainer,
Please find attached a systemd service file for iodined. This should
serve as a drop-in replacement for the existing sysvinit script.
A couple things to note:
- The original init script depends on $remote_fs, $named, and $sysl
4 matches
Mail list logo
