FUSIONINVENTORY-INJECTOR(1p) User Contributed Perl Documentation FUSIONINVENTORY-INJECTOR(1p)NAME
fusioninventory-injector - A tool to push inventory in an OCS Inventory or compatible server.
SYNOPSIS
fusioninventory-injector [options] [--file <file>|--directory <directory|--stdin]
Options:
-h --help this menu
-d --directory load every .ocs files from a directory
-f --file load a speficic file
-u --url server URL
-r --remove remove succesfuly injected files
-v --verbose verbose mode
--stdin read data from STDIN
Examples:
fusioninventory-injector -v -f /tmp/toto-2010-09-10-11-42-22.ocs --url https://login:pw@server/ocsinventory
DESCRIPTION
This tool can be used to test your server, do benchmark or push inventory from off-line machine.
perl v5.14.2 2012-06-14 FUSIONINVENTORY-INJECTOR(1p)
Check Out this Related Man Page
updmv(8) System Manager's Manual updmv(8)NAME
updmv - Moves customized, user, and inventory data files to or from storage.
SYNOPSIS
/usr/bin/updmv -i location
/usr/bin/updmv -o location
OPTIONS
Copies the Customized File Inventory (CFI) and User File Inventory (UFI) files and those files listed in these inventory files from the
specified location to the /var/adm/install/update directory. Copies the CFI and UFI files and those files listed in the inventory files to
the specified location.
OPERANDS
Specifies the storage area of the files. This area can be a tape device, disk device, or a Remote Installation Services (RIS) server area.
You replace the location operand with the name of the tape or disk device, or the server name for a RIS server area. For tape stor-
age, you must use a no-rewind tape device such as /dev/ntape/tape0_d0. For disk storage, specify the complete directory path. For
storage in a RIS server area, you must register the client in the server's RIS database. When you specify the server, the server
name must be followed by a colon (:).
DESCRIPTION
The updmv utility moves files listed in the User File Inventory (UFI) file and the Customized File Inventory (CFI) file to or from storage.
The UFI file, created by the genufi utility, identifies user files created after you installed the operating system. The CFI file, created
by the invsync utility, identifies files that were customized after the installation.
You must have superuser privileges to run the updmv utility.
During a new installation, some user files and customized files can be overwritten. You can identify and save files from the current
installation environment for later integration into the new installation environment. Use the updmv utility to move these files to a stor-
age area or from the storage area to the update area.
To store the files listed in the CFI and UFI files, invoke the updmv utility with the -o option followed by the location operand. The sys-
tem must be shut down to single-user mode before you specify the updmv utility with the -o option.
To make these files accessible for integration into a new installation environment, invoke the updmv utility with the -i option followed by
the location operand. The updmv utility moves the listed files to the /var/adm/install/update directory so that they can be merged into the
new installation environment with the updmerge utility.
EXAMPLES
Save the files to a tape device: # updmv -o /dev/ntape/tape0_d0
You must use a no-rewind tape device.
Store the files on a disk device: # updmv -o /mnt/mydata
Store the files in a RIS server area: # updmv -o midvale:
To restore these files, replace the -o option with the -i option.
Restore the files that were stored in a RIS server area: # updmv -i midvale:
The restored image resides in /var/adm/install/update.
RESTRICTIONS
You must have superuser privileges to run the updmv utility.
The system must be in single-user mode before you invoke the updmv utility with the -o option.
FILES
Customized File Inventory User File Inventory
SEE ALSO genufi(8), invsync(8), updmerge(8)updmv(8)