On Tue, 22.01.13 16:25, Zbigniew Jędrzejewski-Szmek ([email protected]) wrote:
> > On Sun, Jan 20, 2013 at 04:27:58PM +0100, Eelco Dolstra wrote: > > --- > > man/systemd.service.xml | 2 +- > > src/core/manager.c | 2 +- > > 2 files changed, 2 insertions(+), 2 deletions(-) > Applied. > > > diff --git a/man/systemd.service.xml b/man/systemd.service.xml > > index f7cbbb4..891b347 100644 > > --- a/man/systemd.service.xml > > +++ b/man/systemd.service.xml > > @@ -745,7 +745,7 @@ > > open access to the notification socket > > when using > > <varname>Type=notify</varname> or > > - <varname>WatchdogUsec=</varname> (see > > + <varname>WatchdogSec=</varname> (see > > above). If those options are used but > > <varname>NotifyAccess=</varname> not > > configured it will be implicitly set > Just a note here for mailing-list-archives' sake: the configuration variable > should be WatchdogSec=, since the units (if not specified) are seconds. > OTOH, DBus property is called WatchdogUSec, and the environment variable > WATCHDOG_USEC=, since they are both specified in microseconds. To extend on this, for mailing list archives' sake: The "Sec" in WatchdogSec= indicates that the default unit is seconds. I.e. WatchdogSec=70 means 70 seconds. However, if you explicitly specify the unit you can give more precise or bigger values. Example: WatchdogSec=10d for ten days and WatchdogSec=50ms for 50 milliseconds. Lennart -- Lennart Poettering - Red Hat, Inc. _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
