This service will be undergoing maintenance at 00:00 UTC, 2016-08-01. It is expected to last about 1 hours
Bug 164112 - ksh not run as login shell when logging in via gdm
ksh not run as login shell when logging in via gdm
Status: CLOSED INSUFFICIENT_DATA
Product: Fedora
Classification: Fedora
Component: gdm (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ray Strode [halfline]
Mike McLean
:
Depends On:
Blocks: FC5Target
  Show dependency treegraph
 
Reported: 2005-07-24 22:23 EDT by Mike MacCana
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-05-05 17:04:29 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Mike MacCana 2005-07-24 22:23:47 EDT
Description of problem:
Logging this on behalf of a GLS customer, tho I can reproduce this here.

Logging in via gdm does not run a login shell for ksh users. Instead a non-login
shell is run. The users ~/.profile script is never run.

How reproducible:
Always

Steps to Reproduce:
1.Pop something in a users .profile. 
2. Log into X
  
Actual results:
The .profile is never run.

Expected results:
gdm should start a login shell, as it does with other shells, and as other login
apps do for ksh.

Additional info:
Comment 2 Ray Strode [halfline] 2006-01-11 16:28:26 EST
Hi Mike,

The session start up scripts do:

exec -l $SHELL -c <the session scripts>

There is a convention amoung shells that if the shell is invoked with the first
character of argv[0] as - (and then the normal argv[0]) then the shell should
execute as a login shell.

It's possible ksh doesn't follow this convention.  If it doesn't it should be fixed.
Comment 3 Karsten Hopp 2006-02-22 05:33:00 EST
from the ksh manpage: 
If the shell is invoked by exec(2), and the first character of argument 
       zero ($0) is -, then the shell is assumed to be a login shell and  com- 
       mands  are  read from /etc/profile and then from either .profile in the 
       current directory or $HOME/.profile, if either file exists. 
 
I've added an echo in /etc/profile and ~/.profile to see if ksh runs those 
scripts: 
hagen:[~] >exec -l ksh - 
executing /etc/profile 
executing ~/.profile 
 
 
Looks ok to me. 
Comment 4 Ray Strode [halfline] 2006-02-23 19:46:20 EST
Mike have you tried test3?  if so, do you still see this problem?
Comment 5 John Thacker 2006-05-05 17:04:29 EDT
Closing due to lack of response.

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