Subject | Re: [firebird-support] Re: DB modified date is over a month old, but Forced Writes are ON?? |
---|---|
Author | mark@lawinegevaar.nl |
Post date | 2011-06-09T15:16:37Z |
On Thu, 09 Jun 2011 15:00:37 -0000, "Raymond" <rschappe@...> wrote:
This might account for the differences.
As far as I am aware, Windows will only update the date modified if a
process releases its exclusive or shared lock on a file. As this doesn't
happen regularly under SuperServer and does happen on Classic, I suspect
that might account for the difference in behavior (so based on that
suspicion I predict you are using SuperServer, and Andre is using Classic).
Mark
>> FWIW, my Windows does.when
>> Just checked FB-Databases on 2003Server. Stamp updates frequently.
>>
>> best regards,
>> André
>
>
> Andre, Thanks for the feedback.
>
> That is odd as I am also running 2003 Server.
>
> What is __more odd__ is that I ran
>
> gfix -sh -tr 60 dbname
> gfix -sh -force 60 dbname
>
> and the date/time modified Still did not change!!!
>
> I ran my backup and did a successful restore and copied the backup to
> another server as well... so I was feeling pretty safe now...
>
> I finally had to stop the Firebird service (I do not run FBGuard) and
> I did that, the Last Modified date/time stamp _finally_ was updated!!!on
>
> Things seemed to work a bit more "normal" when we were running Firebird
> Ubuntu!<grin>Could it be you are using SuperServer on Windows, and Classic on Ubuntu?
This might account for the differences.
As far as I am aware, Windows will only update the date modified if a
process releases its exclusive or shared lock on a file. As this doesn't
happen regularly under SuperServer and does happen on Classic, I suspect
that might account for the difference in behavior (so based on that
suspicion I predict you are using SuperServer, and Andre is using Classic).
Mark