From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031114 Description of problem: This is actually from the apcupsd-users mailing list. Execute as root /proc/1/environ truncates HOME to OME for some reason. This can mess up scripts at init time which need a correct HOME directory. Version-Release number of selected component (if applicable): SysVinit-2.85-5 How reproducible: Always Steps to Reproduce: 1.tr '\0' '\n' < /proc/1/environ The output will read OME=/ TERM=linux instead of the correct HOME=/ TERM=linux Actual Results: Truncated HOME to OME Expected Results: HOME should have been printed. Additional info:
Actually, I'm not seeing HOME set at all in init's environment here.
Odd. I see OME in init's environment on all of my FC1 systems, both those installed from the original FC1 CDs and then kept up to date via Yum and those which I installed from the KRUD distribution. In any event, if I understood the point of the post to apcupsd-users, HOME needs to be set in init's environment for apcupsd, at least, to work properly. I was going to link to the original post here, but the apcupsd-users mailing list archive on sourceforge seems not to have been updated since May 28.
While I'm working into integrating it in the head branch, care to try the patch in bug 125172? It should fix it for you.
Should be fixed in 2.85-28.
The suggested patch fixes the problem, thanks.
Package name is now sysvinit in latest Fedora.