[Bug 240421] Please branch/build syslog-ng for EPEL (EL-5)

bugzilla at redhat.com bugzilla at redhat.com
Tue Dec 9 15:49:44 UTC 2008


Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=240421





--- Comment #6 from Douglas E. Warner <silfreed at silfreed.net>  2008-12-09 10:49:43 EDT ---
(In reply to comment #5)
>  * you'll have to static link the tcpwrappers' library in EL4 and in EL5
>    (syslog daemons can't depend on anything under /usr)
> 
>    rpm -ql tcp_wrappers (in EL5)
>    -----------------------------
>    /usr/include/tcpd.h
>    /usr/lib/libwrap.a
>    /usr/lib/libwrap.so
>    /usr/lib/libwrap.so.0
>    /usr/lib/libwrap.so.0.7.6
>
>  * EL4 only: you may also have to check if the glib2 library is already
>    located in /lib
> 

Thanks, I'll have to look into this.

>  * with the introduction of rsyslog in EL5.2 the logrotate file was modified
> 
>    $ cat /etc/logrotate.d/syslog 
>    /var/log/messages /var/log/secure /var/log/maillog /var/log/spooler \
>             /var/log/boot.log /var/log/cron {
>       sharedscripts
>       postrotate
>       /bin/kill -HUP `cat /var/run/syslogd.pid 2> /dev/null` 2> /dev/null ||
> true
>       /bin/kill -HUP `cat /var/run/rsyslogd.pid 2> /dev/null` 2> /dev/null ||
> true
>       endscript
>    }
> 
>    Notice the two pid files: one for sysklogd and one for rsyslog
> 

I actually have EL4/EL5 packages at my website that I've maintained for many
years (http://www.silfreed.net/download/repo/packages/syslog-ng ,
https://rpm.silfreed.net:8002/file/tip/syslog-ng/) that allows parallel
installation of sysklogd, rsyslog, and syslog-ng.

>  (question: why doesn't rsyslog use the same filename as the pid file?)

No clue, it's quite the pain.  And getting the other syslog-facility
maintainers to coordinate on making this pain-point go away has had very slow
progress.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.




More information about the fedora-triage-list mailing list