> I think that assumption is wrong. The repeated messages are when syslog
> decides to empty the buffer.  As far as I know, it isn't possible to
> turn off that and get real timing information.
> > > Oct  3 22:48:01 cti-350 kernel: TE410P: Double/missed interrupt detected
> > > Oct  3 22:49:01 cti-350 kernel: TE410P: Double/missed interrupt detected

On per minute, on the minute....

> > > Oct  3 22:52:01 cti-350 last message repeated 2 times
> > > Oct  3 22:54:01 cti-350 last message repeated 3 times

Five minutes later, we've had 5 more messages.

> > > Oct  3 22:56:01 cti-350 last message repeated 2 times
> > > Oct  3 22:58:01 cti-350 last message repeated 2 times
> > > Oct  3 23:00:01 cti-350 last message repeated 2 times
> > > Oct  3 23:03:01 cti-350 last message repeated 2 times
> > > Oct  3 23:05:01 cti-350 last message repeated 2 times
> > > Oct  3 23:07:01 cti-350 last message repeated 2 times
> > > Oct  3 23:09:01 cti-350 last message repeated 2 times
> > > Oct  3 23:11:01 cti-350 last message repeated 2 times
> > > Oct  3 23:14:01 cti-350 last message repeated 2 times
> > > Oct  3 23:16:01 cti-350 last message repeated 2 times
> > > Oct  3 23:18:01 cti-350 last message repeated 2 times
> > > Oct  3 23:20:01 cti-350 last message repeated 2 times
> > > Oct  3 23:22:01 cti-350 last message repeated 2 times

Every two minutes, we have 2 messages, thus....

one message per minute.

Mark

_______________________________________________
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to