Bug 11416
| Summary: | /etc/profile changes umask and environment | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Kjetil T. Homme <kjetilho> |
| Component: | setup | Assignee: | Bill Nottingham <notting> |
| Status: | CLOSED WORKSFORME | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.1 | CC: | 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: | 2000-05-15 10:09:46 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: | |||
Overriding system default variables (such as umask) works fine for me here by editing $HOME/.bashrc, etc. We use a generalized but relatively expensive (~.5sec) method for setting up the environment, and therefore make sure that the environment is set up only once. We've done it this way for ten years on other Unixen, so your workaround simply isn't an option here. I think this is more a matter of principle, though: System policy like this should not be put in /etc/profile. Put it in /etc/skel or perhaps /etc/profile.d/policy*, to make it easier to override. Put your settings in ~/.bash_profile. They are set only once ( at login ) and they are inherited by all subprocesses. |
Our users typically set up their environment and umask once, and let all subprocesses of their session manager inherit those values. This is foiled by /etc/profile, which unconditionally sets the umask. Please put this check in the /etc/skel files instead. The scripts also muck with the environment variables. It would be good if you used the idiom VAR=${VAR:-"value"} to avoid stomping on the environment already set up.