How do I install a software with Codeword ?

terça-feira, 23 de abril de 2013

You can type de Codeword direct on command line (using as paramter of swinstall):
-x codeword=xxxx and -x customer_id=xxx

Or via the Graphical User Interface (using the [Add New Codeword on "swinstall -i"] choice from the [Actions] menu).

Each Codeword is only applicable to a CD or DVD with a specific part number.

Checking the HP-UX installation date

sábado, 4 de fevereiro de 2012

Follow some solution:

Using print_manifest:

# print_manifest | grep -i "The system was created"
Using swlist:

# swlist -l bundle -v HPUXBaseOS | grep mod_date

or

# swlist -a install_date -l product | grep -i os-core

What's the patch installation date?

There's different mothods to do that:

1 - Using swlist:

# swlist -l patch -a revision -a title -a state -a install_date

This is the date format:
200903081306.51
YYYYMMDDHHMM.SS

2 - Using "ls":

# ls -dltr /var/adm/sw/products/PH*

Check the creation date on output.

Find the list of files in a bundle

segunda-feira, 16 de janeiro de 2012

First find the bundle name

# swlist -l bundle -s /patch/11.00/depot
Then
# swlist -l file -l bundle -s /patch/11.00/depot PB_11_00_march_2003

Cleanup command

sábado, 14 de janeiro de 2012

The cleanup command can free space for you commiting patches installed, but if you commit a patch you can't more use swremove to remove it.

cleanup -c n  <--  commits patches that have been superseded n number of times.  Useful to free up disk space in /var/adm/sw/save.
cleanup -p  <-- previews the actual cleanup tasks but does not actually perform the cleanup

[swagentd] ERROR:Remote Procedure Call to a daemon has failed Could not start a management session for...

If you see this error message when you are tring remove/install a depot:

ERROR:Remote Procedure Call to a daemon has failed.  Could not start a management session for <target>.   Make sure the host is accessible from the network,  and that its daemon, swagentd, is running. If the daemon is running see the daemon logfile on this target for more information.

it means SD-UX could not contact the daemon program on a specific target system. Note that this may occur even if you haven’t specified any targets, for example, if the daemon on your local host is not running.

Resolution

If the SD-UX daemon/agent is not installed on a given target system, you must install it before you can use SD-UX.
If you’ve verified that the daemon/agent component has been installed on a target system and you still have trouble contacting it, check to see that the daemon is running:

1. On the target system, type:
   ps -e | grep swagentd
2. If the daemon does not appear to be running, you can start it by typing (as root on the target system):
   /usr/sbin/swagentd
3. If you attempt to start a daemon when one is already running, you will see a message about the other daemon; this is harmless.
   You can also kill and restart a currently running daemon by typing:
   /usr/sbin/swagentd -r

Search for a specified patch

# swlist -l product| grep PH | more


PH = replace this word for "what you are searching"

Create a depot with multiple individual depots

1 - Create all depots, use the follow command for each patch:

# sh patch

2 - Use the swcopy to create a new depot:

# for i in PH*.depot
do
        swcopy -x enforce_dependencies=false -s ${PWD}/$i \* @ /tmp/patch_depot         <-- /tmp/patch_depot this will be the destination directory of your depot
done

3 - Now you can use your new depot to install your patches:

# swinstall -s /tmp/patch_depot