argus-2.0.4 does after a couple of days

[Christian Martin]

Hello, kind people,

I'm running argus 2.0.3 on a machine with a 2.4 Linux kernel.  There's a
fair amount of traffic on the network (argus is pumping out about 800Mb a
day, uncompressed), but it does the job admirably.  So far, so good.  I
recently upgraded to 2.0.4, which worked fine for a couple of days and then
fell over with no explanation.  It restarted fine, but the same thing always
happened - it would survive for anything between one and three days before
bombing out.  I've switched back to 2.0.3 and the problems have gone.
Unfortunately, the environment isn't really suited to debugging (the machine
is in a locked room some distance from my office, and there's so much
activity that logging over SSH would be a bit crazy).

I was wondering if anyone else has experienced problems of this nature, and
if there may be any way to get to the bottom of them without '-D 8'.  Both
2.0.3 and 2.0.4 were installed from the RPM because it was easiest at the
time.

Incidentally, for anyone who is thinking of trying it, I've been
successfully running ra (2.0.1) as a persistent daemon on a Linux (debian,
2.2 kernel) box for over six months now - it has written hundreds of
gigabytes of logs with seemingly no memory problems.

Many thanks in advance,

Christian Martin

--
Christian Martin
IT Department
Jesus College, Cambridge
e-mail: c.martin at jesus.cam.ac.uk
telephone: 01223-(7)64101