Hi! Björn,

In a message to Kurt Weiske you wrote:

 KW>> I've run 8 connections for some time, the only annoyance is
 KW>> Radius' keeping separate log files for each connection.

 BF>    Ah yes, there's that too.

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

It's infinitely better than the way binkD minces multiple sessions into a
single logfile.  Radius's IP logs are easily handled in my pre-maintenance
BAtch, like so...

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

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

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

Cheers,
Paul.

... Ed Vance: Tagline Thievery Criminal since 1994.
--- Paul's Win98SE VirtualBox
 * Origin: Quinn's Post - Maryborough, Queensland, OZ (3:640/384)