Opened 16 years ago

Last modified 15 years ago

#626 closed Bug report

filehandle not released after non-successfull transfer

Reported by: anonymous Owned by:
Priority: normal Component: Other
Keywords: Cc: Tim Kosse
Component version: Operating system type:
Operating system version:

Description

Hi,

if a file upload fails because the destination file
already exists and is write protected, the file handle
is locked. If this is a source file for example that
has to be edited again, you are unable to save that
file in your editor unless you close filezilla and so
release that file. Removing the failed file transfer
from the queue does not work, filezilla has to be
closed completely. This is annoying because every
cvs-driven development relies on the read-only file
protection stuff and so I often have the requirement to
overwrite read-only files.
Wouldn't it make sense just to ask per popup "warning,
write protected! Really overwrite?"

If this behaviour is too risky for most of the users, a
preference caption like "[ ] automatically ask for
overriding read-only files" would do the trick.

Greetings from Lüneburg/Germany,
Eckard

Change History (1)

comment:1 Changed 15 years ago by Tim Kosse

This bug report has been closed due to inactivity and has possibly
already been solved.

You can reopen this report if the issue still exists in the
latest version of FileZilla (Server).

Note: See TracTickets for help on using tickets.