Feature Request: persistent chronology

Moderator: Project members

Post Reply
Message
Author
barbatrukko
500 Command not understood
Posts: 2
Joined: 2022-01-13 07:11
First name: Pinco
Last name: Pallino

Feature Request: persistent chronology

#1 Post by barbatrukko » 2022-01-13 07:18

Hi,
I am working on a pc that often reboots. When I transfer files with filezilla I can see which files have been transferred successfully and which ones have had problems ...
However, if during the night the PC restarts, the next morning I have no more information on which file has been transferred and which not and I have to recreate the queue and check what remains to be copied.
It would be convenient for the queue and other information on the status of the transfers to be persistent and in case of restarting the PC when Filezilla is reopened, to automatically have the status at the moment before the restart.

User avatar
botg
Site Admin
Posts: 34006
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse
Contact:

Re: Feature Request: persistent chronology

#2 Post by botg » 2022-01-13 09:29

The queue is being persisted if FileZilla is closed.

How is the system rebooted? Gracefully, with all programs closed down properly, or abrupt e.g. by pulling the plug?

barbatrukko
500 Command not understood
Posts: 2
Joined: 2022-01-13 07:11
First name: Pinco
Last name: Pallino

Re: Feature Request: persistent chronology

#3 Post by barbatrukko » 2022-01-13 11:21

no, PC will reset bad....
I believe there is a sudden RESET: I lose the Remote desktop connection and have to wait for the restart (slow after a brutal failure).
Precisely for this type of inconvenience that can occur it would be convenient for the software to save the status of the queues from time to time even before being shut down.

User avatar
botg
Site Admin
Posts: 34006
Joined: 2004-02-23 20:49
First name: Tim
Last name: Kosse
Contact:

Re: Feature Request: persistent chronology

#4 Post by botg » 2022-01-14 09:29

That is unfortunate.

For performance reasons FileZilla only saves the queue when it shuts down. With large queues saving can take a considerable amount of time. Saving more often would also introduce weirdness if one were then to start a second copy of FileZilla.

Post Reply