Date: Sat, 2 Nov 2002 16:37:41 +1100 (EST) From: Peter Hoskin <peterh@ripewithdecay.com> To: "Jeroen C. van Gelderen" <jeroen@vangelderen.org> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: rate-limiting uptime went backwards? Message-ID: <20021102163558.S301-100000@extortion.peterh.dropbear.id.au> In-Reply-To: <0C73DE87-EE16-11D6-BF9D-000393754B1C@vangelderen.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Those messages are usually due to a faulty system clock. Generally, when you generate a bit of load these messages will appear. The reason why they aren't rate limited is they are an important kernel message. Regards, Peter Hoskin On Fri, 1 Nov 2002, Jeroen C. van Gelderen wrote: > Hi, > > Is there any specific reason why the "microuptime went backwards" > message is not rate-limited? These messages are rather easy to provoke > by the local user tinkering with something as mundane as Java and > constitute a nice local DoS attack. > > -J > -- > Jeroen C. van Gelderen - jeroen@vangelderen.org - +1 242 357 5115 > Incentive Incompatibility > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021102163558.S301-100000>