I think the 'sanest' way to do this would be to have a /etc/init.d/logger script start the logger instead of /etc/init.d/boot and having the install script for whatever syslog package gets added later on do: '/etc/init.d/logger disable'
That's a core architecture change of course, but not much bigger than adding the check suggested below. On 31/12/12 09:36 AM, Brian J. Murrell wrote: > On 12-12-31 09:12 AM, Bastian Bittorf wrote: >> the best way to solve this problem is IMHO to >> write an startup-script for both and delete it from "/etc/init.d/boot" >> so the "busybox"-logger simply gets overwritten when you install >> "syslog-ng3". > So are you proposing that the syslog-ng3 post-install script edit > /etc/init.d/boot? IMHO, that's a no-no. One given package should not > touch another package's files. > > Surely it would be better to simply have a "switch" in the > /etc/init.d/boot script that would check for the presence of a superior > syslogd and packages like syslog-ng3 would set the switch to announce > that a superior syslogd is installed so the syslogd that > /etc/init.d/boot starts won't be started. > >> I'm unsure if the call in "/etc/init.d/rcS" it tooo hardcoded: >> >> # [ -x /usr/bin/logger ] && LOGGER="logger -s -p 6 -t sysinit" > Yeah, that should be more along the lines of: > > [ -x /usr/bin/logger ] && [ ! -f /etc/superior_syslogger ] \ > LOGGER="logger -s -p 6 -t sysinit" > > Where syslog-ng3 (and any other syslogger package) has the file > "/etc/superior_logger" in it's manifest. > > Cheers, > b. > > > > > _______________________________________________ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
