Ok. Output from truss -cp
syscall seconds calls errors
_exit.000 1
read .000 7
write.005 50
close.000 16 6
time .002 94
brk
Will do.
For the time being we are working with a conservative client and so we
are stuck at v1.3.3g for the time being.
cheers,
Rob
On 14 March 2013 17:03, TJ Saunders wrote:
>
>> Thanks for this, it is similar, but our issue is that the underlying
>> stat calls are taking so long that the dat
Damn.
Forgot to say that this is for 10,000 zero length files created using a
script running touch so they are all owned by the one user.
There are also about 20 non-zero length files in the dir.
cheers,
Rob
On 14 March 2013 17:36, Robert Wells wrote:
> Ok. Output from truss -cp
>
> sys
G'day TJ,
Thanks for this, it is similar, but our issue is that the underlying
stat calls are taking so long that the data connection that has been
opened is hitting the expiry of the timeout_stalled timer.
Ascii conversion will help to some extent, but we have so many files
that doing all those
> For the time being we are working with a conservative client and so we
> are stuck at v1.3.3g for the time being.
Hmm. I could try to backport the fixes for Bug#3819 to that proftpd
version, so that you can verify whether those are indeed the root cause of
the problem. Unless your files are
> Thanks for this, it is similar, but our issue is that the underlying
> stat calls are taking so long that the data connection that has been
> opened is hitting the expiry of the timeout_stalled timer.
Could you provide syscall data (strace, ktrace, etc) of the issue you're
seeing -- using prof
> Looking in modules/mod_ls.c at the functions dolist() and ls_nlst() I
> can see that the data connection is opened and the TimeoutStalled
> timer is started before the file data is gathered. In the case of one
> of our users, it takes around 20 minutes for an ls -l to complete at
> the command l
G'day there,
I've just posted a query to the Proftpd user list regarding badly
behaved clients, and users, timing out when they try to do a long
listing of a large number of files. (It's actually awaiting moderator
input atm because I've only just signed up to that list).
Looking in modules/mod_l
