From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] strange things in /sys/log/auth
Date: Tue, 1 Jul 2003 00:09:03 -0600 [thread overview]
Message-ID: <Pine.LNX.4.44.0307010000410.14298-100000@fbsd.cpsc.ucalgary.ca> (raw)
In-Reply-To: <19dd2f4ec1a603144f39a37b9fb86854@collyer.net>
diff (cmp) doesn't give any difference between keyfs on my fossil system and
sources (i do updates daily, sometimes more so :)..
neither the source nor the binary differ...
the machine is in a private network, so I could explain you my entire
auth configuration. what exactly would be most helpful?
andrey
ps: i just observed that /mnt/keys is an exact duplicate of the one that is
on the kfs server (i just did mkfs < /n/kfs | mkext > /n/fossil). the logs
on the kfs server show complaints about bootes' 'expire' but none of the
garbage that i posted couple of messages ago...
pps: if you don't see anything obvious i suggest we just wait until i get a
chance to reset the auth info on wednesday (tomorrow is canada day, so we
drink beer... i think... we always drink beer around here :)
there is a big chance i screwed something up while converting the kfs into a
fossil, i was just hoping that it'll all work, and so far it has, apart from
these silly log messages :)
On Mon, 30 Jun 2003, Geoff Collyer wrote:
> Curious, my files in /mnt/keys are owned by auth and auth, not bootes
> and sys. Your permissions are also stricter than mine. Are you
> running the latest keyfs?
>
next prev parent reply other threads:[~2003-07-01 6:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-01 5:14 andrey mirtchovski
2003-07-01 5:26 ` Dan Cross
2003-07-01 5:31 ` Geoff Collyer, geoff
2003-07-01 5:40 ` andrey mirtchovski
2003-07-01 5:49 ` andrey mirtchovski
2003-07-01 11:45 ` David Presotto
2003-07-02 16:35 ` andrey mirtchovski
2003-07-03 18:42 ` david presotto
2003-07-01 5:52 ` Geoff Collyer, geoff
2003-07-01 6:09 ` andrey mirtchovski [this message]
2003-07-01 6:37 ` okamoto
2003-07-01 6:46 ` Geoff Collyer, geoff
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=Pine.LNX.4.44.0307010000410.14298-100000@fbsd.cpsc.ucalgary.ca \
--to=mirtchov@cpsc.ucalgary.ca \
--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).