log file getting too big

[Ondrej Zajicek]

On Wed, Nov 18, 2009 at 02:44:32PM +0000, David J Craigon wrote:
>    It might well be a problem on my end. Any suggestions are welcome.
> 
>    It's not the file system:
> 
>    [root at localhost 5731]# ls -sh /tmp/
>    total 5.9G
>    3.9G bigfile     0 birdlogtmp  2.1G look
> 
>    where the file "look" is what was the bird log file. Bird stopped when the
>    file became 2.1 Gb. As you can see, I can make bigger files
> 
>    I've got bird to create a core dump, which I can include if you really
>    want, but sticking it in gdb tells me the following:

>    [root at localhost ~]# gdb /usr/sbin/bird core.4934
>
>    Program terminated with signal 25, File size limit exceeded.
>    [New process 4934]
> 
>    The whole signal 25 thing suggests it is coming from outside, but if so,
>    what?

That makes it clear why BIRD crashed - it received unhandled signal and
a crash is a default behavior for that signal.

But it is strange that sug signal was sent when it is possible to have bigger
files on that FS. What FS is used for /tmp ? What kernel version is used?

BTW, i would suggest to use some smart syslog variant and use syslog-based
log rotation.

-- 
Elen sila lumenn' omentielvo

Ondrej 'SanTiago' Zajicek (email: santiago at crfreenet.org)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20091118/dbd1fc5e/attachment-0001.asc>