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? (2 Replies)
I have a process that I'd like to kill. Doing a "ps -fu myusername" gives me:
UID PID PPID C STIME TTY TIME CMD
myusername 5443 1 0 10:05 ? 00:00:00 /bin/sh /some/path/crap.sh -s /yet/another/path/parentProcess
myusername 5593 5443 0 ... (2 Replies)
Hi,
We are looking for the extensive list of Commands/Syntax that were working in HP-UX and will not work on LINUX.
We would find such commands and modify them accordingly.
Do we have any reference sites or documents.
You help would be greatly appreciated.
Thanks in advance (2 Replies)
Hi all,
I've been pulling my hair out with this problem for 3 days:wall: now without success any help would be massively appreciated.
Basically the script is used to shutdown a rails server so a new IP address can be assigned, the shutdown part is taken care of in function_one using the... (2 Replies)
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... (2 Replies)
Hi All,
I am writing a shell script to kill user processes on all servers using pkill.
But when i am passing user id directly ist works but when password userid as variable its not working & getting the below error.
# ssh hpadmin@vmtest15.zin33 'sudo /usr/bin/pkill -u $unixid'... (2 Replies)
have two scripts on Unix; one that starts some processes and the other one for killing a process. At first, I ran the .sh without WILY in it and it worked perfectly; in this way, I could also ran my stopper process. However I need WILY in this so I added it to my script but this time, a message... (1 Reply)
# 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... (9 Replies)
Discussion started by: Linusolaradm1
9 Replies
LEARN ABOUT OPENSOLARIS
hatimerun
hatimerun(1M) System Administration Commands hatimerun(1M)NAME
hatimerun - run child program under a timeout
SYNOPSIS
/usr/cluster/bin/hatimerun -t timeOutSecs [-av] [-e exitcode]
prog args
/usr/cluster/bin/hatimerun -t timeOutSecs [-v] [-e exitcode]
[-k signalname] prog args
DESCRIPTION
The hatimerun utility provides a convenient facility for timing out the execution of another child, program. It is useful when programming
in scripting languages, such as the Bourne shell. See sh(1).
The hatimerun utility runs the program prog with arguments args as a child subprocess under a timeout, and as its own process group. The
timeout is specified in seconds, by the -t timeOutSecs option. If the timeout expires, then hatimerun kills the child subprocess's process
group with a SIGKILL signal, and then exits with exit code 99.
You can run this command in the global zone or in a non-global zone. The command affects only the global or non-global zone in which you
issue the command.
OPTIONS
The following options are supported:
-a Changes the meaning of hatimerun radically: instead of killing the child when the timeout expires, the hatimerun utility sim-
ply exits, with exit code 99, leaving the child to run asynchronously.
It is illegal to supply both the -a option and the -k option.
-e Changes the exit code for the timeout case to some other value than 99.
-k Specifies what signal is used to kill the child process group. The possible signal names are the same as those recognized by
the kill(1) command. In particular, the signal name should be one of the symbolic names defined in the <signal.h> descrip-
tion. The signal name is recognized in a case-independent fashion, without the SIG prefix. It is also legal to supply a
numeric argument to the -k option, in which case that signal number is used.
It is illegal to supply both the -a option and the -k option.
-t Specifies the timeout period, in seconds.
-v Verbose output, on stderr.
EXIT STATUS
If the timeout occurs, then hatimerun exits with exit code 99 (which can be overridden to some other value using the -e option).
If the timeout does not occur but some other error is detected by the hatimerun utility (as opposed to the error being detected by the
child program), then hatimerunhatimerun exits with exit code 98.
Otherwise, hatimerun exits with the child's exit status.
The hatimerun utility catches the signal SIGTERM. It responds to the signal by killing the child as if a timeout had occurred, and then
exiting with exit code 98.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWscu |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
SEE ALSO kill(1), sh(1), attributes(5)Sun Cluster 3.2 10 Apr 2006 hatimerun(1M)