The changes are copied to the startup configuration automatically. As a result, the changes are preserved even after a reboot.
- Text that describes the reason for the commit.
Use this command to apply and save uncommitted changes to the configuration.
When you add configuration to, modify existing configuration in, or delete configuration from the system, the changes you make must be committed before they take effect. To commit changes, use the commit command.
If you try to exit or quit configuration mode while uncommitted configuration changes still exist, the system gives you a warning. You cannot exit configuration mode until you either commit the changes by entering the commit command or discard the changes by using the discard command.
Until a configuration change is committed, the system marks the change when displaying the information.
Committing changes can take time, depending on the complexity and activity of the system. Be prepared to wait for several minutes for the system to complete committing the changes.
If two or more users are logged into the system in configuration mode and one user changes the configuration, the other user or users receive a warning.
The following example displays a commit command that includes the system commit history and shows that the changes are automatically saved.
vyatta@vyatta# show system commit 0 2017-01-06 09:48:45 by Vyatta Set loopback interface address 1 2017-01-06 09:48:20 by Vyatta Update loopback interface description vyatta@vyatta# set interfaces loopback lo address 220.127.116.11/32  vyatta@vyatta# commit comment "Change loopback interface address"  vyatta@vyatta# run show system commit 0 2017-01-06 09:50:15 by Vyatta Change loopback interface address 1 2017-01-06 09:48:45 by Vyatta Set loopback interface address 2 2017-01-06 09:48:20 by Vyatta Update loopback interface description