[j-nsp] non-existing changes?

[daniel]

Daniel,

as soon as for example you do 'edit <some_not_yet_existing_hierarchy>' the config database gets updated with that hierarchy. When you then decide not put any statement under that hierarchy the empty hierarchy gets removed again. As far as the config is concerned there no change, but technically the db did change and this triggers such warning messages. 

This can ofcourse be changed (as with most things :), but would have some impact in the way certain things are done currently. So far this corner-case wasn't felt enough reason to warrant such effort.  

Hope this explains,
-Daniel (who spends some time in jtac every now and then ;)


On 16:33 Sun 14 Mar     , Daniel Roesen wrote:
> Hi,
> 
> dr at A1# show | compare rollback 0
>  
> [edit]
> dr at A1# exit
> The configuration has been changed but not committed
> Exit with uncommitted changes? [yes,no] (yes)
> 
> Would it be possible for JuNOS to check wether there is actually a
> difference between candidate and current config?
> 
> 
> Best regards,
> Daniel
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/juniper-nsp