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.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
