Logrotate kern.log messages and syslog

[Petri Pennanen]

Good day to you all,

In the process of reading som log-files recently i noticed that they
were huge. /var/log is 872 MB all together. 

The greatest culprits are:

        -rw-r-----  1 root        adm  304852853 2005-02-24 11:36
        kern.log
        -rw-r-----  1 root        adm  269395710 2005-02-24 14:19
        messages
        -rw-r-----  1 root        adm  305119873 2005-02-24 14:19 syslog

This was probably is caused by the a few inotify/gamin crashes last
night (on Hoary). However logrotate status doesn't show any entries for
these logs. 

        cat /var/lib/logrotate/status
        
        logrotate state -- version 2
        "/var/log/acpid" 2005-2-22
        "/var/log/aptitude" 2005-2-22
        "/var/log/base-config.log" 2005-2-22
        "/var/log/base-config.timings" 2005-2-22
        "/var/log/cups/error_log" 2005-2-23
        "/var/log/exim4/mainlog" 2005-2-23
        "/var/log/exim4/rejectlog" 2005-2-22
        "/var/log/exim4/paniclog" 2005-2-22
        "/var/log/lvm" 2005-2-22
        "/var/log/ppp-connect-errors" 2005-2-22
        "/var/log/scrollkeeper.log" 2005-2-22
        "/var/log/vsftpd.log" 2005-2-22
        "/var/log/wtmp" 2005-2-22
        "/var/log/btmp" 2005-2-22

There are no entries kern.log, messages and syslog in /etc/logrotate.d.
However the latest entries in these logs are from yesterday, so they
seem to get rotated (now that I'm running anacron that is). Where can I
find the logrotate settings for kern.log, messages and syslog?

A related problem is that if I try to run logrotate by hand it
segfaults.

        $ sudo gdb logrotate
        (gdb) run /var/log/kern.log
        /var/log/kern.log
        Starting program: /usr/sbin/logrotate /var/log/kern.log
        (no debugging symbols found)
        (no debugging symbols found)
        (no debugging symbols found)
        (no debugging symbols found)
        
        Program received signal SIGSEGV, Segmentation fault.
        0x0804c983 in ?? ()

Am I doing something wrong or is there actually a problem with
logrotate?

- Petri