Bug 811537 - dracut passes on PWD and SHLVL env vars to systemd
dracut passes on PWD and SHLVL env vars to systemd
Status: CLOSED WONTFIX
Product: Fedora
Classification: Fedora
Component: dracut (Show other bugs)
17
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: dracut-maint
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-04-11 07:09 EDT by Lennart Poettering
Modified: 2012-04-11 07:19 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-04-11 07:19:57 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Lennart Poettering 2012-04-11 07:09:26 EDT
dracut-017-62.git20120322.fc17.noarch

Not sure whether bash or dracut is to blame here, but for some reason it seems that systemd when invoked gets PWD=/ and SHLVL=0 passed in the env block which is then inherited to all system services. And we probably shouldn't do that...

This can easily be checked with "cat /proc/1/environ"
Comment 1 Lennart Poettering 2012-04-11 07:19:57 EDT
Hmm, so it seems that bash always implicitly exports "PWD", "SHLVL" and "_". See comments in:

http://lists.busybox.net/pipermail/busybox-cvs/2009-September/029857.html

Given that people might actually invoke us with an exec from an init=/bin/sh boot it probably makes sense for systemd to unconditionally unset these env vars. Also, this behaviour seems to apply to both bash and the busybox shell, hence it's generic enough to be something to unset in systemd. 

I guess that means that there's nothing to fix in dracut. Closing again. Sorry for the noise.

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