I use log4perl in my code for exactly this reason.
On Wed, Nov 26, 2014 at 11:55 AM, Vincent Veyron <
vincent.vey...@libremen.org> wrote:
> On Tue, 25 Nov 2014 11:11:13 +1300
> Worik Stanton wrote:
>
>
> > I get "die" erors in one log file (the one specified for my virtual
> > host) and warn err
On Tue, 25 Nov 2014 11:11:13 +1300
Worik Stanton wrote:
> I get "die" erors in one log file (the one specified for my virtual
> host) and warn errors in /var/log/apache2/error.log
>
> What on Earth could be the reason for that?
I can't tell you the reason, but there is a workaround if that bot
On 21/11/14 04:19, Perrin Harkins wrote:
> I think that only redirects errors logged with Apche2::Log, not all of
> STDERR. There might be a workaround for capturing STDERR. I'd try searching
> the mailing list archives.
>
> - Perrin
I get "die" erors in one log file (the one specified for my vir
I think that only redirects errors logged with Apche2::Log, not all of
STDERR. There might be a workaround for capturing STDERR. I'd try searching
the mailing list archives.
- Perrin
On Mon, Nov 17, 2014 at 6:28 PM, worik wrote:
> My virtual host has errors redirected to:
>
> Worik.errors.log
>
My virtual host has errors redirected to:
Worik.errors.log
(ErrorLog ${APACHE_LOG_DIR}/Worik.error.log)
It is in this virtueal host that I have set-up mod-perl. Why then are
errors sent to error.log?
And why do errors emanating from mod_perl not have time stamps?
--
Why is the legal status
