From: "Will Rogers" <wjr@wam.umd.edu>
To: <gentoo-dev@cvs.gentoo.org>
Subject: RE: [gentoo-dev] Normal user login with ProFTPd?
Date: Sun Aug 19 22:56:02 2001 [thread overview]
Message-ID: <003a01c12934$638a70e0$0801a8c0@saucer> (raw)
In-Reply-To: <20010819224152.A13649@ares.dolly-llama.org>
<snip trouble with logging in non-anonymously to proftpd>
> I can log in as a normal user just fine
>
...
> User blutgens logged in.
> Logged in to localhost
>
> I'd like to help but it's nearly impossible if I can't duplicate it.
After several hours of fiddling and searching the web, I fixed it. I
found some similar problems mentioned on www.geocrawler.com and I put a
'RequireValidShell off' line in my proftpd.conf... and WHAM! It
worked.
Sheesh.
Now, _why_ does that work?
Will Rogers, who is going to sleep now.
wjr@wam.umd.edu
next prev parent reply other threads:[~2001-08-20 4:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-19 17:48 [gentoo-dev] Normal user login with ProFTPd? Will Rogers
2001-08-19 19:39 ` Chad Huneycutt
2001-08-19 21:10 ` Will Rogers
2001-08-19 21:42 ` Ben Lutgens
2001-08-19 22:56 ` Will Rogers [this message]
2001-08-20 2:48 ` Thomas M. Beaudry
2001-08-20 7:21 ` Will Rogers
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='003a01c12934$638a70e0$0801a8c0@saucer' \
--to=wjr@wam.umd.edu \
--cc=gentoo-dev@cvs.gentoo.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