lynn said the following on 05/02/2013 03:06 AM:
12.3 client joined to AD
Hi everyone This is my first battle with systemd so please be patient. It may not be systemd. I'm tired of having to work around this one.
The clients need a root ticket on boot. Here's the content of /etc/init.d/boot.local
sssd kinit -k -t /etc/krb5.keytab CATRAL$
How about making that sssd || { logger "sshd failed at boot.local" ; exit 10 } kinit -k -t /etc/krb5.keytab CATRAL$ || { \ logger "kinit failed at boot.local"; \ exit 11 } it won't cost anything if all goes well and it will give you a better insight if things don't go well. Yes, I'm sully aware that you can set the shell with error handling, but this is logging of the where and what and individual exit codes. This kind of 'defensive programming' should be taken as "baseline good practice" throughout. Many people bemoan the change to systemd but if you look at the original sysvinit scripts they had expensive logging and testing for validity. Each one had to do it individually whereas systemd either absorbs that as a commonality or incorporates it into the structure. But once you get to 'customise' things you can't assume that systemd is some piece of AI that parses all you've written and figures stuff out. You do have to tell it about failures and dependencies. And you still have to write good shell code. Then and only then can you be sure that when you use the systemctl it is reporting correctly on that service. -- Don't think you are going to conceal thoughts by concealing evidence that they ever existed. Dwight D. Eisenhower, speech at Dartmouth College, June 14, 1953 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org