Aaron Dewell writes: >Yes, the commit will fail if commit check would have also failed.
Yup, "commit check" just passes a flag into the commit logic which triggers an early return. >I tend to use commit >check as a check on myself when I've done a big cut-and-paste, or when >creating a bunch >of objects. "show | compare" is also useful for this sort of verification. >The time to fail of commit check is less than commit if there are >discrepancies. This shouldn't be true, given that they share the same logic. >>> If yes, then what is the point of "commit check"? Doing a pre-check before a commit is mostly about working up the confidence that you're not going to break something. We've got "commit confirmed" to help with this also. Thanks, Phil _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
