Date: Wed, 28 Jul 2004 18:13:45 -0400 From: Brian Fundakowski Feldman <green@FreeBSD.org> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/watchdogd watchdogd.c Message-ID: <20040728221345.GB19257@green.homeunix.org> In-Reply-To: <47640.1091049381@critter.freebsd.dk> References: <20040728233751.A31182@newtrinity.zeist.de> <47640.1091049381@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jul 28, 2004 at 11:16:21PM +0200, Poul-Henning Kamp wrote: > In message <20040728233751.A31182@newtrinity.zeist.de>, Marius Strobl writes: > >On Fri, Jul 23, 2004 at 03:24:58PM +0000, Brian Feldman wrote: > >> green 2004-07-23 15:24:58 UTC > >> > >> FreeBSD src repository > >> > >> Modified files: > >> usr.sbin/watchdogd watchdogd.c > >> Log: > >> Now that mlockall(2) is unbroken, use it to keep watchdogd(8) permanently > >> out of swap. > >> > > > >This broke watchdogd(8) on at least alpha and sparc64: > >omega# watchdogd > >watchdogd: mlockall: Resource temporarily unavailable > > > >Like I told you before, every call of mlockall(MCL_CURRENT) returns -1 > >and sets errno to EAGAIN on these platforms. > > Worse, if it had worked it would have prevented watchdogd from > detecting swap disk related issues. > > The only kind of special treatment you should give a watchdog daemons > is negative benefits so that it will be more sensitive to trouble. The usage of real-time priority isn't really much of a negative benefit, either, though. -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040728221345.GB19257>