"File modified on disk" warnings - seemingly random

[bunner bob]

Lately I seem to get a couple of different messages about files that
are open being modified on disk. Often it's right when I open the
file, or I open it and make a few changes, then "boop" - "This file
appears to have been modified" - saving may cause data loss, save
anyway, etc. And I wasn't even trying to save. Just opening.

We're using another mac as a file server - running OS X Tiger (not
Server version).

Never used to see these. Must have happened since some BBEdit upgrade.
That or an OS upgrade. BBEdit 9.3.1, OS X 10.5.8.

Any idea?

[G. T. Stresen-Reuter]

On Jan 25, 2010, at 11:10 PM, bunner bob wrote:

> Lately I seem to get a couple of different messages about files that
> are open being modified on disk.

On a related note, I'm always confused by the copy and buttons in this
dialog. I never know if I should discard or not (am I discarding the
changes on disk or those in my window?).

Can anyone think of a moniker that would help me remember which is
which? I recently lost some important data due to just this confusion.

Thanks in advance.

Ted Stresen-Reuter

[Doug McNutt]

The "modified" dialog comes up when something has changed the file on disk so that it doesn't reliably represent what BBEdit read when it opened the file.

I make use of that a lot because I am often using BBEdit to display something that is being written by other software. BBEdit complains if I accidentally try to modify the file but it is quite happy to reload a revised version automatically if I haven't made changes.

Is anyone else making changes on the server? I would imagine that BBEdit uses time-last-modified tests to detect changes. Are the clocks on server and client synchronized?

And the feature has been around for a long time. I'm stuck on OS 10.3.9 and a much earlier version than 9 of BBEdit.
--
-> The US of A is getting pelloreid <-

[Robert A. Rosenberg]

At 17:42 -0700 on 01/25/2010, Doug McNutt wrote about Re: "File
modified on disk" warnings - seemingly random:

>I would imagine that BBEdit uses time-last-modified tests to detect
>changes. Are the clocks on server and client synchronized?

They do not need to be since if the timestamp that existed when you
originally read the file from the server is no longer the timestamp
on the server's copy, then it must have been updated.

[bunner bob]

On Jan 25, 4:42 pm, Doug McNutt <dougl...@macnauchtan.com> wrote:
> The "modified" dialog comes up when something has changed the file on disk so that it doesn't reliably represent what BBEdit read when it opened the file.
>
> I make use of that a lot because I am often using BBEdit to display something that is being written by other software. BBEdit complains if I accidentally try to modify the file but it is quite happy to reload a revised version automatically if I haven't made changes.
>
> Is anyone else making changes on the server? I would imagine that BBEdit uses time-last-modified tests to detect changes. Are the clocks on server and client synchronized?

Definitely nobody else making changes. This is a micro network of just
two of us plus the server.

Just happened again. I opened an older BBEdit project and BBE updated
it to a ".bbprojectd" file. Then about 5 seconds later, up pops this
warning that the file may have been changed on disk by another
application. My options are "Cancel" and "Save Anyway". I'm not
actually "saving" anything - the project is updated, no files are
open. Clicking Cancel just makes the dialog pop up again.

I hit Cancel then closed it before the dialog had a chance to
reappear. Then reopened. Seems ok for the moment.

But this frequently happens after doing a "save as" with a new name.
Could something in the OS be modifying the files after I save them?

[Gerry Panganiban]

I can confirm that this happens to me quite often as well. My files are mounted via SMB (samba) from a linux server. More often than not, the 'modified' dialog comes up right after I choose "File->Save" or cmd-S a file that I've modified. If I choose 'reload from disk' then my changes are lost. If I choose the other option, my file is intact but not saved. Saving the file a second time usually works.

--Gerry

> --
> 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 bbe...@googlegroups.com
> To unsubscribe from this group, send email to
> bbedit+un...@googlegroups.com
> 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 "sup...@barebones.com" rather than posting to the group.

[Gerry Panganiban]

Hi all,

I'm able to workaround the problem by turning off "Automatically refresh documents as they change on disk" in Preferences->Application.

--Gerry

[Grant Barrett]

I have the same problem:

--The files are on my local drive, not on a remote server. There isn't
even a server connected.

--Nobody else is accessing the files and I only have them open in one
program.

--"Automatically refresh documents as they change on disk" is not
selected.

--It sometimes happens to files I've just opened and have made no
changes to.

Grant Barrett
grantb...@gmail.com

Bio: http://www.google.com/profiles/grantbarrett

[Jim Chaffin]

Had this happen just yesterday with a totally local file. I assumed it was because of these messages! LOL! 8-) Don'cha love those intermittent bugs?! 8-|

On Jan 29, 2010, at 3:02 PM, Grant Barrett wrote:

I have the same problem:

Jim Chaffin

xairbu...@mac.com

----------

A good pun is it's own reword.

[Doug McNutt]

Is it possible that some content-indexing package is hitting the files in background? Or perhaps some disk optimizing cron job?

--

--> A fair tax is one that you pay but I don't <--

[Ken Dubuc]

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.

[Rich Siegel]

On 2/2/10 at 10:54 AM, kennet...@gmail.com (Ken Dubuc) wrote:

>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.

This seems like an excellent reason (and opportunity :-)) to
contact Tech Support. Please supply a screen shot of the alert
that you get, and a brief explanation of why you think it's
incorrect - for example, a screen shot of a Finder Get Info
window showing the file's modification date before you open it,
and another one showing the file's modification date when you
get the warning.

Thanks,

R.
--
Rich Siegel Bare Bones Software, Inc.
<sie...@barebones.com> <http://www.barebones.com/>

Someday I'll look back on all this and laugh... until they
sedate me.