Re: [OpenWrt-Devel] should syslog-ng[3] terminate build-in syslog?
* Brian J. Murrell br...@interlinx.bc.ca [31.12.2012 14:39]: On 12-12-29 05:23 AM, Daniel A. Nagy wrote: Interesting perspective. The reason it seemed so important here to shut it down was because I had configured it to forward to a syslog server here and then also configured syslog-ng3 to do the same. Of course that was not a good situation. 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. and a hook with /etc/init.d/syslog stop should run in preinstall. 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 bye, bastian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] should syslog-ng[3] terminate build-in syslog?
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
Re: [OpenWrt-Devel] should syslog-ng[3] terminate build-in syslog?
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
Re: [OpenWrt-Devel] should syslog-ng[3] terminate build-in syslog?
* Brian J. Murrell br...@interlinx.bc.ca [31.12.2012 16:38]: 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. oops, you misunderstood me: like Jonathan i propose to move the logger call to an rc-file /etc/init.d/logger (or syslog?) which both packages (base-files + syslogd-ng3) have to supply. during preinstall we must do an 'stop' and we are fine... what about klogd? bye, bastian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] should syslog-ng[3] terminate build-in syslog?
On 12-12-31 10:44 AM, Bastian Bittorf wrote: oops, you misunderstood me: like Jonathan i propose to move the logger call to an rc-file /etc/init.d/logger (or syslog?) which both packages (base-files + syslogd-ng3) have to supply. I think I get your meaning. However you cannot have a supplemental package, like syslog-ng3 provide the same file as a base package. If that happens the supplemental package will refuse to install due to overwriting an file provided by a different package and you wouldn't want to remove the base package to get the supplemental package installed. Therefore each package has to install it's own /etc/init.d/ file, with the supplemental package possibly/probably disabling the /etc/init.d/base-logger startup script. The thing about such an approach though is that the naive user, seeing a startup script has been disabled might think he should enable it. what about klogd? Indeed. b. signature.asc Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] should syslog-ng[3] terminate build-in syslog?
On 12-12-29 05:23 AM, Daniel A. Nagy wrote: Hi Brian, Hi Daniel! The builtin syslogd logs to a circular buffer in RAM. It is fairly failsafe and does not take up many resources. I think that the current behavior of leaving it running upon installation of more heavyweight syslog services is correct behavior. Interesting perspective. The reason it seemed so important here to shut it down was because I had configured it to forward to a syslog server here and then also configured syslog-ng3 to do the same. Of course that was not a good situation. But indeed, simply reverting the configuration of having the built-in syslogd log to the syslog server serves my purposes as well. But what about slurping up the kernel messages, (i.e. /proc/kmesg)? Can the built-in syslogd/klogd and syslog-ng3 both read from those or will it be racy with the first reader consuming them and the second reader not getting any? 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
