I'm just not entirely clear from the man page.. does the timeout start
counting from the last communication, or does it start counting from the
beginning of the transmission?
also, if the server is set to timeout at, say, 300s, and it's busy
moving stuff around but not talking to the client,
On 7/9/06, Eric Horne [EMAIL PROTECTED] wrote:
I'm just not entirely clear from the man page.. does the timeout start
counting from the last communication, or does it start counting from the
beginning of the transmission?
I believe it counts from the last communication.
also, if the server
https://bugzilla.samba.org/show_bug.cgi?id=3768
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=3809
[EMAIL PROTECTED] changed:
What|Removed |Added
Severity|normal |enhancement
https://bugzilla.samba.org/show_bug.cgi?id=3806
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
Date: Mon Jul 10 04:24:07 2006
Author: wayned
Update of /data/cvs/rsync
In directory dp.samba.org:/tmp/cvs-serv17363
Modified Files:
configure.in configure config.h.in
Log Message:
If makedev() takes 3 args, define MAKEDEV_TAKES_3_ARGS.
Revisions:
configure.in1.250 =
Date: Mon Jul 10 04:25:10 2006
Author: wayned
Update of /data/cvs/rsync
In directory dp.samba.org:/tmp/cvs-serv17591
Modified Files:
rsync.h
Log Message:
Define MAKEDEV() based on the MAKEDEV_TAKES_3_ARGS define.
Revisions:
rsync.h 1.294 = 1.295
Date: Mon Jul 10 04:25:53 2006
Author: wayned
Update of /data/cvs/rsync
In directory dp.samba.org:/tmp/cvs-serv18156
Modified Files:
flist.c
Log Message:
Use new MAKEDEV() macro instead of makedev() directly.
Revisions:
flist.c 1.350 = 1.351
