mirror of
https://github.com/aptible/supercronic.git
synced 2025-09-26 20:31:17 +08:00
Fix typo
This commit is contained in:

committed by
Ashley Mathew

parent
66bf0161bb
commit
c3a5eb3479
@@ -229,7 +229,7 @@ docker kill --signal=USR2 <container id>
|
|||||||
kill -USR2 <pid>
|
kill -USR2 <pid>
|
||||||
```
|
```
|
||||||
|
|
||||||
If you are running Supercronic in an environment were sending `SIGUSR2` is a bit of a hassle, or you expect frequent updates to your crontab file, you may opt to run Supercronic with the `-inotify` flag. This will start a watch on the crontab file, reloading it on changes. An example use case would be a kubernetes pod runnning Supercronic that mounts its crontab file from a configMap. With the `-inotify` flag, any update to this configmap, provided it is not immutable, will trigger a reload in Supercronic, without you having to figure out a mechanism to send the `SIGUSR2` signal to the pod. The watch on the crontab file triggers on `Write` and `Remove` events, the latter ensures detection of kubernetes' atomic writes.
|
If you are running Supercronic in an environment were sending `SIGUSR2` is a bit of a hassle, or you expect frequent updates to your crontab file, you may opt to run Supercronic with the `-inotify` flag. This will start a watch on the crontab file, reloading it on changes. An example use case would be a kubernetes pod running Supercronic that mounts its crontab file from a configMap. With the `-inotify` flag, any update to this configmap, provided it is not immutable, will trigger a reload in Supercronic, without you having to figure out a mechanism to send the `SIGUSR2` signal to the pod. The watch on the crontab file triggers on `Write` and `Remove` events, the latter ensures detection of kubernetes' atomic writes.
|
||||||
|
|
||||||
```
|
```
|
||||||
$ ./supercronic -inotify ./my-crontab
|
$ ./supercronic -inotify ./my-crontab
|
||||||
|
Reference in New Issue
Block a user