Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 161185 - Dropped connections causes bash to hang on nss lookups
Summary: Dropped connections causes bash to hang on nss lookups
Alias: None
Product: Fedora
Classification: Fedora
Component: nss_ldap
Version: 4
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2005-06-21 07:18 UTC by Enrico Scholz
Modified: 2008-02-17 02:56 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-02-17 02:56:24 UTC

Attachments (Terms of Use)

Description Enrico Scholz 2005-06-21 07:18:19 UTC
Description of problem:

When having an LDAP server which drops connections after a certain timeout, bash
will hang at actions like 'cd ~foo<tab>'. At this time, a lot of connections like

| tcp 1  0          CLOSE_WAIT

are shown by netstat.

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


How reproducible:


Steps to Reproduce:
1. setup NSS to use LDAP as passwd backend
2. setup the LDAP server to timeout after a certain time (e.g. 'idletimeout 900')
3. start a bash
4. type in 'cd ~foo' and press TAB
5. wait some time...
6. type in 'cd ~foo' and press TAB

Actual results:

bash hangs at step 6; 'strace' shows that it waits in a futex(2) syscalls.

Expected results:

bash expands 'foo' both in 4 and 6

Additional info:

nscd is NOT running; LDAP is not configured for TLS

Comment 1 Christian Iseli 2007-01-22 11:40:14 UTC
This report targets the FC3 or FC4 products, which have now been EOL'd.

Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?


Comment 2 petrosyan 2008-02-17 02:56:24 UTC
Fedora Core 4 is no longer maintained.

Setting status to "INSUFFICIENT_DATA". If you can reproduce this bug in the
current Fedora release, please reopen this bug and assign it to the
corresponding Fedora version.

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