[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lock
>>>>> On Sun, 11 Dec 2005 23:44:56 -0500, Phil Shafer <phil@juniper.net> said:
Martin> * the target configuration is 'candidate' and it has already
Martin> been modified and these changes have not been committed or
Martin> rolled back.
Martin>
Martin> What is the purpose of this condition?
Phil> To prevent applications from (a) stealing the lock while a human
Phil> user is in the process of making changes, and (b) preventing the
Phil> script from committing changes which it did not make.
Martin: Note that the case you brought up about a user locking himself
out of his own changes is one of many examples where locking can
actually be misused. The more interesting cases, IMHO, are the ones
where user B has made changes to the candidate config that user A
isn't allowed to change. In this case, A can no longer commit the
changes, get a lock, discard the changes, etc. IE, B doesn't have to
lock the candidate configuration in order to make user A loose all
ability to deal with the candidate configuration set in any useful way.
>>> Then, before committing, A wants to do another change. So A
>>> tries to grab the lock again - but this will fail since there are
>>> uncommitted changes.
Phil> "A" would have no idea what changes are outstanding when it re-aquired
Phil> the lock. Its changes could have been discarded, committed, or added
Phil> to. If you could release the lock with outstanding changes or aquire a
Phil> lock with outstanding changes the application would have no idea of the
Phil> state of the configuration.
Phil> Thanks,
Phil> Phil
Phil> --
Phil> to unsubscribe send a message to netconf-request@ops.ietf.org with
Phil> the word 'unsubscribe' in a single line as the message text body.
Phil> archive: <http://ops.ietf.org/lists/netconf/>
--
"In the bathtub of history the truth is harder to hold than the soap,
and much more difficult to find." -- Terry Pratchett
--
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/>
- References:
- Re: lock
- From: Phil Shafer <phil@juniper.net>