On Wed, 02 Apr 2014, Paul Quinn wrote to Bj”rn Felten:

 BF>    Strangely enough -- despite my 4 connection restriction -- I 
 BF> have all the way up to IP_20.LOG in my log directory. I have no 
 BF> idea about how this could have happened. Most of the double digit 
 BF> log files are single connections with Connection Error in it. 
 BF> 

 PQ> It's infinitely better than the way binkD minces multiple sessions 
 PQ> into a single logfile.

if you think that's bad, you haven't done much wading into your *nix boxen's
logs in a long while... remember that binkd originates from *nix and that's
where the development mindset is... this is why we haven't been able to get
some requests fulfilled (eg: adding some additional semaphore files for things
like freezing binkd for log processing, terminating binkd with a specific
error level for maintence or log processing, and similar)...

 PQ> Radius's IP logs are easily handled in my pre-maintenance BAtch, 
 PQ> like so...

 PQ> [ ... ]
 PQ>     COPY /Y ip_*.log IP-Calls.Log
 PQ>     FOR %%N IN (ip_*.log) DO IF EXIST %%N DEL %%N
 PQ> [ ... ]

FWIW: you shouldn't need the "if exist" there because the file wouldn't be
there if "for %%n in" didn't find it to start with ;)

 PQ> During maintenance, the "IP-Calls.Log" file is posted to a local 
 PQ> echo and then archived in a daily ARJ.  Simple.

 PQ> BTW, I do have a BATch that can de-splice a binkD logfile.  :) 

desplice? as in break out each session by session id number? how do you keep
them in date/time order to make running down the day's sessions easier to
follow?

)\/(ark

One of the great tragedies of life is the murder of a beautiful theory by a
gang of brutal facts. --Benjamin Franklin

--- FMail/Win32 1.60
 * Origin:  (1:3634/12.71)