magill@operations.upenn.edu (PENNnet Oper/Planning) (09/24/89)
In article <1989Sep19.151922.22555@cs.rochester.edu> becker@cs.rochester.edu (Tim Becker) writes: > We wrote an awk script to keep track of connect time on some of our annex > ports (the modem ports). We used the Event Logging feature of the annex > s/w. This sends Unix syslog msgs to a Unix machine of your choice. It can > log every annex port open and close. > > One problem with it is that it uses the 4.2bsd syslog format. Since > upgrading our Suns to SunOS 4.0.x, the annex event logging won't work > anymore (SunOS 4.0.x uses the 4.3bsd syslog format). I'm hoping for a fix > from the Encore-annex folks. > That's interesting - I had no problems with annex logging in our switch to SunOS/4. I Happen to have been using various levels of beta 4.1.(1-9) since last spring for various bug fixes. The latest copy is 4.1.9 which is logging merily away. I was told that the real 4.1 was due out "immediately", just before Labor Day. I don't even remember having to do anything fancy once I got it running, but do recall that there was something "strange" about getting it running. I remember that it didn't "start right up", but the problem was a configuration problem - on the Sun if I remember correctly. Oh yeah, now I remember - this is one of those - "If the file doesn't exist, don't do anything" "unix-gotchas". I have a couple of scripts to cycle and recreate the annex logfiles so that the whole process can run out of cron if anybody's interested. I never did get around to processing the data collected. So I'll trade for the AWK scripts. -- William H. Magill Manager, PENNnet Operations Planning Data Communications and Computing Services (DCCS) University of Pennsylvania Internet: magill@dccs.upenn.edu magill@eniac.seas.upenn.edu magill@upenn.edu