How to correct mrtg going berserk?

[rat_hotbox.ru]

Hello Mark,

Wednesday, October 29, 2003, 1:48:33 AM, you wrote:

M> Mrtg has gone berserk on me; apparently they have never heard of clocks
M> being adjusted because of Daylight Savings:

M> -------------------------------------
M> Rateup ERROR: /usr/local/bin/rateup found that 192.168.0.1_1's log file time
M> of 1067382961 was greater than now (1067380560)
M> ERROR: Let's not do the time warp, again. Logfile unchanged.
M> Rateup ERROR: /usr/local/bin/rateup found that localhost.cpu's log file time
M> of 1067382961 was greater than now (1067380560)
M> ERROR: Let's not do the time warp, again. Logfile unchanged.
M> Rateup ERROR: /usr/local/bin/rateup found that memory's log file time of
M> 1067382963 was greater than now (1067380562)
M> ERROR: Let's not do the time warp, again. Logfile unchanged.
M> Rateup ERROR: /usr/local/bin/rateup found that swap_memory's log file time
M> of 1067382963 was greater than now (1067380562)
M> ERROR: Let's not do the time warp, again. Logfile unchanged.
M> -------------------------------------

M> Manually changing the log-times back does not help either. Does anyone know
M> how to correct it?

M> Thanks,

M> - Mark

I had this problem since i reseted bios with jumper to manufactory settings - i had 2000
year on Freebsd (see man date)
After correcting date in bios - it`s all right

I _do_not_advice_ you playing with MRTG`s logs - it`s too fragile :)

-- 
Let the source be with you,
 Rat                            mailto:donat33 at hotbox.ru