[OpenAFS] OpenAFS implementation questions.
Thu, 25 May 2006 12:46:51 -0700
Thanks for the quick reply! =)
These users are coming in through SSh and often launching jobs that
run in the background. there really isn't room for running reauth and
Plus the hope is to put this on the cluster where jobs sit queued for
ages before running. The user would have no ability to authenticate
Hope this clarifies things a bit.
On May 25, 2006, at 12:32 PM, Derek Atkins wrote:
> Have your users run reauth? That will automatically get them new
> tickets and tokens.. Or tie into the screensaver!
> Quoting Brady Catherman <firstname.lastname@example.org>:
>> I am currently considering moving our environment to OpenAFS but
>> before I can switch I need to make sure a few things are going to
>> keep working..
>> We have users that use or systems for months on end without
>> logging off and I am concerned that the kerberos ticket they are
>> being issued will expire. Having them log back into kerberos/
>> openafs isn't really a good option for us (I am having a hard
>> enough time selling even the basic conversion, let alone anything
>> that requires user action!)
>> Is there an easy way around this with OpenAFS? I have tried
>> setting the length of our kerberos tickets higher but the most it
>> will give me is 7 days. Is there another way to do this?
>> OpenAFS-info mailing list
> Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
> Member, MIT Student Information Processing Board (SIPB)
> URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
> warlord@MIT.EDU PGP key available
> OpenAFS-info mailing list