You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Daemons must be running for vtysh to be able to collect their configuration. Any configuration from non-running daemons is permanently lost after doing a configuration save.
In this case, when I stop a daemon for a while, I may lose the configuration of that daemon. It can be very frustrating if the config was large, for example. This behavior is not so obvious and looks like a bug. Like as a documented bug.
I understand that it is a consequence of the integrated configuration feature. And it works as it works. But I want to understand why this restriction was introduced, what were the preconditions, and why is this interpreted as the norm?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
The official FRR documentation says:
In this case, when I stop a daemon for a while, I may lose the configuration of that daemon. It can be very frustrating if the config was large, for example. This behavior is not so obvious and looks like a bug. Like as a documented bug.
I understand that it is a consequence of the integrated configuration feature. And it works as it works. But I want to understand why this restriction was introduced, what were the preconditions, and why is this interpreted as the norm?
Beta Was this translation helpful? Give feedback.
All reactions