From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] aux/timesync -f fails
Date: Fri, 10 May 2002 10:59:46 +0100 [thread overview]
Message-ID: <3f4f30cb9edfd67f111b6a028020be01@caldo.demon.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 131 bytes --]
i suspect timesync needs to use amount.
try changing /sys/src/cmd/aux/timesync.c:270
if(amount(fd, "/n/boot", MREPL, "") < 0)
[-- Attachment #2: Type: message/rfc822, Size: 1658 bytes --]
To: 9fans@cse.psu.edu
Subject: [9fans] aux/timesync -f fails
Date: Fri, 10 May 2002 09:07:02 +0100
Message-ID: <5ffc0b4acd166eade239527d23481286@9fs.org>
My old arrangement of synchronising the fileserver (with sntp) and then
setting the clock of the terminals from the fileserver root seems not to work
any more.
term% aux/timesync -f
term% aux/timesync: mounting /srv/boot: attach -- unknown user or failed authentication
The file server prints something including the words SUCK EGGS.
Anyone care to enlighten me?
next reply other threads:[~2002-05-10 9:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-10 9:59 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-10 10:42 nigel
2002-05-10 8:07 nigel
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=3f4f30cb9edfd67f111b6a028020be01@caldo.demon.co.uk \
--to=forsyth@caldo.demon.co.uk \
--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).