Bug 197367 - Shell locks up when doing "cd ~username"
Summary: Shell locks up when doing "cd ~username"
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: 389
Classification: Retired
Component: Directory Server
Version: 1.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Rich Megginson
QA Contact: Chandrasekar Kannan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-06-30 16:46 UTC by Ryan Lim
Modified: 2015-01-04 23:20 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-07-15 00:16:55 UTC
Embargoed:


Attachments (Terms of Use)

Description Ryan Lim 2006-06-30 16:46:08 UTC
Description of problem:
There is a problem when (in the shell) performing a "cd ~username". I get some
sort of object printout and the shell (tcsh-6.13-9) then becomes unusable.
Control-C does not terminate the current process. I have not tested/verified
this with other shells.


Version-Release number of selected component (if applicable):
- Fedora Directory Server 1.0.2
- tcsh-6.13-9

How reproducible:
This happens ocassionally on my setup.

Steps to Reproduce:
1. cd ~user

  
Actual results:
root@snowshoe ~# cd ~username/
0cdc=XXX,dc=YYY,dc=ZZZ
.
 bjectclass
           posixAccountuiusername0iuid
                                      userPassword      uidNumber      
gidNumbehomeDirectory
loginShellgecos
               description
                          objectClass

Shell then becomes unusable.


Expected results:
To change directory to the user (username)'s home directory.

Additional info:
This problem happens ocassionally. I do not know what triggers this.

Comment 1 Rich Megginson 2006-07-18 21:01:47 UTC
Are you sure this is a problem with Fedora DS?  Does this work fine with other
Directory Servers?  Have you verified that your pam/nss/autofs configuration is
correct?

Comment 2 Ryan Lim 2006-08-03 12:30:34 UTC
I have not tried other directory servers, but this much I know: my two identical machines using the same 
directory server, both exhibit the same behavior.

PAM/NSS were configured using system-config-authentication. Automount doesn't use ldap.

Comment 3 Rich Megginson 2008-07-15 00:16:55 UTC
This is not a directory server bug.


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