diff options
| author | Holger Hans Peter Freyther <holger@moiji-mobile.com> | 2014-11-21 10:40:07 +0100 |
|---|---|---|
| committer | Holger Hans Peter Freyther <holger@moiji-mobile.com> | 2014-12-04 14:39:14 +0100 |
| commit | 9f0f978c8daa764d01f0892ef7b5e443f7c551a8 (patch) | |
| tree | eac141be7b7139b0f3b4fb18b7fb1042f9f6ee72 /include/osmocom/vty/vty.h | |
| parent | e15ac060e7ae78d4c3569d7fc9071bcf49807e05 (diff) | |
vty: Check with the application before writing the config
For the BSC/NITB application we see that people modify the band
without modifying the ARFCN. This creates an unbootable config.
Using the new hook the BSC/NITB can check if the config is
consistent and prevent the config file being written.
Related: SYS#739
Diffstat (limited to 'include/osmocom/vty/vty.h')
| -rw-r--r-- | include/osmocom/vty/vty.h | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/include/osmocom/vty/vty.h b/include/osmocom/vty/vty.h index ea02e4a0..1dcc2300 100644 --- a/include/osmocom/vty/vty.h +++ b/include/osmocom/vty/vty.h @@ -159,6 +159,8 @@ struct vty_app_info { enum node_type (*go_parent_cb)(struct vty *vty); /*! \brief call-back to determine if node is config node */ int (*is_config_node)(struct vty *vty, int node); + /*! \brief Check if the config is consistent before write */ + int (*config_is_consistent)(struct vty *vty); }; /* Prototypes. */ |