On 04/24/2013 07:50 AM, Johan Vermeulen wrote:
> Dear All,
>
> I'm currently troubleshooting NetworkManger scripts.
>
> I see a difference in machine A :
>
> drwxr-xr-x 2 root root 4096 apr 24 16:33 .
> drwxr-xr-x 5 root root 4096 jan 9 12:13 ..
> -rwxr-xr-x 1 root root 175 jan 9 12:13 00-netreport
> -rwxr-xr-x 1 root root 335 okt 22 2012 04-iscsi
> -rwxr-xr-x 1 root root 345 jan 9 12:13 05-netfs
> -rwxr-xr-x 1 root root 926 sep 25 2012 10-dhclient
> -rwxr-xr-x 1 root root 301 apr 24 15:58 20-backuplauncher
> -rwxr-xr-x 1 root root 220 jun 22 2012 yum-NetworkManager-dispatcher
>
> and machine B:
>
> drwxr-xr-x. 2 root root 4096 apr 24 16:34 .
> drwxr-xr-x. 5 root root 4096 apr 23 12:06 ..
> -rwxr-xr-x. 1 root root 175 jan 9 12:13 00-netreport
> -rwxr-xr-x. 1 root root 345 jan 9 12:13 05-netfs
> -rwxr-xr-x. 1 root root 926 sep 25 2012 10-dhclient
> -rwxr-xr-x. 1 root root 326 apr 23 13:42 15-nfslauncher
> -rwxr-xr-x. 1 root root 307 apr 24 16:10 20-backuplauncher
> -rwxr-xr-x. 1 root root 220 jun 22 2012 yum-NetworkManager-dispatcher
>
> the difference being -rwxr-xr-x and -rwxr-xr-x.
>
> so with or without a dot (.)
>
> Does that mean anything?
Hi Johan,
From "info coreutils", section 10.1.2 (What information is listed):
Following the file mode bits is a single character that specifies
whether an alternate access method such as an access control list
applies to the file. When the character following the file mode
bits is a space, there is no alternate access method. When it is
a printing character, then there is such a method.
GNU `ls' uses a `.' character to indicate a file with an SELinux
security context, but no other alternate access method.
A file with any other combination of alternate access methods is
marked with a `+' character.
My first guess would be that Machine A has SELinux disabled, but Machine
B has (or had at some point) SELinux enabled.
-Greg
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
