Post a reply

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

Abdam

nealobrien wrote:

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.


I 100% agree. Usually for scripted commands these are so they can transfer files over night when our Systems/Network are not being used, so we would like logging to know what it's actually moved/deleted and not anything on a debugging level as it makes the logs so hard to understand when just wanting to see if it's moved something. It gets confusing when it compares it, says if it's going to ignore it or not etc. When all we need is the actual change/action it's doing to a file.

Also when viewing it from the command screen without logging to a file it shows you all the files including their full paths, but as it moves so quickly you don't know what it's doing (comparing, moving, anything else etc...). It also at one point just shows you file names, I guess this is actually coping them at this point but as there is no file path to go with it, I have no idea what it's doing or moving specifically. We have many directories with the same files in them for our customers and we can't tell what customer has been copied specifically.

Even the guides are confusing with not very many examples, just more "text". The saying "Pictures paint 1000 words" comes to mind with examples:

To enable logging to a file, check Enable session logging on level.
" Where's the example of what Enable Session logging on level is?

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

Does this mean set
/loglevel=0
,
/loglevel=-1
,
/loglevel=-2
. How low does it go..

These are all rhetorical questions of possible thoughts going through the users mind. Not everyone is on a developer mind set but actually want to use the product clearly.
martin

nealobrien wrote:

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.

I do not think I like an idea of having third log file format.
nealobrien

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.
martin

Re: Feature Request

nealobrien wrote:

It reads like a debug log.

That's what it is.

Is it possible some form of non xml simple logging could be added?

XML can be converted to anything you like easily. E.g. using XSLT.
nealobrien

Feature Request

The verbosity of the logging really does make it hard to use. It would be nice if upon error the log dumped all these details but with success was more succinct, for example just listing the open/close and files transferred. It reads like a debug log. Is it possible some form of non xml simple logging could be added?
FlatlanderByTheLake

A follow-up question about logging to a file. At the following page...

https://winscp.net/eng/docs/logging

... it says the following:

"Text log: Events are logged in unstructured form with configurable level of verbosity."

How do I configure the level of verbosity?

Thanks
Flatlander
martin

Re: How to make /log option less verbose?

Try using XML logging.
FlatlanderByTheLake

How to make /log option less verbose?

Hello,

I am using WinSCP.exe in an NT shell script, and it is working nicely. I use the "/log=C:\MyLogFile.log" option. The problem is that WinSCP provides "too much information" (as they say in America!).

Is there a way to specify that the logs be less verbose?

Thanks in advance.

Tim