Date: Mon, 19 Sep 2011 15:49:13 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: Arnaud Lacombe <lacombar@gmail.com> Cc: Poul-Henning Kamp <phk@phk.freebsd.dk>, FreeBSD-Current <freebsd-current@FreeBSD.org> Subject: Re: Very imprecise watchdogd(8) timeout Message-ID: <4E773A49.20300@FreeBSD.org> In-Reply-To: <CACqU3MVF5MwqeC%2Bs9VKk4mLJenmoS9Q_bJWkbYeFzaBFjo67gQ@mail.gmail.com> References: <CACqU3MWs0HHnZchOwmwWG8U9Vd2pBDKAqf6Pdw5zS_XO_S6Ppw@mail.gmail.com> <58772.1316203388@critter.freebsd.dk> <CACqU3MVF5MwqeC%2Bs9VKk4mLJenmoS9Q_bJWkbYeFzaBFjo67gQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
on 16/09/2011 23:59 Arnaud Lacombe said the following: > in which case the current notifier-based architecture is broken. You > may want to have a soft-watchdog triggering after 5s, and a fallback > hardware watchdog triggering after 60s. So let's start with the real problem, FreeBSD watchdog infrastructure doesn't expose an API to do what you described above. I think that it would be a rather small part to change the representation of timeouts from current form to, say, value + unit encoding. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E773A49.20300>