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 the beginning, but not so bad. On 2 August 2012 09:35, Benny Amorsen <[email protected]> wrote: > 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 failing. > > > /Benny > > > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
