[PATCH] Cygwin: missing colon in default syslog-ng.conf
Hi, The Cygwin service installer script creates a version entry without a colon, which leads to warnings. The below patch fixes that. Please apply. Thanks, Corinna --- contrib/cygwin-packaging/syslog-ng-config.ORIG 2009-03-25 17:08:34.000000000 +0100 +++ contrib/cygwin-packaging/syslog-ng-config 2009-03-19 19:21:34.000000000 +0100 @@ -205,7 +205,7 @@ if [ ! -f "${SYSCONFDIR}/syslog-ng.conf" then echo "Creating default ${SYSCONFDIR}/syslog-ng.conf file" cat > ${SYSCONFDIR}/syslog-ng.conf << EOF -@version 3.0 +@version: 3.0 options { keep_hostname(yes); owner("system"); -- Corinna Vinschen Cygwin Project Co-Leader Red Hat
Ping? On Mar 25 17:09, Corinna Vinschen wrote:
Hi,
The Cygwin service installer script creates a version entry without a colon, which leads to warnings. The below patch fixes that. Please apply.
Thanks, Corinna
--- contrib/cygwin-packaging/syslog-ng-config.ORIG 2009-03-25 17:08:34.000000000 +0100 +++ contrib/cygwin-packaging/syslog-ng-config 2009-03-19 19:21:34.000000000 +0100 @@ -205,7 +205,7 @@ if [ ! -f "${SYSCONFDIR}/syslog-ng.conf" then echo "Creating default ${SYSCONFDIR}/syslog-ng.conf file" cat > ${SYSCONFDIR}/syslog-ng.conf << EOF -@version 3.0 +@version: 3.0 options { keep_hostname(yes); owner("system");
Hi, Thanks for the fix, I've committed and push it to my git repository. commit 8e484f873046bff64cbfc43f3170d9e5920fd1d0 Author: Balazs Scheidler <bazsi@balabit.hu> Date: Tue Apr 7 12:52:41 2009 +0200 [cygwin packaging] fixed version information in the generated config file Problem reported and patch submitted by Corinna Vinschen. Reported-By: Corinna Vinschen On Wed, 2009-04-01 at 15:21 +0200, Corinna Vinschen wrote:
Ping?
On Mar 25 17:09, Corinna Vinschen wrote:
Hi,
The Cygwin service installer script creates a version entry without a colon, which leads to warnings. The below patch fixes that. Please apply.
Thanks, Corinna
--- contrib/cygwin-packaging/syslog-ng-config.ORIG 2009-03-25 17:08:34.000000000 +0100 +++ contrib/cygwin-packaging/syslog-ng-config 2009-03-19 19:21:34.000000000 +0100 @@ -205,7 +205,7 @@ if [ ! -f "${SYSCONFDIR}/syslog-ng.conf" then echo "Creating default ${SYSCONFDIR}/syslog-ng.conf file" cat > ${SYSCONFDIR}/syslog-ng.conf << EOF -@version 3.0 +@version: 3.0 options { keep_hostname(yes); owner("system");
______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.campin.net/syslog-ng/faq.html
-- Bazsi
Syslog-NG Version: ./syslog-ng -V syslog-ng 3.0.1+binpkg4 Revision: ssh+git://bazsi@git.balabit//var/scm/git/syslog-ng/syslog-ng-ose--mainline-- 3.0#master#555574a984eaef9410a2869db0af1be0d52b269b Compile-Date: Mar 12 2009 16:42:24 Enable-Threads: on Enable-Debug: off Enable-GProf: off Enable-Memtrace: off Enable-Sun-STREAMS: off Enable-Sun-Door: off Enable-IPv6: on Enable-Spoof-Source: on Enable-TCP-Wrapper: off Enable-SSL: on Enable-SQL: on Enable-Linux-Caps: on Enable-Pcre: off NTP Version: ntp.i386 4.2.2p1-9.el5.centos installed Linux Version: 2.6.18-128.1.6.el5PAE #1 SMP Wed Apr 1 10:02:22 EDT 2009 i686 i686 i386 GNU/Linux Relevant config section: source s_sys { file ("/proc/kmsg" program_override("kernel: ")); unix-stream ("/dev/log"); internal(); }; destination d_local_messages { file("/var/log/messages"); }; log { source(s_sys); filter(f_messages); destination(d_local_messages); }; All kind of other messages are being logged OK - but one that I just happened to notice is no ntpd logs. Any help would be appreciated. Charles Jennings
Hi, On Tue, Apr 7, 2009 at 9:52 PM, Charles Jennings <jennings.charles.e.security@gmail.com> wrote:
Syslog-NG Version:
[ cut ] I'd check first whether ntpd runs in a chrooted environment or not. When it is chrooted and syslog-ng is restarted (without using the keep-alive option for /dev/log) then ntpd won't be able to continue logging (/dev/log gets recreated). For chroot-ed apps you can add the log socket to the syslog-ng sources. For example chrooted postfix needs unix-dgram("/var/spool/postfix/dev/log"); Regards, Sandor
Doesn't look like it - here is some more info: Chkconfig --list ntpd 0:off 1:off 2:off 3:off 4:off 5:off 6:off /etc/crontab 01 * * * * root /usr/sbin/ntpd -q > /dev/null & /etc/sysconfig/ntpd # Drop root to id 'ntp:ntp' by default. OPTIONS="-u ntp:ntp -p /var/run/ntpd.pid" # Set to 'yes' to sync hw clock after successful ntpdate SYNC_HWCLOCK=yes # Additional options for ntpdate NTPDATE_OPTIONS="" /etc/ntp.conf restrict default kod nomodify notrap nopeer noquery restrict -6 default kod nomodify notrap nopeer noquery restrict 127.0.0.1 restrict -6 ::1 server time.nist.gov iburst server 127.127.1.0 fudge 127.127.1.0 stratum 10 driftfile /var/lib/ntp/drift keys /etc/ntp/keys -----Original Message----- From: syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] On Behalf Of Sandor Geller (IT) Sent: Wednesday, April 08, 2009 3:53 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] NTPD (maybe others) not logging - No idea why... Hi, On Tue, Apr 7, 2009 at 9:52 PM, Charles Jennings <jennings.charles.e.security@gmail.com> wrote:
Syslog-NG Version:
[ cut ] I'd check first whether ntpd runs in a chrooted environment or not. When it is chrooted and syslog-ng is restarted (without using the keep-alive option for /dev/log) then ntpd won't be able to continue logging (/dev/log gets recreated). For chroot-ed apps you can add the log socket to the syslog-ng sources. For example chrooted postfix needs unix-dgram("/var/spool/postfix/dev/log"); Regards, Sandor ____________________________________________________________________________ __ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.campin.net/syslog-ng/faq.html
On Wed, 2009-04-08 at 09:33 -0500, Charles Jennings wrote:
Doesn't look like it - here is some more info:
Chkconfig --list
ntpd 0:off 1:off 2:off 3:off 4:off 5:off 6:off
/etc/crontab
01 * * * * root /usr/sbin/ntpd -q > /dev/null &
/etc/sysconfig/ntpd
# Drop root to id 'ntp:ntp' by default. OPTIONS="-u ntp:ntp -p /var/run/ntpd.pid"
# Set to 'yes' to sync hw clock after successful ntpdate SYNC_HWCLOCK=yes
# Additional options for ntpdate NTPDATE_OPTIONS=""
/etc/ntp.conf
restrict default kod nomodify notrap nopeer noquery restrict -6 default kod nomodify notrap nopeer noquery
restrict 127.0.0.1 restrict -6 ::1
server time.nist.gov iburst server 127.127.1.0 fudge 127.127.1.0 stratum 10
driftfile /var/lib/ntp/drift
keys /etc/ntp/keys
Hmm.. you could try to strace the ntpd process to see how it tries to send log messages. It might use its own syslog() implementation instead of relying on libc and thus fail because of a mismatching UNIX domain socket type. (dgram vs. stream) -- Bazsi
participants (4)
-
Balazs Scheidler
-
Charles Jennings
-
Corinna Vinschen
-
Sandor Geller (IT)