Bug 7221
Summary: | ".profile" files are not executed for non-bash shells under X window | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | John Horne <john.horne> |
Component: | gdm | Assignee: | Elliot Lee <sopwith> |
Status: | CLOSED WORKSFORME | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.1 | ||
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-24 20:06:36 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: |
Description
John Horne
1999-11-22 10:34:03 UTC
The current approach for setting up the environment when one logs in via a graphical login appears to be to start scripts with #!/bin/bash -login and assume that everyone uses bash or something compatable enough, and writes their login dotfiles nicely, so that 'bash -login' will work. As you've noticed, this doesn't always fly (especially for people using login shells, such as tcsh, that don't use .profile et al at all). Remember to specify that each kterm is to be a login shell - then you'll avoid the problem This isn't a ksh problem - we are aware of it (and have been so for some time), and are thinking about how to fix this (not just ksh...). I think gdm is a better candidate component. Elliot - is gdm the answer to this problem? What do you think? Since the 'Xsession' script uses 'bash -login', things should be initialized correctly AFAIK. I don't see any csh- or bash-specific logic other than assuming that bash can initialize things correctly. |