Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: With latest FC5 update testing selinux stuff: nome$ homedir /bin/false or its parent directory conflicts with a defined context in /etc/selinux/targeted/contexts/files/file_contexts, /usr/sbin/genhomedircon will not create a new context. myrddraal$ homedir /bin/false or its parent directory conflicts with a defined context in /etc/selinux/targeted/contexts/files/file_contexts, /usr/sbin/genhomedircon will not create a new context. coop01$ homedir /bin/false or its parent directory conflicts with a defined context in /etc/selinux/targeted/contexts/files/file_contexts, /usr/sbin/genhomedircon will not create a new context. coop00$ homedir /bin/false or its parent directory conflicts with a defined context in /etc/selinux/targeted/contexts/files/file_contexts, /usr/sbin/genhomedircon will not create a new context. I really don't know what is trying to happen here. I our configuration, we use NIS for users, automount /home from the central server, and use samba. The above users are machine accounts for the samba domain. Perhaps nothing to worry about, but thought I'd report. Version-Release number of selected component (if applicable): selinux-policy noarch 2.2.25-2.fc5 updates-testing 407 k selinux-policy-targeted noarch 2.2.25-2.fc5 updates-testing 472 k How reproducible: Several machies reported the same.
This looks like the python is acting incorrectly. How many fields does ypcat passwd show per record? Looks like it thinks the homedir directory is the shell directory at least for these records Dan
Whoops, my bad. Incorrect passwd entries: nome$:x:6388:501:/dev/null:/bin/false: versus lynx$:x:6381:501::/dev/null:/bin/false Sorry about that.