Thanks
Thank you very much! I had overlooked that part of the doc.
Much appreciated!!
Much appreciated!!
- ipisors
Post a reply
Before posting, please read how to report bug or request support effectively.
Bug reports without an attached log file are usually useless.
Topic review
- martin
Re: Make logging non-cumulative
Use
https://winscp.net/eng/docs/rawconfig#logging_logfileappend
Or use a timestamped log file:
https://winscp.net/eng/docs/ui_pref_logging#session_log
/rawconfig Logging\LogFileAppend=0
https://winscp.net/eng/docs/rawconfig#logging_logfileappend
Or use a timestamped log file:
/log=!Y!M!D!T.log
https://winscp.net/eng/docs/ui_pref_logging#session_log
- ipisors
Make logging non-cumulative
Hello, I have script that operates winscp on command line to put an FTP file. After my script runs, I'd like to check the WinSCP log file to see if it was successful. However, it is very difficult to create logic to check the log file, because the log file is cumulative and includes results from a lot of other times I've sent the command line.
Is there a way to change it so that every time I command line WinSCP, it creates a log file with "just the results from that one execution"? Or otherwise isolate the current execution – maybe by force-placing certain explicit text inside the log file?
Is there a way to change it so that every time I command line WinSCP, it creates a log file with "just the results from that one execution"? Or otherwise isolate the current execution – maybe by force-placing certain explicit text inside the log file?