Re: ftp errors

[Kevin Colby <kevinc grainsystems com>]

> > > > Does "ls" works when logged in as anonymous or as yourself?
> > > > Does "ls -al" work during the same login that "ls" doesn't?
> > > >
> > >         [Burke, Thomas G.]  Yes.  Actually, ls works, it just says "No
> > files
> > > found" (as if the directory were empty...  I checked, and all
> > > files/directories have at least 755 permissions...  This is under any
> > login
> > > (anonymous or otherwise) when the user is sitting in the /home/ftp
> > > directory...  In certain other directories, it works fine.  (my own home
> > > directory, for instance).
> >
> > This happens for anonymous or your own user?  both?
> > Are you doing "ls /somedir" or "cd /somedir; ls"?  Does the cd work?
> >
> > There are only a few things going on here, really.  If ls works
> > at all for that user, then it should work everywhere.  However,
> > if a directory were set to "no read", the files would become
> > invisible.  If you try to "cd /somedir", that directory may also
> > not be accessible as anonymous because of the chroot to the
> > anonymous home directory that ftpd does.
>
>         [Burke, Thomas G.]  Happens for my user, and anonymous user in
> /home/ftp directory.
> 
>         I can cd to any normal directory.
>         ls in /home/ftp or /home/ftp/pub gives the response "No Files Found"
>         ls -al shows all files in the normal ls -al format...
>         permissions on all files include 755....

ls (in ftp) shows "no files found", but ls -al (in ftp) shows the files,
or are you talking about a shell session?  These files don't happen to
have a "." as the first character in the name, do they?
What about permissions on /home/ftp/pub itself?

	- Kevin Colby
	  kevinc grainsystems com