Hi, The correct way of doing this is int verbosity=SSH_LOG_FUNCTIONS; ssh_options_set(session, SSH_OPTIONS_LOG_VERBOSITY, &verbosity);
The log pops on stderr. If it's not possible to use stderr, it is possible to define a callback for a log function but it's a little more complicated. Aris Eduardo Valdes a écrit : > Aris, > > Thanks for the response. > Is there something I need to do to generate a log other than > ssh_options_set(session, SSH_OPTIONS_LOG_VERBOSITY, SSH_LOG_FUNCTIONS)? > Where should the log file wind up? > > Eddy > > > On Mon, Mar 15, 2010 at 8:21 AM, Aris Adamantiadis <[email protected] > <mailto:[email protected]>> wrote: > > Hi Eduardo, > > Have you got any code sample that exhibits that behaviour ? Could you > generate a verbose output of libssh so we get a better idea of what's > happening ? > Having this for both linux and windows would help me to diagnose the > problem the most efficiently. > > Thanks, > > Aris > > Eduardo Valdes a écrit : > > I am working on a cross-platform Freepascal application that uses > > libssh. My issue is that libssh does not seem to behave correctly > under > > Windows. I am using libssh 0.4.1. > > > > My application uses the SCP and channel functionality of libssh and > > everything works correctly in Linux. In Windows, ssh_scp_push_file > fails. > > After ssh_scp_push_file fails, the ssh_get_error call on the SCP > object > > returns nothing. The ssh_get_error call on the session object returns > > "Server specified invalid channel 44". > > > > In my testing I am talking to the same SSH server regardless of > which OS > > I am testing. > > > > Any assistance would be appreciated. > > > > Eddy > > > > -- > > Eddy Valdes > > Project Manager > > Atronix Engineering > > [email protected] > <mailto:[email protected]> > <mailto:[email protected] > <mailto:[email protected]>> > > > > > > > > -- > Eddy Valdes > Project Manager > Atronix Engineering > [email protected] <mailto:[email protected]> >
