Req #35894 [Com]: php-imap doesn't trap USR2 when mailbox is locked

From: Date: Thu, 02 Feb 2023 04:49:00 +0000
Subject: Req #35894 [Com]: php-imap doesn't trap USR2 when mailbox is locked
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-243613@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=35894&edit=1 ID: 35894 Comment by: testing at example dot com Reported by: jik at kamens dot brookline dot ma dot us Summary: php-imap doesn't trap USR2 when mailbox is locked Status: Analyzed Type: Feature/Change Request Package: IMAP related Operating System: Linux PHP Version: 5.1.2 Block user comment: N Private report: N New Comment: 1 Previous Comments: ------------------------------------------------------------------------ [2022-08-18 22:26:17] sample at email dot tst 1 ------------------------------------------------------------------------ [2022-08-18 22:26:16] sample at email dot tst 1 ------------------------------------------------------------------------ [2022-08-18 22:26:11] sample at email dot tst 1 ------------------------------------------------------------------------ [2010-01-10 22:36:08] rasmus@php.net The problem with PHP setting a handler for SIGUSR2 is that when we are running as a SAPI module inside some other process like Apache or anything using LinuxThreads, grabbing SIGUSR2 may cause problems. Newer Linux kernels provide reserved internals signals for LinuxThreads to use, and Apache should only be using SIGUSR1, but how confident are you that PHP grabbing this signal isn't going to break it in some environments? It may fix the problem in yours, but if it breaks it in many others that is something we need to deal with. ------------------------------------------------------------------------ [2010-01-10 21:45:30] tdfischer at fedoraproject dot org This bug is still around and can wreak havok for a drupal site that lets users submit content via machine-local mail. Could someone *please* commit it already? ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=35894 -- Edit this bug report at https://bugs.php.net/bug.php?id=35894&edit=1

« previous php.bugs (#243613) next »