Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 121663

Summary: strange boot message when rc.sysinit starts to run
Product: [Fedora] Fedora Reporter: Brian Millett <bmillett>
Component: initscriptsAssignee: Bill Nottingham <notting>
Status: CLOSED DUPLICATE QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: cacruden, rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 19:02:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 114961    

Description Brian Millett 2004-04-25 00:46:28 UTC
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

Comment 1 Craig Cruden 2004-04-29 12:24:34 UTC
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?

Comment 2 Craig Cruden 2004-05-01 16:40:12 UTC
Looks similar to another FC Blocker bug:

121143 [NEW - normal - notting] "Invalid argument" from
initscripts.

Comment 3 Bill Nottingham 2004-05-03 00:57:17 UTC

*** This bug has been marked as a duplicate of 121143 ***

Comment 4 Red Hat Bugzilla 2006-02-21 19:02:45 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.