home bbs files messages ]

Just a sample of the Echomail archive

<< oldest | < older | list | newer > | newest >> ]

 Message 220 
 Paul Quinn to Mark Lewis 
 Number of outgoing connections 
 04 Apr 14 10:40:00 
 
Hi! mark,

On Thu, 03 Apr 14, you wrote to me:

 PQ>> It's infinitely better than the way binkD minces multiple
 PQ>> sessions into a single logfile.
 ml> if you think that's bad, you haven't done much wading into your *nix
 ml> boxen's logs in a long while...

That's correct.  I only have time for reading Fido-related software logs.  :) 
On rare occasions will I go digging in the system logs, and then only for
specific (rare) problems.

 ml> remember that binkd originates from *nix and that's where the
 ml> development mindset is... this is why we haven't been able to get some
 ml> requests fulfilled (eg: adding some additional semaphore files for
 ml> things like freezing binkd for log processing, terminating binkd with
 ml> a specific error level for maintence or log processing, and
 ml> similar)...

Ah-huh.  Absolutely.

 PQ>>     FOR %%N IN (ip_*.log) DO IF EXIST %%N DEL %%N [ ... ]
 ml> FWIW: you shouldn't need the "if exist" there because the file
 ml> wouldn't be there if "for %%n in" didn't find it to start with ;)

For that matter, I could probably just do a flat 'DEL /Y ip_*.log' but I left
it in as it works IAC.  ;-)

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

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

Yes.  Yes.  The logfile is already in date/time order, so it's just a matter
of stepping through the log searching for (what I call) ID tags, matched with
a "session with" log entry.  This is the theory.  I'd forgotten that I used to
be really only looking for _outbound_ sessions since I wasn't running binkD in
daemon mode then (2001), with the target string being "call to".

Pseudocode:
-----------
PROCESS EACH LINE IN THE FILE
  FOR EVERY "call to" LINE
    EXTRACT THE PROCESS_ID TAG
    FOR EVERY OCCURRENCE OF THAT PROCESS_TAG OUTPUT THE LOG DETAIL
  BUMP A LINE COUNTER
LOOP UNTIL WE RUN OUT OF LINES

The guts of the script uses a couple of DOS commands...

[ ... ]
  TYPE %TEXTFILE%|FIND "[%ID_TAG%]">%OUTFILE%
[ ... ]

Easy-peasy.

Cheers,
Paul.

... Hey SysOp! You'd better upgrade me or el%$^&%NO CARRIER
--- Paul's Win98SE VirtualBox
 * Origin: Quinn's Post - Maryborough, Queensland, OZ (3:640/384)

<< oldest | < older | list | newer > | newest >> ]

(c) 1994,  bbs@darkrealms.ca