You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have just started running dsc watch and am worrying about a failure mode: When dsc watch isn't running and, e.g., an ADF scanner uploads new documents to an SFTP drop directory, starting the dsc watch job does not cause it to submit the files that were previously uploaded.
I guess I can construct a systemd unit that works like this, but probably still has a race condition (e.g. a file getting uploaded at exactly the right/wrong point in time). I think I would love to see this solved in the watch command itself.
The text was updated successfully, but these errors were encountered:
Yeah, that's an interesting question.I have no good idea how to solve this. Can only think of periodically doing the dsc upload --traverse once in a while. Or maybe after starting the watch command use a find to get all files added in the last n minutes and touch them. But it's hard to say how long to look back. Hm, this could be done in the watch command but seems quite expensive (for large directories) for this case…? It is also possible to do this as a ExecStartPost in the systemd unit.
I have just started running
dsc watch
and am worrying about a failure mode: Whendsc watch
isn't running and, e.g., an ADF scanner uploads new documents to an SFTP drop directory, starting thedsc watch
job does not cause it to submit the files that were previously uploaded.I guess I can construct a systemd unit that works like this, but probably still has a race condition (e.g. a file getting uploaded at exactly the right/wrong point in time). I think I would love to see this solved in the
watch
command itself.The text was updated successfully, but these errors were encountered: