Timeline for Unison via cron, how to deal with one job still running as the next one starts
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 24 at 15:06 | vote | accept | user149408 | ||
| May 17 at 15:30 | answer | added | Bob | timeline score: 2 | |
| May 16 at 23:55 | answer | added | Sotto Voce | timeline score: 0 | |
| May 16 at 14:24 | comment | added | Austin Hemmelgarn | Just a thought, but had you considered rclone instead of unison? The syntax is different and it would need a bit of manual configuration, but it supports essentially the same type of synchronization using it’s SFTP backend, and it also has options to limit how long a sync operation can run for (or how much data to transfer at a time), which would let you completely sidestep this issue (because you could limit it to only running for, say, 20 hours at a time, and therefore could be certain that a previous cron job isn’t still running when a new one starts). | |
| May 16 at 0:59 | history | became hot network question | |||
| May 15 at 23:15 | answer | added | Mike Pierce | timeline score: 5 | |
| May 15 at 17:25 | answer | added | larsks | timeline score: 11 | |
| May 15 at 16:53 | history | asked | user149408 | CC BY-SA 4.0 |