I have an incident which occurs regularly around noon thirty the last
couple of Tuesdays. Trying to look at the console.logs. It looks like
they are wrapping. Funny thing is only around this incident. Strange
error (pmr open) trying to archive the boss' email.

....+....1....+....2....+....3....+....4....+....5..
************Beginning of data**************
console_NOTES02_2013_06_25@00_32_40.log

[696503:15822:00004-000000D1] 06/25/2013 14:34:13.88
...

and

....+....1....+....2....+....3....+....4....+....5..
************Beginning of data**************
console_NOTES02_2013_07_02@00_40_06.log
[702287:20890:00004-0000013E] 07/02/2013 14:06:16.98

It's only the Tuesday ones. Size on those Tuesday ones is rather
significant, 39MB vs usual 2-9MB size. Let me guess:
the server gets bounced nightly, which would cause a new console.log.
secondary server in the cluster (no one's home server),
Tuesday's archive is the only busy day,
Therefore this experience is expected since it's the only day that garners
significant log activity.
notes.ini line
Log=log.nsf, 1, 0, 7, 40000
I'm guessing the 39MB size and that 40000 in the notes.ini are somewhat
related.
Is there a way to say, don't wrap, generate a new successive console.log?


Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2021 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.