@@ -2785,6 +2785,26 @@ let docs =
2785
2785
\032 cleanup procedures and terminates the process forcibly (similar to\n \
2786
2786
\032 SIGKILL). Doing so may leave the archives or replicas in an\n \
2787
2787
\032 inconsistent state or locked.\n \
2788
+ \032 When synchronizing continuously (time interval repeat or with\n \
2789
+ \032 filesystem monitoring), interrupting with \226\128\156 Ctrl-C\226\128\157 or with signal\n \
2790
+ \032 SIGINT or SIGTERM works the same way as described above and will\n \
2791
+ \032 additionally stop the continuous process. To stop only the\n \
2792
+ \032 continuous process and let the last synchronization complete\n \
2793
+ \032 normally, press \226\128\156 Ctrl-D\226\128\157 or send signal SIGUSR2 instead. Closing\n \
2794
+ \032 the input, receiving an EOF, or receiving a ^D (0x04) from the\n \
2795
+ \032 input terminal or a redirected standard input all have the same\n \
2796
+ \032 effect. EOF is not interpreted as a stop request when standard\n \
2797
+ \032 input is redirected from a regular file. If the standard input is\n \
2798
+ \032 not open or is not open for reading already at Unison startup then\n \
2799
+ \032 it is ignored and only signals can be used to send the stop\n \
2800
+ \032 request.\n \
2801
+ \n \
2802
+ \032 Tips: For continuous synchronization the input should not be\n \
2803
+ \032 redirected from any source providing a lot of input (such as an\n \
2804
+ \032 existing regular file larger than a few tens of bytes or a device or\n \
2805
+ \032 a pipe that produces large quantities of data). In such cases,\n \
2806
+ \032 Unison would keep reading all the input looking for the stop\n \
2807
+ \032 condition.\n \
2788
2808
\n \
2789
2809
Exit Code\n \
2790
2810
\n \
0 commit comments