On 2012-10-18, andrea crotti <andrea.crott...@gmail.com> wrote:
> 2012/10/18 Grant Edwards <invalid@invalid.invalid>:
>> On 2012-10-18, andrea crotti <andrea.crott...@gmail.com> wrote:
>>
>> File locks under Unix have historically been "advisory". That means
>> that programs have to _choose_ to pay attention to them. Most
>> programs do not.
>>
>> Linux does support mandatory locking, but it's rarely used and must be
>> manually enabled at the filesystem level. It's probably worth noting
>> that in the Linux kernel docs, the document on mandatory file locking
>> begins with a section titled "Why you should avoid mandatory locking".
>
> Uhh I see thanks, I guess I'll use the good-old .lock file (even if
> it might have some problems too).
>
> Anyway I'm only afraid that my same application could modify the
> files, so maybe I can instruct it to check if the file is locked.
If what you're guarding against is multiple instances of your
application modifying the file, then either of the advisory file
locking schemes or the separate lock file should work fine.
--
Grant Edwards grant.b.edwards Yow! All this time I've
at been VIEWING a RUSSIAN
gmail.com MIDGET SODOMIZE a HOUSECAT!
--
http://mail.python.org/mailman/listinfo/python-list
