@@ -2757,6 +2757,26 @@ let docs =
2757
2757
\032 cleanup procedures and terminates the process forcibly (similar to\n \
2758
2758
\032 SIGKILL). Doing so may leave the archives or replicas in an\n \
2759
2759
\032 inconsistent state or locked.\n \
2760
+ \032 When synchronizing continuously (time interval repeat or with\n \
2761
+ \032 filesystem monitoring), interrupting with \226\128\156 Ctrl-C\226\128\157 or with signal\n \
2762
+ \032 SIGINT or SIGTERM works the same way as described above and will\n \
2763
+ \032 additionally stop the continuous process. To stop only the\n \
2764
+ \032 continuous process and let the last synchronization complete\n \
2765
+ \032 normally, press \226\128\156 Ctrl-D\226\128\157 or send signal SIGUSR2 instead. Closing\n \
2766
+ \032 the input, receiving an EOF, or receiving a ^D (0x04) from the\n \
2767
+ \032 input terminal or a redirected standard input all have the same\n \
2768
+ \032 effect. EOF is not interpreted as a stop request when standard\n \
2769
+ \032 input is redirected from a regular file. If the standard input is\n \
2770
+ \032 not open or is not open for reading already at Unison startup then\n \
2771
+ \032 it is ignored and only signals can be used to send the stop\n \
2772
+ \032 request.\n \
2773
+ \n \
2774
+ \032 Tips: For continuous synchronization the input should not be\n \
2775
+ \032 redirected from any source providing a lot of input (such as an\n \
2776
+ \032 existing regular file larger than a few tens of bytes or a device or\n \
2777
+ \032 a pipe that produces large quantities of data). In such cases,\n \
2778
+ \032 Unison would keep reading all the input looking for the stop\n \
2779
+ \032 condition.\n \
2760
2780
\n \
2761
2781
Exit Code\n \
2762
2782
\n \
0 commit comments