James, you wrote:
>>trapd keeps a count of every trap he writes and he adds the size in bytes
>>what he has already written. So as long as he handles the switching of
>>trapd.log to trapd.log.old, there is no way you can lose traps, because
>>write the new one to the file until the old log has been switched.
I've written a script which parses the trapd log, and generates an
availability report based on various agent traps(not netmon) (DLCI,LINK
UP/DOWN, etc.). I have to rotate the logs with cron, otherwise the reports
might not be complete on the first of the month(almost certainly not,
actually), and the monthly cron job would reflect incomplete data.
Currently I check for the backup file, and process it if it exists.....but
it would be nice if I could reset this byte count somehow after renaming
the log file - is that possible?