... | @@ -12,7 +12,7 @@ If that variable is defined then the archives will be created and used. Each in |
... | @@ -12,7 +12,7 @@ If that variable is defined then the archives will be created and used. Each in |
|
|
|
|
|
The `guardutil archive-clone` command can be used to clone the code repositories, to inspect the guardian user code that was running at any point in time. It uses the same GUARDIAN_ARCHIVE_ROOT environment variable to find the appropriate archive path.
|
|
The `guardutil archive-clone` command can be used to clone the code repositories, to inspect the guardian user code that was running at any point in time. It uses the same GUARDIAN_ARCHIVE_ROOT environment variable to find the appropriate archive path.
|
|
|
|
|
|
If no directory is provided a gui interface will be displayed for visual inspection of each commit in the repository (actually just [gitk](https://git-scm.com/docs/gitk)). If a directory path argument is provided the full archive will be cloned in that directory:
|
|
If no directory is provided a gui interface ([gitk](https://git-scm.com/docs/gitk)) will be presented, allowing for visual inspection of each commit in the archive repository. If a directory path argument is given, the system archive repo will be cloned in that directory:
|
|
```shell
|
|
```shell
|
|
jameson.rollins@opsportal:~ 0$ guardutil archive-clone ISC_LOCK tmp/
|
|
jameson.rollins@opsportal:~ 0$ guardutil archive-clone ISC_LOCK tmp/
|
|
jameson.rollins@opsportal:~ 0$ cd tmp/ISC_LOCK/
|
|
jameson.rollins@opsportal:~ 0$ cd tmp/ISC_LOCK/
|
... | | ... | |