[31915] in Kerberos
K5start: best startup strategy?
daemon@ATHENA.MIT.EDU (Jaap Winius)
Wed Jan 13 17:31:33 2010
From: Jaap Winius <jwinius@umrk.nl>
MIME-Version: 1.0
Date: 13 Jan 2010 18:51:52 GMT
Message-ID: <4b4e1648$0$28796$e4fe514c@dreader15.news.xs4all.nl>
To: kerberos@mit.edu
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu
Hi folks,
After a experimenting with k5start v3.15 for a while, I've noticed that
it usually starts up for me during the boot process, but not always
(perhaps due to a flaky Kerberos server). My simple startup script looks
like this:
#!/bin/sh
/usr/local/bin/k5start -U -f /etc/krb5.keytab -b -K 10 -l 24h \
-k /tmp/krb5cc_105 -o openldap
exit 0
I use Debian lenny and created a symlink for it, /etc/rc2.d/S18k5start,
that is supposed to start it up just before /etc/rc2.d/S19slapd.
Of course, it's possible to write another script to perform a check later
on (or perhaps even periodically), to see if k5start is actually (still)
running, and if not, attempt to start it up again, but I'm hoping to
avoid such a workaround.
Has anyone else experienced and attempted to address this problem, or
have I just done something stupid?
Thanks,
Jaap
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
