[Buildroot] [PATCH v4 3/4] sysklogd: rewrite init script
matthew.weber at rockwellcollins.com
Wed Nov 7 00:32:47 UTC 2018
On Tue, Nov 6, 2018 at 6:08 PM Arnout Vandecappelle <arnout at mind.be> wrote:
> On 05/11/18 15:07, Matthew Weber wrote:
> > So by default the user may take a busybox based target and get the
> > logging daemons from busybox's default config. Then they choose to go
> > enable one of the other logging options but don't understand they need
> > to make a custom busybox config. For sysklogd, the install would just
> > copy over the init scripts busybox installed, however do we need to
> > handle this case with rsyslog(S02klogd would be left in the target
> > from busybox) and syslog-ng(both S01/S02 would be left) ? Maybe a
> > check for existance and exit with warning that the busybox
> > configuration needs to have logging disabled....
> That is handled in busybox.mk:
> +# Only install our logging scripts if no other package does it.
> +ifeq ($(BR2_PACKAGE_SYSKLOGD)$(BR2_PACKAGE_RSYSLOG)$(BR2_PACKAGE_SYSLOG_NG),)
> define BUSYBOX_INSTALL_LOGGING_SCRIPT
Agree, just more of a "if you don't do a clean build" what questions
will hit the mailing list and how could we prevent that.....
More information about the buildroot