[pacman-dev] Lock file location

Jason Chu jason at archlinux.org
Mon Jun 11 19:44:39 EDT 2007

On Mon, Jun 11, 2007 at 10:40:15AM -0400, Dan McGee wrote:
> Just thinking about this while changing some other stuff this morning
> (permissions checking by libalpm and pacman). Here is the current
> "default" situation:
> DB Path: /var/lib/pacman/<dbname>
> Lock file: /var/run/pacman.lck
> Remember that the lock file formerly resided in /tmp/, but that is not
> exactly a FHS-prescribed path. My proposal is this- when we create a
> lock file, it is for one purpose- to lock the database. Perhaps we
> should indicate this a bit better, and have one less path that needs
> to be manually configured, by simply making the lock file a part of
> the DB and generalizing the lock method to something that could
> eventually use any backend? In an extreme case, we could lock each
> individual DB seperately, but for now, a single lock file here:
> /var/lib/pacman/db.lck
> would seem to suffice. Is this acceptable to everyone? The benefit it
> gives us is if this location is writable, the DB is surely writable by
> the user running pacman, and we can remove the dependence on the
> pacman user being root. We will still need to do some permission
> checking on install/pre-install, but I'll think about that later. :)
> -Dan

Sounds fine to me, just as long as there's always an easy way to remove the
lock.  You know, when pacman crashes... ;)

If the lock were moved inside a sqlite db (or something) there'd have to be
a script to remove the lock.  Heck, we could generalize that too.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://archlinux.org/pipermail/pacman-dev/attachments/20070611/630fa58e/attachment.pgp>

More information about the pacman-dev mailing list