From: Piotr Szczap <szczapu@poczta.onet.pl>
To: linux-admin@vger.kernel.org
Subject: nss-mysql + chroot
Date: Fri, 04 Nov 2005 21:26:19 +0100 [thread overview]
Message-ID: <436BC3EB.1010802@poczta.onet.pl> (raw)
Hello list,
I have a problem with using nss-mysql and doing chroot. We are trying to
set up an FTP server on a system that is using nss-mysql for
authentication. We have set up the FTP server so that it chroot's to
user's home dir after the user authenticates. The problem is that when
the user lists files in his/her directory the username is displayed as
(?), eg:
drwxr-x--- 2 (?) ftp_corusant 4096 Feb 1 2005 sw0017
drwxr-x--- 3 (?) ftp_corusant 4096 Sep 21 21:30 sw0023
This happens because after the chroot operation FTP server looses access
to nss-mysql* files in /etc and so it cannot connect to the database.
However, if a user is in the local user database(/etc/passwd) his/her
name is displayed OK.
I'm out of ideas:( Could anyone suggest a workaround/solution other than
copying nss-mysql* file into user's directory??
TIA
Piotr Szczap
reply other threads:[~2005-11-04 20:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=436BC3EB.1010802@poczta.onet.pl \
--to=szczapu@poczta.onet.pl \
--cc=linux-admin@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).