Fixing this will likely require a change to the base program, but I think it would be a valuable change as I can't envision a use case where the current scheme is ever desired (that is, sleeping or shutting down while a "Run a command" is still running in the background). The "When finished" action (on the progress screen) only looks at the actual backup job and doesn't take into account any "Run a command" action specified on the Synchronization screen. I played around with numerous flavors of invoking the batch job as you suggest, but suspect the problem is internal to the FFS program. My desire is to be able to add the sleep while the job is already running, so cases when it's running long and I want to "go home" and know it'll finish and sleep the PC when complete, without having to make that decision when I invoke the job. While I appreciate the response, as I stated in my 3rd paragraph, I already have sleeping from the batch file working (I prefer to use Steve Gibson's wizmo.exe for the sleep function - works flawlessly). For example, if a long job is running past quitting time and I don't want my PC left on all night, I'd like to be able to set the "System: Sleep" and then walk away knowing it'll all complete and then sleep the PC. I already know I can just add the "system sleep" to the end of my "Run a command" batch script and not use the "When finished" function (that's my work-around right now), but I like the ability to add the "System: Sleep" after the job is already running rather than having to decide to do the sleep at the start of the job. End-to-End Encryption Rclone has E2E Encryption, for entire or parts of the app. Lightweight Rclone consumes less device resources compared to similar apps. Cloud Sync Sync your data (notes, documents, bookmarks, etc.) across your different devices and to the cloud. My preference is that the add-on "Run a command" be considered part of the overall job and the "When Finished" action is executed after the "Run a command" has completed. Command line interface Rclone either have CLI support or is a CLI-only app. I have a batch script I run at the completion of a job that takes ~30 seconds to complete, but it doesn't get a chance to finish as the "When finished" action kicks in immediately after the actual copy job is complete.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |