Todd C. Merrill writes: [...]
And, NetApp, can you please fix this? The second line of these related messages doesn't contain a timestamp. Really fools up anything that expects it:
Sun Nov 12 17:56:50 EST [Java Thread]: TimeDaemon: timed: adjusting time: filer thinks time is Sun Nov 12 17:56:50 EST 2000. Time reported by time server time is Sun Nov 12 17:56:50 EST 2000 (skew -0.071 secs).
Not the only one like that. My bete noir is
Thu Nov 16 17:16:17 GMT [de4]: uid 261 tid 1: disk quota exceeded on volume CUS. Additional warnings will be suppressed for 30 minutes or until a quota resize.
We suppress those from the console by raising the level to kern.warning and <everything-else>.info, while keeping *.info for /etc/messages, but that's far from satisfactory.
The timed messages can be turned off by "options timed.log off", and we do -- but what I would prefer is a timed.log.min_jump so that I could see all steps of > 1s (say), but not the smaller deltas.
Chris Thompson University of Cambridge Computing Service, Email: cet1@ucs.cam.ac.uk New Museums Site, Cambridge CB2 3QG, Phone: +44 1223 334715 United Kingdom.