"Keepuptodate" behaviours
I have a server production server I want to keep all resources to a minimum and have file transfers at specific time called by scripts. What I do is start the "keepuptodate" script at a specific time and script it to stop the process at another time.
Unfortunately starting the "keepuptodate" script only monitors for changes in a directory, which IF one happens it then starts the transfers, but there are times where all the changes have been made already, but not always. This means that it doesn't start off a transfer because there aren't any changes being made after it starts.
I know I could use the "synchronize" command for that scenario, but it's not every time that the files are there waiting as some of the time there are more files that could be added to the directory after my script has started.
Does/can the "keepuptodate" command start with a "synchronize" to make sure the directory is up-to-date and then keep monitoring the directory for any further changes?
Unfortunately starting the "keepuptodate" script only monitors for changes in a directory, which IF one happens it then starts the transfers, but there are times where all the changes have been made already, but not always. This means that it doesn't start off a transfer because there aren't any changes being made after it starts.
I know I could use the "synchronize" command for that scenario, but it's not every time that the files are there waiting as some of the time there are more files that could be added to the directory after my script has started.
Does/can the "keepuptodate" command start with a "synchronize" to make sure the directory is up-to-date and then keep monitoring the directory for any further changes?