Hi all,
A while ago, I figured out how to set up Debian lenny as a Kerberos and
LDAP client for user authentication and authorization. K5start is
important for this, because if the workstation cannot automatically
obtain a Kerberos ticket for itself as it boots up, it has no way to
On Sat, Jul 3, 2010 at 7:39 PM, Jaap Winius jwin...@umrk.nl wrote:
And if that's not bad enough, what can be done for all those laptop users
out there who are used to managing their network connections from their
desktops? In such cases, there may not be a network connection until
after they
Jaap Winius jwin...@umrk.nl writes:
However, a lot of this depends on how init behaves: if it runs k5start
before the network comes up, the process will fail and the user will not
be able to log in. I had this experience recently with Ubuntu 10, which
uses a replacement init, called upstart.
On Mon, 05 Jul 2010 22:59:31 +0200, Natxo Asenjo wrote:
apparently sssd https://fedorahosted.org/sssd/ should take care of that.
I read this recently:
http://people.skolelinux.org/pere/blog/
Caching_password__user_and_group_on_a_roaming_Debian_laptop.html
It looks like sssd and
On Mon, 05 Jul 2010 14:05:31 -0700, Russ Allbery wrote:
How are you invoking k5start under initctl (what flags, in other words)?
Hi Russ!
This is my /etc/init/kstart.conf that I used on Kubuntu lucid:
start on filesystem
stop on runlevel S
expect fork
respawn
respawn limit 20
Jaap Winius jwin...@umrk.nl writes:
This is my /etc/init/kstart.conf that I used on Kubuntu lucid:
start on filesystem
stop on runlevel S
expect fork
This doesn't look right. k5start doesn't fork unless you use the -b flag
to tell it to daemonize itself.
The logs did report
