Script migration help from HPUX Post: 302444093

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 HPUX

symlink

symlink(4)						     Kernel Interfaces Manual							symlink(4)

NAME

       symlink - symbolic link

DESCRIPTION

       A symbolic (or soft ) link is a file whose name indirectly refers (points) to a relative or absolute path name.

       During  path  name  interpretation,  a symbolic link to a relative path name is expanded to the path name being interpreted, and a symbolic
       link to an absolute path name is replaced with the path name being interpreted.

       Thus, given the path name

	      If is a symbolic link to a relative path name such as the path name is interpreted as

	      If is a symbolic link to an absolute path name such as the path name is interpreted as

       All symbolic links are interpreted in this manner, with one exception: when the symbolic link is the last component of a path name,  it	is
       passed  as  a  parameter  to  one of the system calls: or (see readlink(2), rename(2), symlink(2), unlink(2), chown(2) and lstat(2)).  With
       these calls, the symbolic link, itself, is accessed or affected.

       Unlike normal (hard) links, a symbolic link can refer to any arbitrary path name and can span different logical devices (volumes).

       The path name can be that of any type of file (including a directory or another symbolic link), and may be invalid if no such  path  exists
       in  the	system.   (It is possible to make symbolic links point to themselves or other symbolic links in such a way that they form a closed
       loop.  The system detects this situation by limiting the number of symbolic links it traverses while translating a path name.)

       The mode and ownership of a symbolic link is ignored by the system, which means that affects the actual file, but not the  file	containing
       the symbolic link (see chmod(1)).

       Symbolic links can be created using or (see ln(1) and symlink(2)).

AUTHOR

       was developed by HP and the University of California, Berkeley.

SEE ALSO

       cp(1), symlink(2), readlink(2), link(2), stat(2), mknod(1M).

																	symlink(4)