Justin Piszcz wrote:
Mog,
I believe it is for all data transmissions within the lftp session:
net:limit-total-rate (bytes per second)
limit transfer rate of all connections in sum. 0
means unlim-
ited. You can specify two numbers separated by colon
to limit
download and upload rate separately. Note that
sockets have
receive buffers on them, this can lead to network
link load
higher than this rate limit just after transfer
beginning. You
can try to set net:socket-buffer to relatively small
value to
avoid this.
Yes because when you list a large directory, it is limited by this
parameter.
However, I have not found that a serious issue in normal operation, what
problem are you seeing?
Justin.
Justin,
Again thanks for your quick response.
You're right, I guess restricting the communications channel as well
isn't a big problem so long as the directories aren't very big; but the
most noticeable issue for me is that yesterday I was able to use the
net:limit-max value to restrict only the data transfer part of the lftp
session, yet today it doesn't seem to work - and like you said, it seems
necessary to use net:limit-total-rate to limit all communication instead
of just the data channel. It just seems weird, heh.
I just set limit-total-rate to 25600 and it is now restricting the
bandwidth usage (I assume all bandwidth) like we both would expect, so
I'm able to resume my files transfers, but yeah, it's just weird to work
one day and not the next.
Regards,
mog.
