On 12/04/2015 12:57 AM, Jan Klemkow wrote:
I wrote ucspi-tee[1] to do this job for me. But I think there is a
similar tool of djb's tool chain, that does it, too.
Okay yes I can compile and run your program ucspi-tee. But how exactly
do I use it? This is how I (successfully) use sj now:
On Fri, Dec 04, 2015 at 11:21:17AM -0500, Greg Reagle wrote:
> On 12/04/2015 12:57 AM, Jan Klemkow wrote:
> >I wrote ucspi-tee[1] to do this job for me. But I think there is a
> >similar tool of djb's tool chain, that does it, too.
>
> Okay yes I can compile and run your program ucspi-tee. But
On Tue, Dec 01, 2015 at 11:35:46AM -0500, Greg Reagle wrote:
> On 12/01/2015 10:55 AM, Greg Reagle wrote:
> >I don't experience any bugs in sj, but I would like to see the raw XML
> >messages that are sent back and forth via sj, messaged, iqd, and
> >presenced, in order to be able to understand
I don't experience any bugs in sj, but I would like to see the raw XML
messages that are sent back and forth via sj, messaged, iqd, and
presenced, in order to be able to understand better.
These programs write to "in" files (named pipes). So what is the best
(easiest, most convenient) way to
On 12/01/2015 10:55 AM, Greg Reagle wrote:
I don't experience any bugs in sj, but I would like to see the raw XML
messages that are sent back and forth via sj, messaged, iqd, and
presenced, in order to be able to understand better.
These programs write to "in" files (named pipes). So what is
