Logging not working until session/Winscp is closed

Advertisement

naeco
Guest

Logging not working until session/Winscp is closed

Hi!

I'm running 5.8.4rc and find that logs are no longer created simultaneously during sessions. Only after closing the session or the client will the log be generated.

I assume that this behavior occurs due to the recent removal of log window.

It's quite inconvenient when in the middle of a running session, I have to check the log whether a file has been sent.

I really hope it is not intended to be so after log window removal. :)

For now I'm falling back to 5.8.2 beta where logging work as intended.

Best regards,
NHH

Reply with quote

Advertisement

martin
Site Admin
martin avatar
Joined:
Posts:
27,226
Location:
Prague, Czechia

Re: Logging not working until session/Winscp is closed

I'm not sure I understand. If I open two sessions at the same time (in two tabs), using WinSCP 5.9, both create their own log files.

Reply with quote

Guest

Re: Logging not working until session/Winscp is closed

martin wrote:

I'm not sure I understand. If I open two sessions at the same time (in two tabs), using WinSCP 5.9, both create their own log files.

I've just got 5.9 downloaded and running.

At first, in file explorers, it looked like that logs are still not generated during a running session (file size and time stamp are unchanged even after refresh, 0Kb at the beginning of the day). However, I trusted in your reply so I opened the log file and voilà.. Upon opening the file, the log is generated and updated. :)

A little confusing since the files are not updated on-the-fly, but knowing how it works now, I can work with it

Cheers!

Reply with quote

martin
Site Admin
martin avatar
Joined:
Posts:
27,226
Location:
Prague, Czechia

Re: Logging not working until session/Winscp is closed

A little confusing since the files are not updated on-the-fly, but knowing how it works now, I can work with it
This has nothing to do with WinSCP. I hope you understand, that it's not WinSCP that somehow magically checks that you try to read the log file and updates the file only afterwards. WinSCP writes the log continuously. It's Windows that somehow caches a file information, probably for performance reasons.

Reply with quote

Advertisement

You can post new topics in this forum