Package: squirrelmail Version: 1.4.9a-1 Severity: normal Hi,
When /etc/squirrelmail/conf.pl is disconnected abruptly, it does not die but spawns infinitely calls to "clear" via clear_screen(). I got 600 forks/s and 100% CPU for hours because the admin of one of my vservers closed his ssh session abruptly :-( My guess is that in the loop of the script to display the menu, it clears the screen (so the fork to call "clear") and waits for input but with disconnected IO, there is no wait on input and the process loops as crazy. To reproduce the bug: Simply connect remotely to a server, launch /etc/squirrelmail/conf.pl and close the xterm running the ssh session. This leaves the perl script running alone as explained. Reconnect and watch your cpu ;-) To fix the bug: Either trap the IO disconnection event to quit nicely or at least test for it in the loop but find a way to avoid looping without pause. Phil -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-1-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
