Pacman

Historical bug tracker for the Pacman package manager.

The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues

This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
Tasklist

FS#26718 - pacman: unhandled SIGQUIT

Attached to Project: Pacman
Opened by Léo LETARO (firekraag) - Wednesday, 02 November 2011, 08:23 GMT
Last edited by Dan McGee (toofishes) - Tuesday, 22 November 2011, 03:38 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Unlike SIGINT, SIGQUIT seems to be unhandled: pacman exits without deleting its lock file.
It should at least delete /var/lib/pacman/db.lck.
(Exiting cleanly would be preferred compared to just ignoring the signal as this is done with SIGINT)

Additional info:
* package version: 3.5.4-4
* execution output: http://pastebin.com/iAHavnJq

Steps to reproduce:
run pacman and interrupt it, using the key combo C-\ or with: kill -s `kill -l QUIT` PACMAN_PID
This task depends upon

Closed by  Dan McGee (toofishes)
Tuesday, 22 November 2011, 03:38 GMT
Reason for closing:  Won't implement
Additional comments about closing:  QUIT is different than INT, on purpose for escalating levels of severity. Simply remove the file yourself.
Comment by Alessandro Delgado (adelgado) - Friday, 04 November 2011, 15:19 GMT
Should it really remove its lock file? What if the abrupt killings renders something inconsistent? Isn't this by default?

Loading...