Attention is currently required from: fixeria.

2 comments:

Commit Message:
- Patch Set #1, Line 9:
```
Saving the current configuration by doing 'write file [FILE]' breaks
the 'show startup-config' command.  If write succeeds, this command
will be showing contents of the new (potentially modified) file.
```
  this is exactly how it would behave on a cisco device, isn't it? If you write to the file (basically `copy running-config startup-config`, then the [next] startup config is exactly the same as what you're running right now. I don't see a bug here.
- Patch Set #1, Line 12: If
  Doesn't that mean that the write is then broken? The write should probably always write to a newly-created file, and only after that succeeds unlink the old file and rename the new file, to ensure we always have either the old (unsuccesful write) or the new (successful write) config. If there is a related bug, it should be fixed in the write, and not worked around here?

To view, visit change 40187. To unsubscribe, or for help writing mail filters, visit settings.