| Server IP : 79.136.114.73 / Your IP : 3.142.134.67 Web Server : Apache/2.4.7 (Ubuntu) PHP/5.5.9-1ubuntu4.29 OpenSSL/1.0.1f System : Linux b8009 3.13.0-170-generic #220-Ubuntu SMP Thu May 9 12:40:49 UTC 2019 x86_64 User : www-data ( 33) PHP Version : 5.5.9-1ubuntu4.29 Disable Function : pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority, MySQL : ON | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : ON Directory : /usr/share/doc/dpkg-dev/ |
Upload File : |
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, should lock the dpkg database by locking the file «<admindir>/lock» using file record locks (i.e. fcntl(2) advisory locking). 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. Take into account there will be a race condition between the frontend unlocking the database and the invoked dpkg locking it again, in which another process could lock it. In the future this functionality will be available through a shared libdpkg library, and all frontends will be expected to switch to that instead, because this will fix the aforementioned race condition.