Memory Problems in Argus-1.8

Carter Bullard cbullard at
Fri Apr 7 10:48:00 EDT 2000

   Hmmm, well this wasn't the intended result.
The approach is for the clients to automatically
close the socket when they see an argus management
CLOSE record.  Argus has always sent this message,
but the clients did not take any action on them.
This is why 1.8.1 version ra() is important to
this strategy.  The other part of the strategy, is
for argus() to get into a loop, waiting for the
client sockets to close, and then it exits.

   As it was working once, I'm sure we can get it
working again ;o)


> -----Original Message-----
> From: Neil Long [mailto:neil.long at]
> Sent: Thursday, April 06, 2000 12:57 PM
> To: Bullard, Carter [NYPAR:DS33:EXCH]
> Cc: neil.long at
> Subject: Re: Memory Problems in Argus-1.8
> Hi
> I have just had a quick look at the 1.8.1 argus_dlpi.
> If I kill the remote ra and then argus I can re-start it instantly.
> If I kill the argus daemon then no matter whether I kill ra 
> or leave it
> running I have to wait for the socket to time out before argus can
> start and re-bind the same port.
> The latter mode also has problems if I use the 1.8 ra rather 
> than 1.8.1
> ra - if I use CTRL-C I have do do it twice before it dies and it does
> not go quietly if I use kill -HUP - the man records are output but it
> still runs -
> so 2 CTRL-C or 2 HUPs to get it to go away.
> with 1.8.1 ra and argus 1 HUP is enough but I still get the TIME_WAIT
> problem.
> This on Solaris 2.6 (Ultra 1) test box, not main logger.
> Can you reproduce this? Not a major problem since killing the ra
> listener and then HUP argus is neat and clean. Many thanks!
> (Don't suppose you know the ndd -set incantation to reduce the
> TIME_WAIT parameter before cleanup?  tcp_close_wait_interval ?)
> Neil
> -- 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>  Dr Neil J Long, Computing Services, University of Oxford
>  13 Banbury Road, Oxford, OX2 6NN, UK Tel:+44 1865 273232 
> Fax:+44 1865 273275
>  EMail:       Neil.Long at  
>  PGP:    ID 0xE88EF71F    OxCERT: oxcert at PGP: ID 0x4B11561D
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the argus mailing list