Hello Heiko, this seems absolutely right after reading a bit about it. Since I've never used Unix sockets nor Mojo::IOLoop, I'd like to double check my comprehension with you :)
So rsyslogd sends output to a Unix Socket (in occurence, a file ?) and Mojo::IOLoop::Client reads its content in real time ? Or is this some sort of queue ? IOLoop::Client would be used as an extension to feed some core function in IOLoop ? If you could explain the interactions that would be give me an edge ... and help kickstart my lab :) In the meanwhile I'll keep reading. Cheers, Luc On Friday, 26 April 2019 09:09:13 UTC-4, Heiko Jansen wrote: > > Bit late to the party, but anyhow.... > If you tell rsyslogd to send output to a socket (using omuxsock), you can > then use Mojo::IOLoop::Client to connect() to a socket via the "path" > argument. > Afterwards you can make use of the IOLoop to process events for reading > from the socket. > That's what you want? > -- You received this message because you are subscribed to the Google Groups "Mojolicious" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/mojolicious. For more options, visit https://groups.google.com/d/optout.
