xCAT/xcat-core
2
0
Fork 0
mirror of https://github.com/xcat2/xcat-core.git synced 2026-10-21 07:08:12 +00:00
Code Issues Releases Wiki Activity

docs(imgexport): describe the destination of the bundle

Browse Source 
A local export now writes the bundle to the path of the destination.
This commit is contained in:
Vinícius Ferrão
2026-10-13 11:40:16 -03:00
parent af0781ad77
commit f8c6b2d2ed
2 changed files with 6 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/source/guides/admin-guides/references/man1/imgexport.1.rst
+3 -4
View File
@@ -125,10 +125,9 @@ OPTIONS
\ *destination*\
The output bundle file name. If remote host is specified with \ **-**\ **-remotehost**\ option,
the \ *destination*\ can include the path to the bundle file. If remote host is not
specified, the bundle file is placed in a local working directory, even if \ *destination*\
includes a path.
The output bundle file name, which can include a path. Without \ **-**\ **-remotehost**\ , a relative
path starts from the current working directory, and the directory must exist. With
\ **-**\ **-remotehost**\ , the path is on the remote host.
xCAT-client/pods/man1/imgexport.1.pod
+3 -4
View File
@@ -82,10 +82,9 @@ The name of the image. Use B<lsdef -t osimage> to find out all the image names.
=item I<destination>
The output bundle file name. If remote host is specified with B<--remotehost> option,
the I<destination> can include the path to the bundle file. If remote host is not
specified, the bundle file is placed in a local working directory, even if I<destination>
includes a path.
The output bundle file name, which can include a path. Without B<--remotehost>, a relative
path starts from the current working directory, and the directory must exist. With
B<--remotehost>, the path is on the remote host.
=back