But remember the caveat: 'noappledouble' is a heavy hammer. It works by *unceremoniously* denying everything related to ._ files. New ones can't be created, existing ones can't be seen, and so on. It is possible for some applications (including the Finder) under some circumstances to throw a fit when they attempt to create a ._ file and fail--they could conclude that it must be because of insufficient permissions, which in turn could cause them to abort/unroll operations on other (non-._) files.
If you run into mysterious issues and have 'noappledouble' set, try removing it first. The nicer solution is for individual user-space file systems to support extended attributes. Some do, some don't. sshfs doesn't, or rather, can't, since there's no extended attribute support in the protocol version it uses. Amit On Apr 3, 2:37 am, Jej <[EMAIL PROTECTED]> wrote: > > The 'noreadahead' and 'nolocalcaches' options TURN OFF several types > > of caching at the kernel level. Regardless of what you might have > > experienced in your use case, you don't/can't make sshfs "faster" by > > using these options. You can make it slower though. > > ok, thanks for your technical explainations. You are true that the > cache/readahead are necessary. > > But noappledouble really improve the perf when using finder/ > fileselector to browse the mounts. Try the -o debug to see the > background activity without it... So maybe that depends of the user > needs, some can disable appledouble if they need finder and some would > leave it if console usage only. > > Jej --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
