Change Details

D4033 introduces a lot of messages for /var/log/messages Probably best to have a specific log file.

D4033 introduces many log messages in `/var/log/messages`, which makes that file noisier and less practical to use for general system monitoring. Since these messages are specific to the CARP OVH failover logic, it is cleaner to store them in a dedicated log file instead of mixing them with unrelated system events. Using a specific log file also makes debugging easier. When investigating a CARP failover issue, we can directly inspect the dedicated log without filtering through all system messages. Adding a `newsyslog` rule also ensures these logs are rotated properly and do not grow indefinitely.

D4033 introduces a lot of messages for /var/log/messagesmany log messages in `/var/log/messages`, which makes that file noisier and less practical to use for general system monitoring. Since these messages are specific to the CARP OVH failover logic, it is cleaner to store them in a dedicated log file instead of mixing them with unrelated system events. Probably best to have a specific log file.Using a specific log file also makes debugging easier. When investigating a CARP failover issue, we can directly inspect the dedicated log without filtering through all system messages. Adding a `newsyslog` rule also ensures these logs are rotated properly and do not grow indefinitely.