From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] cron and timesync
Date: Thu, 17 Jul 2003 20:26:07 +0100 [thread overview]
Message-ID: <66e17ca3544b3b475439dbd93f5999f7@vitanuova.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0307171223310.7478-100000@fbsd.cpsc.ucalgary.ca>
> ... # time set by rtc (1am)
> aux/timesync -n ntp.ucalgary.ca # time still 1am
> ...
> auth/cron # time still 1am
i came across this problem in for another reason, and my assessment
was not that /dev/rtc wasn't being set (after all, everything reads
/dev/time, not /dev/rtc), but that aux/timesync returns immediately
without having synced the time.
it wouldn't be hard to do: it just requires a little synchronisation
between the forked process and its parent. i'm afraid i didn't get
around to it (story of my life!).
next prev parent reply other threads:[~2003-07-17 19:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-17 18:53 andrey mirtchovski
2003-07-17 19:26 ` rog [this message]
2003-07-17 19:47 ` Dan Cross
2003-07-17 20:21 ` Geoff Collyer
2003-07-17 20:57 ` David Presotto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=66e17ca3544b3b475439dbd93f5999f7@vitanuova.com \
--to=rog@vitanuova.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).