[j-nsp] purpose of "commit check"?

[Aaron Dewell]

Yes, the commit will fail if commit check would have also failed.  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.  The time to fail of commit check is less than commit if there are discrepancies.  

On Sep 28, 2015, at 3:32 PM, Brad Fleming <bdflemin at gmail.com> wrote:
> I use it to make sure another admin hasn’t made changes overtop of mine. Also, I believe commit check can help in situations where you are using “edit private”.
> 
> 
>> On Sep 28, 2015, at 4:24 PM, Martin T <m4rtntns at gmail.com> wrote:
>> 
>> Hi,
>> 
>> when I commit the candidate configuration in Junos, I tend to execute
>> "commit check" and if configuration check succeeds, then I execute
>> "commit comment <COMMENT>". However, when I think about it, "commit
>> (comment)" itself should perform those very same checks that "commit
>> check" does. If yes, then what is the point of "commit check"? Only
>> purpose I could see is to check the validity of the candidate
>> configuration in the middle of the configuration process, i.e. to
>> check if the changes made in candidate configuration so far are fine
>> but the candidate configuration is not ready to be committed.
>> 
>> 
>> thanks,
>> Martin
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp