** Changed in: Debian
Status: Unknown => Fix Released
--
apache2.2-common: mod_cgid fills error.log with [error] lines
https://bugs.launchpad.net/bugs/131632
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs ma
This was fixed in debian, and should be in gutsy already.
** Changed in: apache2 (Ubuntu)
Status: Invalid => Fix Released
--
apache2.2-common: mod_cgid fills error.log with [error] lines
https://bugs.launchpad.net/bugs/131632
You received this bug notification because you are a member of
** Bug watch added: Debian Bug tracker #418499
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=418499
** Also affects: Debian via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=418499
Importance: Unknown
Status: Unknown
--
apache2.2-common: mod_cgid fills error.log with [error
The standard way to control the apache2 daemon is to use the init
script.
** Changed in: apache2 (Ubuntu)
Status: Incomplete => Invalid
--
apache2.2-common: mod_cgid fills error.log with [error] lines
https://bugs.launchpad.net/bugs/131632
You received this bug notification because you ar
Hello Mathias, thanks for your reply.
I have some further detail to add. Yes, it started to happen after an
upgrade, but I don't think this could be the cause of this behaviour (if
however you need more info about this I can provide them).
Rather, I discovered that the way I started Apache (using
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I cannot reproduce your issue. The directory /var/run/apache2 should be
created whenever apache2 is started with its init script.
Did this start to happen after an upgrade from apache2 ?
** Changed in: apache2 (U
