Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have configured vsftpd with the "text_userdb_names=YES" option, which is expected to put user and group names into the listing. The server is configured with nscd and ldap. The users are chrooted into a 'general root' directory, but that doesn't affect the result (not chrooting still fails).

The problem: obvious timeouts and unsuccessful resolving of 'group names'. The 'ls' output contains correct usernames but instead of a groupname there is a number.

share|improve this question
up vote 1 down vote accepted

The new vsftpd uses a clone() with CLONE_NEWNET parameter instead of fork(). This puts the process accessing the files into a separate networking environment that cannot access any network. Neither the nscd unix socket, nor the ldap servers. If you strace the process, you will see only errors trying to access the servers:

Solution: set the following undocumented parameter in the vsftpd.conf:


This will revert vsftpd to use the fork() and everything works perfectly.

Additional note: In the chroot environment one should use nscd (you have to mount --bind /var/run/nscd into /chroot/var/run/nscd). It doesn't help.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.