On Sun, Jan 08, 2017 at 03:59:44PM +0100, Andreas Metzler wrote:
> On 2013-08-14 Moritz Muehlenhoff <j...@debian.org> wrote:
> > Package: leafnode
> > Version: 1.11.8-3
> > Severity: normal
> > Tags: patch
> > User: pkg-systemd-maintain...@lists.alioth.debian.org
> > Usertags: systemd-units
>
> > Hi,
> > the attached patch leafnode-add-systemd.patch adds systemd support to
> > leafnode. It doesn't change anything for people using sysvinit!
>
> > When using systemd, leafnode is then started through systemd instead of
> > inetd.
>
> > The second patch leafnode-make-inetd-optional.patch demotes the dependency
> > on inetd towards a Recommends. For the default installation nothing changes,
> > but it allows people running systemd to remove inetd from their systems.
>
> > If you have any questions, please ask.
>
> Hello,
>
> with the patch leafnode is both started from by systemd and added to
> inetd.conf. - Won't this cause errors, when inetd tries to bind to nntp
> and fails because systemd is already listening?
Yes, that patch was a WIP and doesn't work properly (also why I didn'tp
apply it so far). I don't have time to work on this ATM; that's something
for buster.
> Also the leafnode package has some support for tcp wrappers (By default
> reject everything but 127.0.0.1). Wouldn't it make sense to either start
> leafnode via tcpd (as inetd does)
> ExecStart=@/usr/sbin/tcpd /usr/sbin/leafnode
> or either listen on localhost only by default?
I'd rather get rid of tcp wrappers entirely, the same restrictions can
be configured via the systemd unit as well.
Cheers,
Moritz
