diff options
| author | Donatas Abraitis <donatas@opensourcerouting.org> | 2023-06-30 12:58:32 +0300 |
|---|---|---|
| committer | Donatas Abraitis <donatas@opensourcerouting.org> | 2024-07-25 11:28:42 +0300 |
| commit | 3c2529c783453a94437105e5570e7864c92d95e4 (patch) | |
| tree | f0b6ed17b7e13cbe1bcf928417460791b949db74 | |
| parent | 5957a4697f3b11d318309142a61a55c34c4f9c19 (diff) | |
tools: Ignore errors for frr reload stuff
When we pass an unknown/wrong command and do `systemctl reload frr`, all processes
are killed, and not started up.
Like doing with frr-reload.py, all good:
```
$ /usr/lib/frr/frr-reload.py --reload /etc/frr/frr.conf
vtysh failed to process new configuration: vtysh (mark file) exited with status 2:
b'line 20: % Unknown command: neighbor 192.168.10.123 bfd 300 300\n\n'
```
Signed-off-by: Donatas Abraitis <donatas@opensourcerouting.org>
| -rw-r--r-- | tools/frrinit.sh.in | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tools/frrinit.sh.in b/tools/frrinit.sh.in index ee10b89e52..b0579ca0c4 100644 --- a/tools/frrinit.sh.in +++ b/tools/frrinit.sh.in @@ -123,7 +123,7 @@ reload) NEW_CONFIG_FILE="${2:-$C_PATH/frr.conf}" [ ! -r $NEW_CONFIG_FILE ] && log_failure_msg "Unable to read new configuration file $NEW_CONFIG_FILE" && exit 1 "$RELOAD_SCRIPT" --reload "$NEW_CONFIG_FILE" `echo $nsopt` - exit $? + exit 0 ;; *) |