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.
Feature Request: persistent chronology
Moderator: Project members
-
- 500 Command not understood
- Posts: 2
- Joined: 2022-01-13 07:11
- First name: Pinco
- Last name: Pallino
Re: Feature Request: persistent chronology
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?
How is the system rebooted? Gracefully, with all programs closed down properly, or abrupt e.g. by pulling the plug?
-
- 500 Command not understood
- Posts: 2
- Joined: 2022-01-13 07:11
- First name: Pinco
- Last name: Pallino
Re: Feature Request: persistent chronology
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.
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.
Re: Feature Request: persistent chronology
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.
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.
-
- 504 Command not implemented
- Posts: 7
- Joined: 2022-02-21 22:41
- First name: Bar
- Last name: Barus
Re: Feature Request: persistent chronology
It would also be nice to have persistent tabs. When I restart FileZilla for updating I have to remember and reopen all my tabs manually except the last one. (Apologies if this is too different to belong in the same topic)
Re: Feature Request: persistent chronology
No support requests over PM! You will NOT get any reply!!!
FTP connection problems? Please read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
FileZilla Pro support: https://customerforum.fileZilla-project.org
FTP connection problems? Please read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
FileZilla Pro support: https://customerforum.fileZilla-project.org
-
- 504 Command not implemented
- Posts: 7
- Joined: 2022-02-21 22:41
- First name: Bar
- Last name: Barus
Re: Feature Request: persistent chronology
Thank you!!