Bug 83527 - empty argument to /sbin/initlog at the top of rc.sysinit
empty argument to /sbin/initlog at the top of rc.sysinit
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
8.0
All Linux
low Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-02-05 04:42 EST by SEKINE Tatsuo
Modified: 2014-03-16 22:34 EDT (History)
1 user (show)

See Also:
Fixed In Version: 7.31-1
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-09-03 21:49:28 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description SEKINE Tatsuo 2003-02-05 04:42:59 EST
Description of problem:

The first valid line of rc.sysinit are:

    if [ -z "$IN_INITLOG" -a -x /sbin/initlog ]; then
        exec /sbin/initlog $INITLOG_ARGS -r /etc/rc.d/rc.sysinit
    fi

/sbin/initlog doesn't define INITLOG_ARGS variable, 
and no configuration file (like /etc/init.d/functions) is not imported
at this time.

Therefore INITLOG_ARGS variable is not defined
except kernel command line such as
  ro root=LABEL=/12 INITLOG_ARGS=-q

Probably, /etc/init.d/functions file should be imported at the top of
rc.sysinit script or other scheme to configure INITLOG_ARGS should be
requierd to reflect BOOTUP configuration (defined in /etc/sysconfig/init).

Version-Release number of selected component (if applicable):
  initscripts-7.06

How reproducible:

Steps to Reproduce:
1.
2.
3.
    
Actual results:


Expected results:


Additional info:
Comment 1 Bill Nottingham 2003-02-05 12:54:00 EST
Is this causing errors for you?
Comment 2 Bill Nottingham 2003-02-05 12:57:55 EST
Actually, I'm thinking that the reference to initlog_args there can probably
just be removed.
Comment 3 SEKINE Tatsuo 2003-02-09 06:44:22 EST
Sorry, It's not BUG.
It doesn't cause any error.

I change severity to "enhancement".

Comment 4 Bill Nottingham 2003-09-03 21:49:28 EDT
Fixed in 7.31-1, thanks!

Note You need to log in before you can comment on or make changes to this bug.