Re: How to prevent Gnumeric from overwriting the same file by different gnumeric instances

Morten Welinder <[email protected]>
Newsgroups gmane.comp.gnome.apps.gnumeric
Message-ID <CANv4PN=DqpY2gz+UsqYY0tcKovGe+bwwScVS+PkR1aROheQKkA@mail.gmail.com>
The next version of Gnumeric will verify that the time stamp has the expected
value before overwriting.

Morten


On Sat, Mar 24, 2018 at 7:09 PM, Yury Dubinsky <[email protected]> wrote:
> I believe  timestamp checking must be anyway. Just lock files cannot
> be a very reliable solution. A lock file could be deleted. I am not
> talking about more exotic hard links when lock files will be saved in
> different directories.
>
>
>> ---------------------------------------------------
>> On Thu, 22 Mar 2018 20:28:29 -0400, Morten Welinder <[email protected]>
>> wrote :
>>>  [...]
>>>
>>> Yes.
>>>
>>> And now a reasonable follow-up question would be what that reason was,
>>> but I don't
>>> remember the details.  It was discussed in mail or on IRC.
>>>
>>> However, a quick look says that it can't work right under NFS -- and
>>> networked
>>> file systems are the primary reason why one would want locking.
>>> Specifically,
>>> O_EXCL isn't going to be necessarily exclusive.
>>>
>>> M.
>>> _______________________________________________
>>> gnumeric-list mailing list
>>> [email protected]
>>> https://mail.gnome.org/mailman/listinfo/gnumeric-list
>> _______________________________________________
>> gnumeric-list mailing list
>> [email protected]
>> https://mail.gnome.org/mailman/listinfo/gnumeric-list
>>
> _______________________________________________
> gnumeric-list mailing list
> [email protected]
> https://mail.gnome.org/mailman/listinfo/gnumeric-list
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.