Hello stevieb,

I am not sure if you only want to use your module stevieb9/logging-simple or any logging module e.g. Log::Log4perl.

I put together a simple example using the default code from the documentation from Async::Event::Interval and your info that you want to log.

Sample of code bellow:

If this is not something that you are looking for, let me know if I understand not correctly and I will try to come up with something else.

Hope this helps, BR.

This is actually great! To be honest, I've never used Log::Log4perl before, so this got me to doing some testing and reading of the very informative docs. It does what is needed here so I do believe I am going to swap out for this logging distribution in this case. There's even config file directives to eliminate race-type conditions (ie. overlap).

That said, I'm still wondering if there's a real, feasible way to "share" a file handle across procs (forks, really). I don't believe there is, but I'm still open to hear input. Even at a C level, it doesn't appear very trivial to get things to run smoothly all of the time where eliminating overlap can be made consistent.

Update

"I put together a simple example using the default code from the documentation from Async::Event::Interval and your info that you want to log."

That's awesome that you actually tested out the SYNOPSIS of the distribution :)

I'm still wondering if there's a real, feasible way to "share" a file handle across procs (forks, really)

It depends on the system you are running on. Under Linux one can share file descriptor even between processes (forks). One can open file in append mode, use buffering based on EOL character and then the system will make sure that messages from different processes are written line-by-line. That will put lines from one process between lines from another process, but won't corrupt lines.

Of course file handle is not file descriptor, so passing of "file handles" around is a little bit more work, but still is quite possible.

With multi-threaded processes things are similar. Even though there are internal mutexes (though I'm not sure here about perl), still one has to make sure that buffering is line-oriented and file descriptor is in append mode.

Hello stevieb,

I am glad that it worked for you my proposed solution. To be honest when ever I need to do some logging I use this module. It is so powerful and flexible to do many many things.

Regarding: That said, I'm still wondering if there's a real, feasible way to "share" a file handle across procs (forks, really). I was reading yesterday the module AnyEvent that maybe can do what you are asking for. Unfortunately I did not spend time to experiment with it but maybe you can give it a try.

Never the less if you manage to resolve your problem update us also so we can have a reference for a possible similar case in future :)

BR / Thanos

Seeking for Perl wisdom...on the process of learning...not there...yet!

Here's a bit more of a simple example that uses a file handle directly, as opposed to having it hidden in the log object:

use warnings;
use strict;

use Async::Event::Interval;

open my $fh, '>', 'test.log' or die $!;

my $count = 1;

my $e = Async::Event::Interval->new(
    1,
    sub {
        print $fh "in event: $count\n";
        $count++;
    }
);

$e->start;

for (0..3){
    print $fh "write to file in main\n";
    sleep 1;
}

$e->stop;
[download]