Bug 224083 – pdksh does not load ~/.profile

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 224083 - pdksh does not load ~/.profile

Summary:	pdksh does not load ~/.profile

Status:	CLOSED WORKSFORME

Aliases:	None

Product:	Red Hat Enterprise Linux 4
Classification:	Red Hat
Component:	pdksh (Show other bugs)
Sub Component:
Version:	4.4
Hardware:	x86_64 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Karsten Hopp
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2007-01-23 18:10 EST by Chris Naude
Modified:	2007-11-16 20:14 EST (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2007-01-24 04:41:48 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Chris Naude 2007-01-23 18:10:30 EST

Description of problem:


Version-Release number of selected component (if applicable):
Version 5.2.14
Release 30.3

How reproducible:
Every time I login this occurs

Steps to Reproduce:
1. Create ~/.profile with custom settings
2. Switch to ksh or login with ksh
3. 
  
Actual results:
The ~/.profile is never read

Expected results:
The ~/.profile needs to be sourced according to the man pages

Additional info:

Comment 1 Karsten Hopp 2007-01-24 04:41:48 EST

How are you testing this ?
Please note that you either need to set your login shell to /bin/ksh with the
chsh command or you need to start ksh with the '-l' parameter to make it a login
shell.

Both ways work for me on RHEL-4.4 with pdksh-5.2.14-30.3
p.e.
> cat ~/.profile
echo running $HOME/.profile
> ksh -l
running /home/karsten/.profile
>

Comment 2 Chris Naude 2007-01-24 10:26:26 EST

I created another LDAP account and it works as it's supposed to. I tested it on
several other machines and it works correctly. The issue seems to be specific to
one LDAP account on one machine. Thanks for your assistance.

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