From: Helge Bahmann <hcb@chaoticmind.net>
To: "Kevin Coffman" <kwc@citi.umich.edu>
Cc: nfs@lists.sourceforge.net
Subject: Re: lockd and krb5
Date: Thu, 16 Nov 2006 17:02:38 +0100 [thread overview]
Message-ID: <200611161702.38857.hcb@chaoticmind.net> (raw)
In-Reply-To: <4d569c330611160621w48c7a85cy9982ea8c9d96877@mail.gmail.com>
Am Donnerstag, 16. November 2006 15:21 schrieb Kevin Coffman:
> I can't help directly with the locking behavior, but could it be
> related to expiring Kerberos credentials and/or gss contexts?
no credentials are valid
> Is the KDE startup that often triggers this at initial login, or at some
> other time?
seems completely erratic; it happens both at initial login as well as second
login (after successful logout, but before credentials expire); if there is
any regularity at all then it seems that initial login seems more likely to
succeed
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2006-11-16 16:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-16 10:37 lockd and krb5 Helge Bahmann
2006-11-16 14:21 ` Kevin Coffman
2006-11-16 16:02 ` Helge Bahmann [this message]
2006-11-16 16:27 ` J. Bruce Fields
2006-11-17 8:22 ` Helge Bahmann
2006-11-17 18:44 ` J. Bruce Fields
2006-11-19 17:31 ` Helge Bahmann
2006-11-19 17:40 ` J. Bruce Fields
2006-11-17 11:38 ` Helge Bahmann
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=200611161702.38857.hcb@chaoticmind.net \
--to=hcb@chaoticmind.net \
--cc=kwc@citi.umich.edu \
--cc=nfs@lists.sourceforge.net \
/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