[Buildroot] [PATCH v3 0/8] init scripts: rewrite S01logging

Thomas Petazzoni thomas.petazzoni at bootlin.com
Sat Nov 3 10:44:16 UTC 2018


On Fri, 2 Nov 2018 23:30:10 +0100, Arnout Vandecappelle wrote:

> > To me, this is exactly like what happens if you enable both Dropbear
> > and OpenSSH. It installs two init scripts with different names, even if
> > in practice, only one SSH server will start. We don't handle this
> > "conflict" for the SSH servers, I don't see why we should have some
> > special thing to handle it for logging daemons.  
>  There is one big difference with the HTTP daemon, however: even if busybox
> httpd is enabled, we don't install an init script for it. However, S01logging is
> installed unconditionally, even if the user didn't consciously choose for
> busybox as its logging provider.

Well, my point was not simply for Busybox HTTP server, but for HTTP
servers in general. We have S50apache and S50lighttpd for example, and
possibly others as well. We have S50dropbear and S50sshd.

So the problem doesn't exist today for the Busybox HTTP server, because
we don't have an init script for it (but we may add one at some point
in the future). But it already exists for tons of other

>  In that sense, it does make sense to offer an option to choose between the
> logging providers.

No, see above :-)

>  However, as I mentioned before, I see this as completely orthogonal to the
> S01logging cleanup, because this series is in fact mostly about standardizing
> the format of the init scripts. So Carlos, if you prefer to keep it as
> S01logging, that's fine.

On this, I totally agree, it is independent from Carlos work.

Best regards,

Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering

More information about the buildroot mailing list