David,
On Mon, November 18, 2019 10:27 am, David Carlson wrote:
> I like Derek 's suggestion but I would see that and call with this
> suggestion:
>
> There is a lock on the selected data file. Most likely this means that
> the data file was not cleanly closed (due to a crash) after it was last
> opened.
> If you are sure that it is not currently in use by you or another user,
> click
> "Open Anyway". Otherwise, click "Open Read-Only" or one of the other
> options.
I was trying to avoid the word "lock".
> And my note to dev's would include the caveat that PID is useless when
> remote users have access.
I don't understand why you say this. Perhaps I should have been more
explicit about what data to put in, which can include e.g. machine name,
to differentiate if you have a data file on an NFS/CIFS/etc shared
storage. The point being that in the case where it is a crash/shutdown
event, the local PID will have changed and we can have a high probability
of detecting that condition.
> David Carlson
-derek
> On Mon, Nov 18, 2019, 8:30 AM Derek Atkins <de...@ihtfp.com> wrote:
>
>> Hi,
>>
>> I think I have a suggestion for some better wording. See below.
>>
>> David Carlson <david.carlson....@gmail.com> writes:
>>
>> > I think a better and more accurate wording would be "The data file has
>> not
>> > been cleanly closed since it was last opened. If you are sure that it
>> was
>> > not opened by another user, click 'Open Anyway'. Otherwise click one
>> of
>> > the other options."
>>
>> How about:
>>
>> The data file is currently in use. Most likely this means that the data
>> file was not cleanly closed (due to a crash) after it was last opened.
>> If you are sure that it is not currently in use by you or another user,
>> click "Open Anyway". Otherwise, click one of the other options.
>>
>> Note to devs: does it make sense to put the gnucash PID into the lock
>> file and then check to see if that PID is currently running? That could
>> help detect whether there is a current process or a crash/unclean
>> shutdown?
>>
>> > To me the important part is that the data file has not been cleanly
>> closed,
>> > which is the real reason that the lock file exists. There may be
>> better
>> > words to use as long as this idea is incorporated.
>>
>> I suppose that is one way to interpret it, as "currently in use".
>>
>> > David Carlson
>>
>> > Please remember to CC this list on all your replies.
>> > You can do this by using Reply-To-List or Reply-All.
>>
>> -derek
>>
>> --
>> Derek Atkins 617-623-3745
>> de...@ihtfp.com www.ihtfp.com
>> Computer and Internet Security Consultant
>>
>
--
Derek Atkins 617-623-3745
de...@ihtfp.com www.ihtfp.com
Computer and Internet Security Consultant
_______________________________________________
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
