I have this happen regularly -- one per hour? -- as well. I'm pretty sure I first saw this problem with BBEdit 9.3.0.
BBEdit 9.3.1 had a release note item saying, "Worked around bug in SMB client on Mac OS X 10.4.x which would randomly trigger a 'this file has been modified' warning when saving documents on SMB volumes." I was hopeful that this would solve the problem, but there was seemingly no change in the problem's occurrence on my setup. My files are stored on an NFS server. The server is running some flavour of Red Hat Linux with kernel 2.6.30. My Mac is running OS X 10.6.2. The Mac mounts the server using automountd, at a custom mount point (/opt/... rather than /Network/Servers/...). I've also changed the options for this mount point such that it is Finder-visible. The Mac and the server are on the same 100Mb/s LAN. Enabling or disabling the BBEdit preference to "Automatically refresh documents as they change on disk" has no effect. I'm certain nothing else is modifying the files: their timestamp isn't changing, and no-one but me has write access to them. The server and the Mac are time-synchronized to the same NTP server. I've noticed that this problem is correlated with a periodic large burst of activity between my Mac and the NFS server. At the same time, BBEdit becomes extremely sluggish, to the point of putting up the beach-ball for several seconds. I presume BBEdit is trying to refresh something from the server. At the times this occurs, I'll typically have 20-40 files open, as well as three or four BBEdit project views into the server's directories, each project showing several hundred to several thousand files. -- Ken. -- You received this message because you are subscribed to the "BBEdit Talk" discussion group on Google Groups. 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/bbedit?hl=en If you have a feature request or would like to report a problem, please email "[email protected]" rather than posting to the group.
