From: 9nut@9netics.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] rm /lib/ndb/auth?
Date: Wed, 10 Mar 2004 23:07:50 -0800 [thread overview]
Message-ID: <3f342b9ff85a0d994a771a0666de4b3f@9netics.com> (raw)
In-Reply-To: <d560c4058981a5546ec80db31f22841d@orthanc.cc.titech.ac.jp>
>> Could it be that authsrv had it open when you removed it, and
>> it has not closed it?
>
> Umm, I don't think so. Authsrv writes `no /lib/ndb/auth'
> error to syslog and that should mean authsrv couldn't
> open it.
Since others appear to be getting some sleep, I'll try for double
or nothing; maybe I can redeem myself ☺
I checked authsrv.c. Interesting. Perhaps your question is
rhetorical. It looks like when hostid and uid in the ticket request
are the same, speaksfor() does not consult /lib/ndb/auth and returns
success. Is the hostid the same as the uid you're authenticating?
next prev parent reply other threads:[~2004-03-11 7:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-11 5:05 YAMANASHI Takeshi
2004-03-11 7:07 ` 9nut [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-11 4:26 YAMANASHI Takeshi
2004-03-11 5:57 ` 9nut
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=3f342b9ff85a0d994a771a0666de4b3f@9netics.com \
--to=9nut@9netics.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).