Jason Edgecombe wrote:
We have users who need to run long-running jobs and store their files in
AFS during the run.
I've read the k5start and k5renew man pages, but I don't see how I can
have users type in their password when they start a job and have the
tickets and tokens keep being
On Sat, Feb 28, 2009 at 11:40:26PM -0500, Jason Edgecombe wrote:
I guess setting things for renewable tickets longer than 7 days or
running the jobs in local disk will be easiest.
We have a 7 day normal/renewable lifetime. What length do other sites have?
I have seen sites use on the order
Nicolas Williams wrote:
On Sat, Feb 28, 2009 at 11:40:26PM -0500, Jason Edgecombe wrote:
I guess setting things for renewable tickets longer than 7 days or
running the jobs in local disk will be easiest.
We have a 7 day normal/renewable lifetime. What length do other sites have?
On Mon, Mar 02, 2009 at 09:02:59PM -0500, Jason Edgecombe wrote:
Nicolas Williams wrote:
I have seen sites use on the order of months for the renewable ticket
lifetime, but still hours for normal ticket lifetime. If you already
use seven days for renew life you might as well double it --
Ken Raeburn wrote:
On Feb 6, 2009, at 11:31, Anh Nguyen wrote:
Hi,
Sorry for the following newbies questions, but thanks in advance for
your comments and suggestions:
1. Could we set up multiple KDC per single realm?
Absolutely; at most sites I think it's the normal way of doing
things.
