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.

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

martin

Re: WinScp lock the directory (version 5.8.4.0)

It should not happen. The winscp.exe is a part of a job created by the .NET assembly.
https://docs.microsoft.com/en-us/windows/win32/procthread/job-objects

Anyway, how do you stop the service? Is the process shut down cleanly or is it killed?

Please attach a debug log file (Session.DeubgLogPath)
dharmdatt.sharma

WinScp lock the directory (version 5.8.4.0)

I am using Windows 7 and application is a windows service. If the service is stopped when download/upload is in-progress, the folder is locked and winscp.exe remains in memory (i can see it in Task Manager). Until I kill that process manually, the folder is unusable.
martin

Re: WinScp lock the directory (version 5.8.4.0)

dharmdatt.sharma wrote:

Whenever my application (which is using winscp) is stopped when winscp is in action, the folder where download is happening is locked until system is rebooted. What could be the problem? Please note that i am having "using" block wherever session is used.

This should not be happening. What is your version of Windows? How do you "stop" the application? Is winscp.exe process left behind, when you "stop" the application.
Guest

Re: WinScp lock the directory (version 5.8.4.0)

dharmdatt.sharma wrote:

Whenever my application (which is using winscp) is stopped when winscp is in action, the folder where download is happening is locked until system is rebooted. What could be the problem? Please note that i am having "using" block wherever session is used.


File Version is 1.3.3.6736
Product Version is 5.8.4.0
dharmdatt.sharma

WinScp lock the directory (version 5.8.4.0)

Whenever my application (which is using winscp) is stopped when winscp is in action, the folder where download is happening is locked until system is rebooted. What could be the problem? Please note that i am having "using" block wherever session is used.
martin

Re: directory listing lock-up when following simlink to another filesystem

WinSCP follows link to detect whether it points to file or directory. Of course it is a bug to follow recursive symlink, I'll fix it sometimes.
Guest

Re: directory listing lock-up when following simlink to another filesystem

Got the problem. In the directory being read in the remote filesystem, there is a symlink of this kind:

lrwxrwxrwx 1 giov users 4 Jan 27 2002 exec -> exec

which obviously something made by mistake. But as soon as Winscp finds it, it immediately tries to follow it (why?), which of course is a neverending affair. From the winscp log:

. Listing file "exec".
> ls -lad "exec" ; echo "WinSCP: this is end-of-file:$?"
< lrwxrwxrwx 1 giov users 4 Jan 27 2002 exec -> exec
< WinSCP: this is end-of-file:0
(repeated many and many times).

It is true that this simlink is recursive, but heck, it is just a symlink, so it is legal in unix, albeit a bit stupid. Why winscp tries to follow it? Nobody told to open that directory... Note that I was trying to read the directory where the link IS, not trying to open the link itself.
martin

Re: directory listing lock-up when following simlink to another filesystem

Please send me a log file.
deepsky

directory listing lock-up when following simlink to another filesystem

WinSCP locks up when I try to browse a certain directory on the remote server (a Linux machine). It happens just with that one, so I suppose it is a bug.
This directory it is actually a link to a directory in another filesystem:

lrwxrwxrwx 1 giov users 28 May 29 2002 web -> /usr/local/httpd/htdocs/giov

Of course in normal conditions I have permissions to browse this directory, which is owned by me.
But if I try to enter into this directory with winscp, the program locks up and I have to ctrl-alt-del to terminate it.
Looks like a bug...