On 01/04/2012 05:06 AM, Stephen Gallagher wrote:
I see the users and can log in etc,
however every client machine fails to shut down after being configured
Hmm, that's interesting. If it's only happening once the ipa client
install is done, then it's probably an SSSD issue.
I think it could be the certmonger service but I haven't had any
confirmation yet, although the maintain says it works in rawhide. I've
opened a BZ with the package maintainer
https://bugzilla.redhat.com/show_bug.cgi?id=771222
If I manually stop the certmonger.service... actually manually stopping
certmonger.path is sufficient. For example:
systemctl stop certmonger.path
then the systems shut down quite happily. I haven't done anything
special to these clients, just vanilla installs of F16 in a VM for testing.
Do you have any way of identifying which applications are still running
at that point?
That's a good question. I just figured the above out by trial and error.
At that point in the shut down, almost everything has been stopped so
I'm not sure I have much visibility on what's going on but that's
probably my lack of in-depth knowledge about systemd and it's
bewildering array of options.
--
Ian Chapman.
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
