From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a) Gecko/20040422 Firefox/0.8.0+ Description of problem: cat: /proc/self/attr/current: Invalid argument is the message seen. I am booting with selinux=0. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.boot 2.read screen 3. Actual Results: cat: /proc/self/attr/current: Invalid argument Expected Results: no message about "invalid argument" Additional info: code in rc.sysinit is: # Check SELinux status selinuxfs=`awk '/ selinuxfs / { print $2 }' /proc/mounts` SELINUX= if [ -n "$selinuxfs" -a "`cat /proc/self/attr/current`" != "kernel" ]; then if [ -r $selinuxfs/enforce ] ; then SELINUX=`cat $selinuxfs/enforce` else # assume enforcing if you can't read it SELINUX=1 fi fi
I have seen the same "problem" on bootup.... After bootup I decided to execute "cat /proc/self/attr/current" at the shell, and received the same: "cat: /proc/self/attr/current: Invalid argument". I checked the file and it exists with 0 bytes [rw-rw-rw-]. I decided to create another file in my home directory [text.txt] with zero bytes [touch text.txt] and then execute "cat text.txt".... no error. Could this be related to something special about the "proc" filesystem?
Looks similar to another FC Blocker bug: 121143 [NEW - normal - notting] "Invalid argument" from initscripts.
*** This bug has been marked as a duplicate of 121143 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.