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.