Mailing List Archive

STDERR/Debug/Log File
Couldn't find a clear answer via google, so am choosing to pick your brains on this....

How does one get error information, for debugging, going into a text file instead of to the terminal window?

The context is a Catalyst App started via a Plackup command.
Do I add something to that command line command (does 2> work with plackup?),
or do I add something to the script in my Catalyst app?

Either way, I'd like STDERR to go to a specified text file, instead of to the terminal window.

It sounds stupidly simple, only a few google searches later, the answer is still surprisingly unclear, =S.

Grateful for any help.

If there's more than one way to do it, any advice on best practice also appreciated.

Yours,
Andrew.
Re: STDERR/Debug/Log File [ In reply to ]
Hello,

we are using Log4perl to log in different logfiles (paniclog (ERROR &
PANIC) + app.log (DEBUG & INFO & WARN & ERROR & PANIC)). Also we override
die() & warn() to write into logfiles before write to STDERR.

It is possible to use a special app-debug.log only for DEBUG-level messages.

Mit freundlichen Grüßen
Felix Ostmann

_________________________________________________

QE GmbH & Co. KG
Martinistraße 3
49080 Osnabrück
Deutschland

Tel.: +49 (0) 541 / 40666 11
Fax: +49 (0) 541 / 40666 22
Email: info@qe.de
Web: www.qe.de

Unsere Geschäftszeiten:
Montag bis Freitag von 8 bis 16 Uhr

Firmensitz: Osnabrück
AG Osnabrück - HRA 200252
Steuer-Nr.: 66/204/54104
Ust-IdNr.: DE814737310

Komplementärin:
QE24 GmbH
AG Osnabrück - HRB 200359
Geschäftsführer: Ansas Meyer
_________________________________________________


Die in dieser Email enthaltenen Informationen sind vertraulich
zu behandeln und ausschließlich für den Adressaten bestimmt.
Jegliche Veröffentlichung, Verteilung oder sonstige in diesem
Zusammenhang stehende Handlung wird ausdrücklich untersagt.

2015-12-15 8:39 GMT+01:00 Andrew <catalystgroup@unitedgames.co.uk>:

> Couldn't find a clear answer via google, so am choosing to pick your
> brains on this....
>
> How does one get error information, for debugging, going into a text file
> instead of to the terminal window?
>
> The context is a Catalyst App started via a Plackup command.
> Do I add something to that command line command (does 2> work with
> plackup?),
> or do I add something to the script in my Catalyst app?
>
> Either way, I'd like STDERR to go to a specified text file, instead of to
> the terminal window.
>
> It sounds stupidly simple, only a few google searches later, the answer is
> still surprisingly unclear, =S.
>
> Grateful for any help.
>
> If there's more than one way to do it, any advice on best practice also
> appreciated.
>
> Yours,
> Andrew.
>
>
> _______________________________________________
> List: Catalyst@lists.scsys.co.uk
> Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
> Searchable archive:
> http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
> Dev site: http://dev.catalyst.perl.org/
>
>
Re: STDERR/Debug/Log File [ In reply to ]
Hi,

did you tried "&> /tmp/logfile"? I tried it with my App and it redirected
all the output in the given Textfile.

Best Regards,

Patrick

Andrew <catalystgroup@unitedgames.co.uk> schrieb am Di., 15. Dez. 2015 um
08:41 Uhr:

> Couldn't find a clear answer via google, so am choosing to pick your
> brains on this....
>
> How does one get error information, for debugging, going into a text file
> instead of to the terminal window?
>
> The context is a Catalyst App started via a Plackup command.
> Do I add something to that command line command (does 2> work with
> plackup?),
> or do I add something to the script in my Catalyst app?
>
> Either way, I'd like STDERR to go to a specified text file, instead of to
> the terminal window.
>
> It sounds stupidly simple, only a few google searches later, the answer is
> still surprisingly unclear, =S.
>
> Grateful for any help.
>
> If there's more than one way to do it, any advice on best practice also
> appreciated.
>
> Yours,
> Andrew.
>
> _______________________________________________
> List: Catalyst@lists.scsys.co.uk
> Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
> Searchable archive:
> http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
> Dev site: http://dev.catalyst.perl.org/
>
Re: STDERR/Debug/Log File [ In reply to ]
Worked a treat! Many thanks! =).

Yours,
Andrew.
----- Original Message -----
From: Patrick Kilter
To: The elegant MVC web framework
Sent: Tuesday, December 15, 2015 8:35 AM
Subject: Re: [Catalyst] STDERR/Debug/Log File


Hi,


did you tried "&> /tmp/logfile"? I tried it with my App and it redirected all the output in the given Textfile.


Best Regards,


Patrick


Andrew <catalystgroup@unitedgames.co.uk> schrieb am Di., 15. Dez. 2015 um 08:41 Uhr:

Couldn't find a clear answer via google, so am choosing to pick your brains on this....

How does one get error information, for debugging, going into a text file instead of to the terminal window?

The context is a Catalyst App started via a Plackup command.
Do I add something to that command line command (does 2> work with plackup?),
or do I add something to the script in my Catalyst app?

Either way, I'd like STDERR to go to a specified text file, instead of to the terminal window.

It sounds stupidly simple, only a few google searches later, the answer is still surprisingly unclear, =S.

Grateful for any help.

If there's more than one way to do it, any advice on best practice also appreciated.

Yours,
Andrew.

_______________________________________________
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/



------------------------------------------------------------------------------


_______________________________________________
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/