Reduce the number of unnecessary time(3)/gettimeofday(2) calls, and make sure

that the time always goes forward, so reports are neither duplicated nor lost.

Report state changes stabilised through dampening immediately, instead of delay-
ing them until the next reporting window; previously, it was common for check()
to lag one second behind report(), hence the initial report was delayed one
extra minute (this then reduces the number of sleep(3)/nanosleep(2) calls, too).

ok ckuethe;  some man-page suggestions jmc

1 files changed, 6 insertions, 8 deletions

diff --git a/usr.sbin/sensorsd/sensorsd.8 b/usr.sbin/sensorsd/sensorsd.8
index 46cbf5fe56e..fd802087be4 100644
--- a/usr.sbin/sensorsd/sensorsd.8
+++ b/usr.sbin/sensorsd/sensorsd.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: sensorsd.8,v 1.18 2007/11/28 19:20:05 jmc Exp $
+.\"	$OpenBSD: sensorsd.8,v 1.19 2008/03/16 03:07:03 cnst Exp $
 .\"
 .\" Copyright (c) 2003 Henning Brauer <henning@openbsd.org>
 .\" Copyright (c) 2005 Matthew Gream <matthew.gream@pobox.com>
@@ -16,7 +16,7 @@
 .\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
 .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 .\"
-.Dd $Mdocdate: November 28 2007 $
+.Dd $Mdocdate: March 16 2008 $
 .Dt SENSORSD 8
 .Os
 .Sh NAME
@@ -26,7 +26,6 @@
 .Nm sensorsd
 .Op Fl d
 .Op Fl c Ar check
-.Op Fl r Ar report
 .Sh DESCRIPTION
 The
 .Nm
@@ -63,15 +62,14 @@ The options are as follows:
 Check sensors every
 .Ar check
 seconds.
+The shortest reporting period for state changes
+will be three times this value.
+The default is 20.
 .It Fl d
 Do not daemonize.
 If this option is specified,
 .Nm
 will run in the foreground.
-.It Fl r Ar report
-Report changes in sensor status every
-.Ar report
-seconds.
 .El
 .Sh FILES
 .Bl -tag -width "/etc/sensorsd.conf"
@@ -99,4 +97,4 @@ an additional delay in status reporting and command execution,
 e.g. one may notice that
 .Nm
 makes its initial report about the state of monitored sensors
-not immediately, but either 1 or 2 minutes after it is being started up.
+not immediately, but about 60 seconds after it is being started up.