VRRP Json dump readiness notifications about keepalived HOT 2 CLOSED

@saikanuri This all depends on what you mean by "whenever there's a modification on the configuration". My understanding of a modification to the configuration is that the configuration file is modified and SIGHUP is sent to keepalived to make it reload its configuration (1). If on the other hand you mean if, for example, a VRRP instance changes from master to backup state, then you would like the JSON dumped (2), then that is another matter.

Re (1), since some outside agent (script or person) has triggered the configuration reload, then that agent could also send SIGJSON, and so there is no need to modify keepalived. I you mean something like (2) above, then you will need to define what events should trigger a re-write of the JSON file. However, you can probably use a notify_fifo together with a notify_fifo_script to be notified of relevant events, and then send a SIGJSON from the script.

The explanation for why a temporary file is created and then renamed to keepalived.json is given in a long(ish) comment in fopen_safe() in lib/utils.c. You can still monitor what is happening using inotify if you monitor the directory (default /tmp) using inotify, rather than monitoring the keepalived.json file itself.

from keepalived.

Closing due to no response for over 4 months.

from keepalived.