Re: stdout from POE::Component::Server::TCP as daemon

Stefan.

This sounds like a reasonable implementation scheme for a POE based
daemon.  I did something like this several years ago with roughly the
same components.

chris

On Sun, Jun 24, 2012 at 2:16 AM, Stefan Parvu
<[email protected]> wrote:
> Hi folks,
>
> Im experimenting with POE, POE::Component::Server::TCP to implement
> a simple daemon (Proc::Daemon) which listens to requests to update
> one or many RRD databasefiles. So this daemon will use:
>
> =A0Proc::Daemon
> =A0POE::Component::Server::TCP
> =A0RRDs
>
> I am playing around: http://www.systemdatarecorder.org/poe1
> my application starts fine but I expect to see all STDOUT,
> STDERR under the dameon's log. I should read more, I know.
>
> If I defined in my Proc::Daemon::Init the STDOUT and STDERR
> like below:
> eval { Proc::Daemon::Init( { child_STDOUT =3D> "$slog",
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 child_STDERR =3D>=
 "$slog" } ); };
>
>
> wouldnt this be ok for my POE::Component::Server::TCP ?
>
> Thanks,
> Stefan