Re: Custom logging in libssh

2019-01-20 Thread g4-lisz
On 17.01.19 17:02, g4-l...@tonarchiv.ch wrote: > I just foundĀ  ssh_set_log_callback() , so gladly I was wrong and it's > not session-wise. But I think it still needs some sychnromization to > write to a file from several sessions? Hello again It seems that I have to set log callback and verbositi

Re: Custom logging in libssh

2019-01-19 Thread g4-lisz
On 17.01.19 18:57, g4-l...@tonarchiv.ch wrote: > On 17.01.19 17:29, Andreas Schneider wrote: >> On Thursday, January 17, 2019 5:02:24 PM CET g4-l...@tonarchiv.ch wrote: >>> On 17.01.19 16:40, g4-l...@tonarchiv.ch wrote: I try to accomplish two things: 1) My libssh client should run

Re: Custom logging in libssh

2019-01-17 Thread g4-lisz
On 17.01.19 17:29, Andreas Schneider wrote: > On Thursday, January 17, 2019 5:02:24 PM CET g4-l...@tonarchiv.ch wrote: >> On 17.01.19 16:40, g4-l...@tonarchiv.ch wrote: >>> I try to accomplish two things: >>> >>> 1) My libssh client should run as a deamon. So logging should go to a file >>> 2) I

Re: Custom logging in libssh

2019-01-17 Thread Andreas Schneider
On Thursday, January 17, 2019 5:02:24 PM CET g4-l...@tonarchiv.ch wrote: > On 17.01.19 16:40, g4-l...@tonarchiv.ch wrote: > > I try to accomplish two things: > > > > 1) My libssh client should run as a deamon. So logging should go to a file > > 2) I also want to use logging from my own code > > >

Re: Custom logging in libssh

2019-01-17 Thread g4-lisz
On 17.01.19 16:40, g4-l...@tonarchiv.ch wrote: > I try to accomplish two things: > > 1) My libssh client should run as a deamon. So logging should go to a file > 2) I also want to use logging from my own code > > [...] > > Now it seems that logging is configured session-wise. So writing to the > lo

Custom logging in libssh

2019-01-17 Thread g4-lisz
Hi there, I try to accomplish two things: 1) My libssh client should run as a deamon. So logging should go to a file 2) I also want to use logging from my own code Concerning 1: I can't find an option to tell libssh where the logging should go. So I guess that I have to write a logging callback