Re: lock on candidate

[Phil Shafer <phil@juniper.net>]

Yes, all outstanding changes are discarded, which effectively
restores the candidate to the current running config.

Thanks,
 Phil



Martin Bjorklund writes:
>Hi,
>
>Another detail.  Section 8.3.5.1. talks about lock on the candidate.
>It says:
>
>   To facilitate easy recovery, any outstanding changes are discarded
>   when the lock is released
>
>What does 'discard' mean here?  Does it mean the same as
><discard-changes>, which copies the *current* running to the
>candidate, or does it mean the state the candidate was in before the
>lock was set?
>
>
>/martin
>
>--
>to unsubscribe send a message to netconf-request@ops.ietf.org with
>the word 'unsubscribe' in a single line as the message text body.
>archive: <http://ops.ietf.org/lists/netconf/>

--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>