Re: [j-nsp] Commit status in SNMP

Tom Storey writes: > What about forcing the use of "configure exclusive" and "configure > private" as opposed to plain "configure"? This way you're either > locking configuration of the box to yourself for a good reason, or > multiple people/systems can work on configuration simultaneously? > > I

Re: [j-nsp] Commit status in SNMP

What about forcing the use of "configure exclusive" and "configure private" as opposed to plain "configure"? This way you're either locking configuration of the box to yourself for a good reason, or multiple people/systems can work on configuration simultaneously? Its a tiny pain to get used to in

[j-nsp] Commit status in SNMP

Is it possible via SNMP to see if the configuration is locked or whether there are uncommitted changes? If I forget to commit my changes, our automated configuration systems cannot do their job. I'm wondering if I could make OpenNMS poke me when that happens -- before the automated scripts start f