Wolfgang S. Rupprecht wrote:
Daniel J Walsh <dwalsh@xxxxxxxxxx> writes:
Wolfgang S. Rupprecht wrote:
# ll -a --lcontext /u
total 120
drwxr-xr-x 14 root:object_r:root_t:s0 root root 4096 2007-06-08 16:37 .
drwxr-xr-x 30 system_u:object_r:root_t:s0 root root 4096 2007-06-18 08:59 ..
drwxr-xr-x 86 root:object_r:root_t:s0 alison alison 4096 2007-06-08 11:02 alison
drwxr-xr-x 2 root:object_r:root_t:s0 root root 4096 2006-11-30 10:51 CVS
drwxr-xr-x 35 root:object_r:root_t:s0 cvs staff 4096 2006-11-21 12:52 cvsroot
drwxr-xr-x 24 root:object_r:root_t:s0 wolfgang staff 4096 2000-08-29 11:22 gps
drwxr-xr-x 3 root:object_r:root_t:s0 laine laine 4096 2006-10-26 15:15 laine
drwxr-xr-x 3 root:object_r:root_t:s0 marc marc 4096 2006-10-26 15:15 marc
drwxrwxr-x 22 root:object_r:root_t:s0 root wheel 4096 2007-06-15 10:35 src
drwxr-xr-x 273 root:object_r:root_t:s0 wolfgang wolfgang 12288 2007-06-18 09:04 wolfgang
drwxrwxr-x 17 root:object_r:root_t:s0 root wsrcc 4096 2007-04-04 08:34 www
restorecon -R -v /root
Its the user's directories located in /u (instead of /home) that need
the restorecon. (The /home directory is automounted.) I suspect I
need to copy something in restorecon's database so that it knows that
/u contains home directories.
The underlying problem with the rpm db locks failing after a few hours
of uptime is what concerns me more. It seemed to be selinux related
since turning off selinux fixed the lock leakage.
-wolfgang
semanage fcontext -a -t home_root_t /u
semanage fcontext -a -t user_home_dir_t -f-d /u/[^/]*
semanage fcontext -a -t user_home_t /u/[^/]*/.+
should clean that up
Yes if the rpm problem happens in permissive mode it should be reported
as a bug to rpm.
