* 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
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
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
* 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
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
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
I have installed syslog-ng3, configured it and started it. I notice
that while it does seem to be doing the work of logging to my syslog
server, the old syslogd still seems to be running.
Should the installation and/or startup of syslog-ng[3] either prevent
the standard syslogd from running or
