[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#215741: A meaningful log message when a CGI script is killed due to RLimit* settings



Package: apache
Version: 1.3.27.0-2
Severity: wishlist

A more meaningfull message in the log file or something else than the usual HTTP 500
error page would be nice when a CGI script gets killed because it's over the limits
set by RLimitCPU or RLimitMem.

With the current way logging works I only get premature end of script headers in the 
error log file. That makes it extremely hard to find out why the script is not working.


-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux mtx 2.4.22-1-686 #1 Fri Sep 5 23:04:29 EST 2003 i686
Locale: LANG=C, LC_CTYPE=C (ignored: LC_ALL set to POSIX)

Versions of packages apache depends on:
ii  apache-common                 1.3.27.0-2 Support files for all Apache webse
ii  debconf                       1.3.8      Debian configuration management sy
ii  dpkg                          1.10.10    Package maintenance system for Deb
ii  libc6                         2.3.2-6    GNU C Library: Shared libraries an
ii  libdb4.1                      4.1.25-6   Berkeley v4.1 Database Libraries [
ii  libexpat1                     1.95.6-4   XML parsing C library - runtime li
ii  libmagic1                     4.02-4     File type determination library us
ii  logrotate                     3.6.5-2    Log rotation utility
ii  mime-support                  3.23-1     MIME files 'mime.types' & 'mailcap
ii  perl [perl5]                  5.8.0-18   Larry Wall's Practical Extraction 

-- debconf information:
* apache/enable-suexec: false




Reply to: