maxRetryPause doesn't have desired effect on Leopard (Mac OS X 10.5) about s3backer HOT 10 CLOSED

Should be fixed in r88. If you get a chance please apply that patch and retest. 
Thanks!

I believe code in r88:

snprintf(buf, sizeof(buf), "-odaemon_timeout=%u", config.connect_timeout
 + config.io_timeout + config.max_retry_pause / 1000 + 10);

should read:

snprintf(buf, sizeof(buf), "-odaemon_timeout=%u", ( config.connect_timeout
 + config.io_timeout + config.max_retry_pause ) / 1000 + 10);

Because all these parameters are in milliseconds.

And daemon_timeout has a maximum value of 600 seconds.
Look here:

http://www.google.com/codesearch?hl=en&lr=&q=FUSE_MAX_DAEMON_TIMEOUT+package%3Ah
ttp%3A%2F%2Fmacfuse\.googlecode\.com&sbtn=Search

and here:

http://www.google.com/codesearch?q=daemon_timeout+package%3Ahttp%3A%2F%2Fmacfuse
\.googlecode\.com&origq=daemon_timeout&btnG=Search+Trunk

Oops! I was wrong! Sorry!

Code is fine.

Strange thing, when I give different parameters to maxRetryPause s3backer always
starts with daemon_timeout = 100:

s3backer --prefix=macos --size=75M --filename=s3-backup3-remote.dmg
--maxRetryPause=500000 -d -f du-backup3 /Users/demon/mounts/mnt-du-backup3

2008-07-11 13:13:46 DEBUG:  connect_timeout: 30s
2008-07-11 13:13:46 DEBUG:       io_timeout: 30s
2008-07-11 13:13:46 DEBUG: initial_retry_pause: 200ms
2008-07-11 13:13:46 DEBUG:  max_retry_pause: 500000ms
2008-07-11 13:13:46 DEBUG: fuse_main arguments:

2008-07-11 13:13:46 DEBUG:   [0] = "s3backer"
2008-07-11 13:13:46 DEBUG:   [1] = "-o"
2008-07-11 13:13:46 DEBUG:   [2] =
"kernel_cache,fsname=s3backer,use_ino,entry_timeout=31536000,negative_timeout=31
536000,attr_timeout=31536000,default_permissions,nodev,nosuid,daemon_timeout=100
"

On a Leopard "daemon_timeout" has a fixed maximum of 600 seconds.
Everything higher is simply ignored.

May be it is better just to set it to a maximum?


Cause when I am using different values of timeout/retry_pause, s3backer always 
sets
daemon_timeout to 850 seconds which is higher than a maximum and it defaults to 
60
seconds which sometimes is not enough.

See changes in r104. We now limit the daemon_timeout setting to
FUSE_MAX_DAEMON_TIMEOUT on MacOS and emit a warning if we would have tried to 
set a
higher value.

Correction: use r110 instead of r104.

Thank you! r110 makes sense and works perfect.