Tõivo Leedjärv
Tõivo Leedjärv
Add ability to specify custom prog/script to run on each file to decide whether to include or ignore
This is mentioned in https://github.com/bcpierce00/unison/issues/80#issuecomment-347319726 and a workaround in https://github.com/bcpierce00/unison/issues/80#issuecomment-381113502
This is by design. Repeat mode is not intended for use in scripts/batch. What would that even mean? What is your intention with running in repeat mode (which by definition...
You are welcome to clarify the request in the mailing list but I really don't think you need one. > The aforementioned batch monitors the connection and, upon sync-error, returns...
> unison fills the log with unnecessary information about a fatal error I agree, this is something that should be fixed.
> Sounds like we should have a new issue for exiting on fatal errors. Ah, no, that's not it. It's about spamming the log about "fatal" errors when in fact...
I'm currently thinking about a solution which would silence repeat errors and be explicit about it. So the user knows that the error condition persists until something else is logged...
@acsysch if you are able to, you may want to try a build from https://github.com/tleedjarv/unison/actions/runs/8377886894 (scroll to bottom) which is 2.53.4 + some patches. The patches are intended to make...
> * we need exponential backoff (roughly) for reconnect attempts, because retrying every 10s is not reasonable to the network and the remote system, in case of persistent problems or...
Thank you for testing, I will go ahead an open a PR with this patch. > But I would even go further by adding the option to exit in such...
Correcting some factual errors that have been stated: SIGTERM works, as does SIGINT. SIGUSR2 can be used for even more graceful shutdown. > then it should be able to write...