Gecko [ oric.aiou.edu.pk ]

Name	Size	Permission
AUTHORS	1.21 KB	-rw-r--r--
README.api	1.51 KB	-rw-r--r--
README.feature-removal-schedul...	2.19 KB	-rw-r--r--
THANKS.gz	3.25 KB	-rw-r--r--
changelog.Debian.gz	4.39 KB	-rw-r--r--
copyright	7.7 KB	-rw-r--r--
frontend.txt	1.07 KB	-rw-r--r--
rootless-builds.txt.gz	2.83 KB	-rw-r--r--
triggers.txt.gz	11.42 KB	-rw-r--r--
usertags.gz	1.8 KB	-rw-r--r--

Code Editor : frontend.txt

Frontend Interfaces
===================

This file will try to document some of the interfaces that dpkg makes
available to frontends or that expects them to use, which are currently
not covered by any other type of documentation.

Database Locking
----------------

Any frontend needing to make sure no write operation is currently happening,
and no other frontend is running should first acquire the frontend lock at
«<admindir>/lock-frontend», and then acquire the dpkg database lock at
«<admindir>/lock». When the frontend invokes dpkg, it should set the
environment variable DPKG_FRONTEND_LOCKED (to prevent dpkg from acquiring
the frontend lock), and then release the dpkg database lock, which will be
acquired by dpkg itself. This way no other frontend following this protocol
can race to perform operations while another one has one in progress.

These locks must be file record locks (i.e. fcntl(2) advisory locking), and
the whole file should be locked, as that's the most portable way to perform
this operation; this can be achieved by using start=0, len=0 and
whence=SEEK_SET.

${this.title}

Code Editor : frontend.txt