Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    ARGUS    |    Argus Support Echo    |    613 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 41 of 613    |
|    mark lewis to Kurt Weiske    |
|    Single IP_LOG file?    |
|    11 Aug 12 10:49:17    |
       KW> I'm running RADIUS 4.010 and was wondering if there's some way to        KW> get all of the IP nodes to write to one log file? I have IP_1.log        KW> through IP_6.log in my LOG directory, and sorting through 6 files        KW> is time consuming.               what type of sorting? is there some sort of indicator in each line that keeps       all of a session's entries together? maybe something like the number in [] in       this binkd sample?              - 01 Aug 00:00:01 [114] incoming from 24.87.152.147 (2391)       + 01 Aug 00:00:02 [16959] incoming session with 24.87.152.147 (2391)       - 01 Aug 00:00:02 [16959] OPT MB CRC MD5       - 01 Aug 00:00:02 [16959] SYS BandMaster BBS       - 01 Aug 00:00:02 [16959] ZYZ Dallas Hinton       - 01 Aug 00:00:02 [16959] LOC The BandMaster, Vancouver, BC, Canada       - 01 Aug 00:00:02 [16959] NDL IBN       - 01 Aug 00:00:02 [16959] TIME 2012/07/31 21:00:01 -8:00       - 01 Aug 00:00:02 [16959] VER Internet Rex 2.29 Win32 (binkp/1.1)              it might be possible to combine those logs (eg: copy ip_1 + ip_2 + ip_3       ip_all) and then sort them by date/time and then the sequence number in []...               KW> I'd prefer to have them all write to one file, if possible, but        KW> can't find anything in the preferences dialogs.              if you don't care about them being in date/time order, just copy them together       as shown above... but you'll have to do this each day after saving the       previous one or maybe use a unique name for each combined log...              i don't recall any way of having them all write to one... it is easier to code       for each writing to their own... why? because multiples writing to the same       log at the same time is not an easy task...              )\/(ark               * Origin: (1:3634/12)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca