Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 150082 - environment of init process mangled ?
environment of init process mangled ?
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: SysVinit (Show other bugs)
i686 Linux
medium Severity low
: ---
: ---
Assigned To: Bill Nottingham
David Lawrence
Depends On:
Blocks: 156320
  Show dependency treegraph
Reported: 2005-03-02 05:03 EST by Antonio Dolcetta
Modified: 2014-03-16 22:52 EDT (History)
2 users (show)

See Also:
Fixed In Version: RHBA-2005-510
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-28 16:00:37 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2005:510 qe-ready SHIPPED_LIVE SysVinit bug fix update 2005-09-28 00:00:00 EDT

  None (edit)
Description Antonio Dolcetta 2005-03-02 05:03:39 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Gecko/20041116 Firefox/1.0

Description of problem:
running cat /proc/1/environ | tr "\000" "\n" returns:


the H charachter from the HOME variable is missing
I'm not sure what can cause this nor if it has any adverse effects,
just wanted to let you know

this is reproducible on my machine on every reboot

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

How reproducible:

Steps to Reproduce:
run the command:
cat /proc/1/environ | tr "\000" "\n"

Additional info:
Comment 1 Bill Nottingham 2005-03-02 11:39:08 EST
Comment 9 Red Hat Bugzilla 2005-09-28 16:00:37 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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