First of all I would like to thank all those who responded.
Rick von Richter <firstname.lastname@example.org>
Darren Dunham <email@example.com>
Barry Gamblin <firstname.lastname@example.org
"Christopher L. Barnard" <email@example.com>
"Evans, Tim" <Tim_Evans@troweprice.com>
Ric Anderson <ric@Opus1.COM>
Stacey Conrad <Stacey.Conrad@millersville.edu>
David Foster <firstname.lastname@example.org>
Derrick Daugherty <email@example.com>
Don Krause" <firstname.lastname@example.org>
Tim Carlson <email@example.com>
James Ford <firstname.lastname@example.org>
"Perrier,Kent - PLANO" <Kent.Perrier@Oneco.net>
Moti Levy <email@example.com>
Don Cary Grant <firstname.lastname@example.org>
Actually I failed to understand the ~ftp directory. My directory hierarchy
was as given below:
/export/home ......contained all home directories of ftp users.
/export/home/ftp .....anonymous ftp user home directory
/export/home/ftp/bin ..bin directory as mentioned in FAQ for wuftpd.
/export/home/ftp/usr .usr directory as mentioned in FAQ for wuftpd.
/export/home/ftp/etc ..etc directory as mentioned in FAQ for wuftpd.
/export/home/ftp/dev ..dev directory as mentioned in FAQ for wuftpd.
My mistake was that the user's home directories were not beneath the
/export/home/ftp directory which I was chrooting users to.
As soon as I received the replies from above said friends, I realized my
mistake. Then I chrooted users to /export/home directory and created bin, dev,
etc, usr directories beneath /export/home (not beneath /export/home/ftp). and
then everything worked fine. dir command is now functioning fine as is the
'ls' is built in to the binary, but 'dir' is done by calling the external
/usr/bin/ls program. Although I copied 'ls' and related libraries in bin and
usr/lib directories under /export/home/ftp yet these were not accessible by
ftp users as their home directories did not lie under the chrooted
Thank you very much once again for the support which enabled me to realize my
Original Post 2:
This is my 2nd mail. Thank you very much the prompts responses from so many
friends. Almost all the replies advised me to upgrade to wu-ftp version
which I have done. But still the problem exists.
After installation of wu-ftp version 2.6, I can log on successfully as a ftp
user, I can put or get successfully, I can do an "ls" and can see the files
successfully, but when I give dir command it apparently works fine ( I mean
does not give any error message) but it does not give any file listing. I am
running wu-ftp to allow users to upload their pages on the web server so I am
running in restricted mode. I want to give access to only guest users (not
anonymous or real local users).
If I do not run in restricted mode then "dir" works ok and gives the normal
directory listing. Is the dir command disabled in restricted mode? Is it that
much dangerous? It should not be....I beleive that it should work even in
Original Post 1:
We are an ISP and offer ftp accounts to users. I am running wu-ftp version
2.4.2 beta on solaris 2.6. The problem is that "dir" command is not
functioning in ftp session. Whereas "ls" is working fine. Most ftp clients
like Cute FTP use "dir" command so they do not run with our wu-ftp server.
Please advise on how to enable "dir" command in wu-ftp 2.4.2 beta.
I will summarize.
Get free email and a permanent address at http://www.netaddress.com/?N=1
U BEFORE POSTING please READ the FAQ located at
. and the list POLICY statement located at
A To submit questions/summaries to this list send your email message to:
A To unsubscribe from this list please send an email message to:
E and in the BODY type:
R unsubscribe sun-managers
. unsubscribe sun-managers email@example.com
L To view an archive of this list please visit:
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:14:21 CDT