Script migration help from HPUX Post: 302443945

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Script Migration From HP to Linux (KSH)

Hi All, Currently iam going to migrate some of the ksh scripts from HPUX to LINUX. Will there be any major change in scripts which I have to take care for migration? Appreciate some help on this. Thanks Om

2. UNIX for Advanced & Expert Users

script migration from HP-UX to AIX

Dear All, What points should i keep in mind while migrating scripts from HP-UX to AIX. Are there any notes available for this? cheers, vishal

3. Shell Programming and Scripting

Need Script to Use CPUs on a HPUX server to simulate Workload Manager on HPUX.

I am running HPUX and using WLM (workload manager). I want to write a script to fork CPUs to basically take CPUs from other servers to show that the communication is working and CPU licensing is working. Basically, I want to build a script that will use up CPU on a server. Any ideas?

4. Shell Programming and Scripting

Shell Script migration issues

Hi All, We will be doing a Solaris 8 to Solaris 10 migration migration, just wanted to know if there are any known / common issues arise from this migration from Shell script point of view. I tried searching this site but mostly post are related to SA's question and jumpstart, etc. If there's...

5. HP-UX

pwage-hpux-T for Trusted HPUX servers

I'm sharing this in case anybody needs it. Modified from the original solaris pwage script. This modified hpux script will check /etc/password file on hpux trusted systems search /tcb and grep the required u_succhg field. Calculate days to expiry and notify users via email. original solaris...

6. HP-UX

Hpux and bacula script

# bacula status /opt/bacula/bin/bacula-ctl-fd: UNIX95=1;: not found bacula-fd is stopped #! /bin/sh # # bacula-ctl-fd This shell script takes care of starting and stopping # the bacula File daemon. # # This is pretty much watered down version of the RedHat script # that...

7. HP-UX

Hpux pkill,a little help with script

This work #!/usr/bin/sh COMM=${1} shift UNIX95=1 ps -C ${COMM} -o pid='' | while read P do kill -15 ${P} done This don't work #!/usr/bin/sh COMM=${1} shift UNIX95=1 ps -C ${COMM} -o pid='' | while read P do kill -"$@" ${P} done

8. Shell Programming and Scripting

ksh script migration from Solaris to Linux.

We are migrating some scripts (ksh) from Solaris 10 to Linux 2.6.32. Can someone share list of changes i need to take care for this ? Have found few of them but i am looking for a exhaustive list. Thanks.

9. AIX

AIX - FC Switch migration, SAN Migration question!

I'm New to AIX / VIOS We're doing a FC switch cutover on an ibm device, connected via SAN. How do I tell if one path to my remote disk is lost? (aix lvm) How do I tell when my link is down on my HBA port? Appreciate your help, very much!

LEARN ABOUT DEBIAN

vzmigrate

vzmigrate(8)							    Containers							      vzmigrate(8)

NAME

       vzmigrate - migrate a container between two OpenVZ servers

SYNOPSIS

       vzmigrate [-r|--remove-area yes|no] [--ssh=ssh_options] [--rsync=rsync_options] [--keep-dst] [--online] [-v] destination_address CTID

DESCRIPTION

       This  utility  is  used	to  migrate  a container from one (source) Hardware Node (HN) to another (destination) HN. The utility can migrate
       either stopped or running container. For a stopped container, simple CT private area transfer is  performed  (rsync(1)  is  used  for  file
       transfer). For running containers, migration may be offline (default) or online.

       This  program uses ssh as a transport layer. You will need to put ssh public key to destination node and be able to connect to node without
       entering password.

OPTIONS

       -r, --remove-area yes | no
	      Whether to remove a container area on source HN for the successfully migrated container. Default is yes.

       --ssh=options
	      Additional options that will be passed to ssh while establishing connection to destination HN.

       --rsync=options
	      Additional options that will be passed to rsync(8).  You may add options like -z to enable data compression  if  you  are  migrating
	      over a slow link.

       --keep-dst
	      Do  not  clean  synced  destination container private area in case of some error. It makes sense to use this option on big container
	      migration to avoid syncing container private area again in case some error (on container	stop  for  example)  occurs  during  first
	      migration attempt.

       --online
	      Perform  online (zero-downtime) migration: during the migration the container hangs for a while and after the migration it continues
	      working as though nothing has happened.

       -v     Verbose mode. Causes vzmigrate to print debugging messages about its progress.  Multiple -v options  increase  the  verbosity.   The
	      maximum is 3.

EXAMPLES

       Migration of CT 101 to 192.168.1.130 with downtime:

	  vzmigrate 192.168.1.130 101

       Online migration of CT 102 to 192.168.1.130:

	  vzmigrate --online 192.168.1.130 102

EXIT STATUS

       0 EXIT_OK
	      Command completed successfully.

       1 EXIT_USAGE
	      Bad command line options.

       2 EXIT_VE_STOPPED
	      Container is stopped.

       4 EXIT_CONNECT
	      Can't connect to destination (source) HN.

       6 EXIT_COPY
	      Container private area copying/moving failed.

       7 EXIT_VE_START
	      Can't start or restore destination CT.

       8 EXIT_VE_STOP
	      Can't stop or checkpoint source CT.

       9 EXIT_EXISTS
	      Container already exists on destination HN.

       10 EXIT_NOTEXIST
	      Container does not exists on source HN.

       12 EXIT_IP_INUSE
	      You attempt to migrate CT which IP address(es) are already in use on the destination node.

       13 EXIT_QUOTA
	      Operation with CT quota failed.

SEE ALSO

       rsync(1).

COPYRIGHT

       Copyright (C) 2001-2010, Parallels, Inc. Licensed under GNU GPL.

OpenVZ								    28 Jun 2011 						      vzmigrate(8)