@guitarzan8: What do you miss at the -1 level?
Where's the example of what Enable Session logging on level is?
Does this mean set
/loglevel=-2. How low does it go..
/loglevelswitch are documented in the
It would be very helpful to have a less verbose (non-xml) logging option. A log with logon/logoff, commands, what files have been moved, and any failures and close/exit. Is this an unrealistic/not-going-to-happen request? Its just that the current debug log is hard to use at all and it grows so fast it has to be backed up frequently.
To enable logging to a file, check Enable session logging on level.
To increase a verbosity of the session log, select Debug 1 or Debug 2 level. You will probably need these (together with a logging to file), when reporting bugs only. To decrease a verbosity of the session log, select Reduced level
/loglevel=-2. How low does it go.
It reads like a debug log.
Is it possible some form of non xml simple logging could be added?
Text log: Events are logged in unstructured form with configurable level of verbosity.
WinSCP.exein an NT shell script, and it is working nicely. I use the
/log=C:\MyLogFile.logoption. The problem is that WinSCP provides "too much information" (as they say in America!).