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". > > http://en.wikipedia.org/wiki/File_locking#In_Unix-like_systems > http://kernel.org/doc/Documentation/filesystems/locks.txt > http://kernel.org/doc/Documentation/filesystems/mandatory-locking.txt > http://www.thegeekstuff.com/2012/04/linux-file-locking-types/ > http://www.hackinglinuxexposed.com/articles/20030623.html > > -- > Grant Edwards grant.b.edwards Yow! Your CHEEKS sit like > at twin NECTARINES above > gmail.com a MOUTH that knows no > BOUNDS -- > -- > http://mail.python.org/mailman/listinfo/python-list
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. Or maybe using sqlite would work even if writing from different processes? I would prefer to keep something human readable as INI-format though, rather then a sqlite file.. Thanks -- http://mail.python.org/mailman/listinfo/python-list
