> Linux customers are reporting that they cannot get files - No such file
> or directory. We are able to reproduce the problem on Solaris and
> Linux clients but Windows clients are able to get files with no problem.
>
> The private directory is where the problem has been reported and if we
> comment out
>
>
> DenyAll
>
> the Unix clients are able to get files.


This suggests that the Unix clients are using LIST (or NLST) for checking
for file existence first. I also suspect a difference in the clients
between requesting the file by full path (versus by relative path).

There are some subtle bugs in the per-directory configuration lookup that
fortunately don't crop up too often, but you may be running into them.

To verify this, could you supply proftpd debug logging, from both a
Windows client session and a Unix client session?

TJ

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The last temptation is the greatest treason:
To do the right deed for the wrong reason.

-T.S. Eliot

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?p...rge&CID=DEVDEV
_______________________________________________
ProFTPD Users List
Unsubscribe problems?
http://www.proftpd.org/list-unsub.html