Ok, thanks. I'll try to avoid it. Dan On Wed, Aug 27, 2008 at 11:44 AM, Amit Singh <[EMAIL PROTECTED]> wrote: > > Set it to 0 to disable it. The timeout mechanism is there for good > reason. Hopefully you won't release any software with the timeout > disabled by default--the user should have to opt in. > > Amit > > On Aug 27, 11:07 am, "Daniel Benamy" <[EMAIL PROTECTED]> wrote: >> That was it. Thanks. Amit- I read the FAQ but not the OPTIONS doc; >> I'll try to look around more before asking any more easy questions :-) >> >> Do you know if there is a way to disable it altogether instead of >> making it a big number? >> >> Dan >> >> On Tue, Aug 26, 2008 at 10:06 PM, ted bonkenburg <[EMAIL PROTECTED]> wrote: >> >> > See the "daemon_timeout" option: >> >> >http://code.google.com/p/macfuse/wiki/OPTIONS >> >> > I suspect this will explain what is going on. >> >> > ted >> >> > On Tue, Aug 26, 2008 at 9:50 PM, Daniel Benamy <[EMAIL PROTECTED]> wrote: >> >> >> I've got an odd problem. If I run my file system and use some >> >> operations including open and readlink, it's fine. If I use my read >> >> which is a special blocking call, it seems to works ok for maybe a >> >> minute and the suddenly the file system closes. gdb says it's exiting >> >> normally and I've run it with libgmalloc and it's not accessing >> >> invalid memory. If I do the read and then nothing else it'll close >> >> after a little while and if I do other things after the read (while >> >> it's still blocked) they work until it exits. Any ideas about what >> >> could cause this? >> >> Thanks a lot, >> >> Dan > > >
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "macfuse-devel" group. To post to this group, send email to macfuse-devel@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
