Radium and output files

[Mike Iglesias]

I have a copy of radium running that is receiving netflow records from our
routers and writing them to a file.  When I rename the output file, radium
creates a new one but keeps the old one open, so when the file is gzip'd the
space used is not reclaimed.  Is radium supposed to work like argus in that
when the output file is renamed, it will close it and open a new one, or do I
have to restart radium when I rename the file?

Here's some output from lsof showing what radium did:

radium  12671 root    0u   CHR  136,1         0t0       4 /dev/pts/1 (deleted)
radium  12671 root    1u   CHR  136,1         0t0       4 /dev/pts/1 (deleted)
radium  12671 root    2u   CHR  136,1         0t0       4 /dev/pts/1 (deleted)
radium  12671 root    3w   REG    9,0  2010741524 3932172 /log/argus/argus.out
radium  12671 root    4w   REG    9,0 13282553300 3932171
/log/argus/argus.out.20110411 (deleted)

argus.out.20110411 is yesterday's file, which was renamed shortly after
midnight by a cron script.  The script gzip'd the file after it renamed it, so
that's why lsof is saying the file has been deleted.


-- 
Mike Iglesias                          Email:       iglesias at uci.edu
University of California, Irvine       phone:       949-824-6926
Office of Information Technology       FAX:         949-824-2270