On Mar 2, 7:50 pm, David <[EMAIL PROTECTED]> wrote: > On Feb 29, 3:00 pm, Amit Singh <[EMAIL PROTECTED]> wrote: > > > What's the practical difference to you between saying > > "daemon_timeout=<insanely high value>" versus something like > > "disable_daemon_timeout"? > > My file system is a network file system, which may suffer from long > lapses in network connectivity, and I'm nesting another file system on > top of it. This means my file system can't just fail and put up a > message, "Oops, try again", because its client won't be a human > operator. So this means I want it to never give up, similar to how > I've experienced NFS file systems during network failures.
daemon_timeout is a uint32. "insanely high value" could be UINT32_MAX seconds. That's something like 136 *years*. Unless you are expecting your "long lapse in network connectivity" to last longer than that, let me ask you again: what's the practical difference to you between saying "daemon_timeout=<insanely high value>" versus something like "disable_daemon_timeout"? Amit --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "macfuse-devel" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/macfuse-devel?hl=en -~----------~----~----~----~------~----~------~--~---
