Where not to store lock files

akostop at inaccessnetworks.com akostop at inaccessnetworks.com
Fri Jun 27 08:33:41 CEST 2008

AFAIK, and also according to FHS, all lock files should be stored in
/var/lock. And even though /var may be non-volatile (it usually is),
/var/lock is always mounted as tmpfs. In any case, I believe that
/usr/lib/opkg is NOT the right place to store a lock file.



> On Thursday 26 June 2008 14:22:22 you wrote:
>> This behaviour was mostly copied from dpkg, in that the lock file is
>> stored in the same place as the list files and other data. However, dpkg
>> stores the list data in /var, which we cannot always rely on to be
>> non-volatile. There is a configure option to specify a different
>> directory for the list cache, which should also change the lock
>> directory. Obviously volatility is not an issue for the lock file, so I
>> don't think there would be any issues with a patch to change it.
> IIRC /var is supposed to be non-volatile. In OE based distros this wasn't
> the
> case for a long time but it is now (mostly due marcel/hcid/bluetooth..).
> Ah
> the config option sounds great, I will give it a spin.
> sorry that my opkg mails always sound so grumpy...
> 	z.
> _______________________________________________
> opkg-devel mailing list
> opkg-devel at lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/opkg-devel

More information about the opkg-devel mailing list