Skip to content

Conversation

donaldsharp
Copy link
Member

Our startup scripts allow the passing of a cli command to all daemons started. Recently -w was added to handle namespaces better, but watchfrr was not included. This caused people using startup scripts to be a bit unhappy. Let's get them rolling by adding a quick and dirty ignoring of that flag to watchfrr.

Fixes: #18107

@donaldsharp
Copy link
Member Author

I believe the format warnings are wrong and should be ignored

Copy link
Contributor

@eqvinox eqvinox left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

$frr_global_options should be removed from watchfrr calls in the init script instead

watchfrr is currently being started with $frr_global_options
This is problematic as that it has a entirely different cli
than the rest of the daemons and we have no plans to make
this equivalent.

Fixes: FRRouting#18107

Signed-off-by: Donald Sharp <sharpd@nvidia.com>
@donaldsharp donaldsharp force-pushed the w_option_for_watchfrr branch from f94bb23 to 9101bff Compare February 13, 2025 16:42
@frrbot frrbot bot added the tools label Feb 13, 2025
@github-actions github-actions bot added size/XS and removed size/S labels Feb 13, 2025
@donaldsharp
Copy link
Member Author

I rewrote it the way that @eqvinox has suggested and tested it. Works.

@eqvinox eqvinox merged commit 196b7f1 into FRRouting:master Feb 13, 2025
15 checks passed
@donaldsharp donaldsharp deleted the w_option_for_watchfrr branch July 30, 2025 17:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Adding -w option to frr_global_options field in /etc/frr/daemons prevents frr from starting
2 participants