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.
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.
FS#33654 - Increasing nofile limit leads to delay in signature verification
Attached to Project:
Pacman
Opened by Georgi Yonchev (gy) - Thursday, 31 January 2013, 15:00 GMT
Last edited by Allan McRae (Allan) - Saturday, 09 February 2013, 03:48 GMT
Opened by Georgi Yonchev (gy) - Thursday, 31 January 2013, 15:00 GMT
Last edited by Allan McRae (Allan) - Saturday, 09 February 2013, 03:48 GMT
|
DetailsSummary and Info:
Strange delay appears when pacman is doing package signature verification, when the number of opened files is set to 999999. Using strace I've saw that there are close() calls as many as the limit is. So, when using default limits (1024 or 4096) this delay can't be noticed. Steps to Reproduce: ulimit -n 999999 pacman -S ... this way integrity check will delay a bit, running strace -f pacman -S ... will show you the close() syscalls. Using 9999999 as limit, increases the syscalls and so the delay. |
This task depends upon
Closed by Allan McRae (Allan)
Saturday, 09 February 2013, 03:48 GMT
Reason for closing: Upstream
Additional comments about closing: gpgme issue
Saturday, 09 February 2013, 03:48 GMT
Reason for closing: Upstream
Additional comments about closing: gpgme issue
Comment by Dan McGee (toofishes) -
Thursday, 31 January 2013, 15:23 GMT
This is gpgme stupidity. We can't do much here, I've noticed this before as well.