From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Real basics: authentication
Date: Fri, 10 Jan 2003 09:39:09 +0200 [thread overview]
Message-ID: <20030110093904.N12514@cackle.proxima.alt.za> (raw)
In-Reply-To: <20030110075834.K12514@cackle.proxima.alt.za>; from Lucio De Re on Fri, Jan 10, 2003 at 07:58:36AM +0200
On Fri, Jan 10, 2003 at 07:58:36AM +0200, Lucio De Re wrote:
>
> On Thu, Jan 09, 2003 at 09:41:57AM -0500, Russ Cox wrote:
> >
> > Is there anything interesting in /sys/log/auth?
>
Maybe the following will help?
1. tickle Jan 10 07:14:54 tr-ok lucio@lucio(192.96.32.71) -> lucio@lucio
2. tickle Jan 10 07:14:56 tr-ok lucio@lucio(192.96.32.71) -> lucio@inferno
3. tickle Jan 10 07:15:09 tr-ok proxima@proxima(192.96.32.73) -> proxima@proxima
4. tickle Jan 10 07:24:44 tr-ok lucio@lucio(192.96.32.71) -> lucio@lucio
5. tickle Jan 10 07:24:45 tr-ok lucio@lucio(192.96.32.71) -> lucio@inferno
6. tickle Jan 10 07:47:54 tr-ok inferno@inferno(192.96.32.75) -> inferno@proxima
7. tickle Jan 10 07:56:47 tr-ok lucio@lucio(192.96.32.71) -> lucio@lucio
8. tickle Jan 10 07:56:48 tr-ok lucio@lucio(192.96.32.71) -> lucio@inferno
9. tickle Jan 10 07:56:51 tr-ok lucio@inferno(192.96.32.75) -> lucio@proxima
10. tickle Jan 10 08:32:20 tr-ok proxima@proxima(192.96.32.73) -> proxima@proxima
These are from the auth server, the first bunch (1-5) is subsequent
to a file server reboot (to put it into "allow" mode) and the second
(6-10) is subsequent to the next reboot where the file server was
restored to normal operation. The proxima@proxima (ip 192.96.32.73)
is the 2ed CPU server and can safely be ignored.
192.96.32.71 is the drawterm workstation, 192.96.32.75 is the CPU
server. I logged into it - but I'd have expected inferno@inferno,
perhaps my NVRAM is set up badly? Or is it that lucio@inferno ought
to be lucio@proxima? How is that determined?
> I note that user inferno exists on the 3ed box but is a "group" with a
> totally different id on the 4ed file server that the auth server uses.
>
> I'll bring these two into line and see if it makes a difference.
>
It didn't, but perhaps the solution is in the above, invisible to
me.
++L
next prev parent reply other threads:[~2003-01-10 7:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-09 12:22 Lucio De Re
2003-01-09 14:41 ` Russ Cox
2003-01-10 5:15 ` Lucio De Re
2003-01-10 5:58 ` Lucio De Re
2003-01-10 7:39 ` Lucio De Re [this message]
2003-01-10 17:43 ` Russ Cox
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=20030110093904.N12514@cackle.proxima.alt.za \
--to=lucio@proxima.alt.za \
--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).