[422] in Kerberos
short Kerberos ticket times
daemon@TELECOM.MIT.EDU (Craig Finseth)
Tue Jul 5 11:12:33 1988
From: fin@uf.msc.umn.edu (Craig Finseth)
To: kazar+@andrew.cmu.edu, kerberos@ATHENA.MIT.EDU
In-Reply-To: Mike Kazar's message of Fri, 1 Jul 88 14:23:52 -0400 (EDT) <cWmxWsy00Uk-M250V2@andrew.cmu.edu>
We are wondering about the short times ourselves. In our environment,
it is not unusual to have a single "batch" job (i.e., detached shell
script) run for over two weeks. This job will have been
checkpoint/restarted several times during its lifetime. In some
cases, the job may be held for over a day before it is restarted.
Is it reasonable to ask that a researcher log in once each day so that
their job doesn't stop?
We checkpoint/restart jobs during system maintenance time (like 2 to 5
AM). For jobs that started before 8 AM the previous day, do we have
to tell our researchers "sorry, but you have to get up an log in in
order to make use of the early morning time?"
We haven't gotten far enough to actually encounter this problem in
real life: we are just "looking for trouble" that we may encounter
down the road.
Any ideas?
Craig A. Finseth fin@uc.msc.umn.edu [CAF13]
Minnesota Supercomputer Center, Inc. (612) 624-3375
