Hpux and bacula script Post: 302804989

4 More Discussions You Might Find Interesting

1. 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?

2. Linux

Script migration help from HPUX

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

3. 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...

4. 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

LEARN ABOUT CENTOS

btraceback

BTRACEBACK(1)					     Network backup, recovery and verification					     BTRACEBACK(1)

NAME

	btraceback - wrapper script around gdb and bsmtp

SYNOPSIS

       btraceback /path/to/binary pid

DESCRIPTION

       btraceback is a wrapper shell script around the gdb debugger (or dbx on Solaris systems) and bsmtp, provided for debugging purposes.

USAGE

       btraceback  is called by the exception handlers of the Bacula daemons during a crash.  It can also be called interactively to view the cur-
       rent state of the threads belonging to a process, but this is not recommended unless you are trying to debug a problem (see below).

NOTES

       In order to work properly, debugging symbols must be available to the debugger on the system, and gdb, or dbx (on Solaris systems) must	be
       available in the $PATH.

       If  the	Director  or Storage daemon runs under a non-root uid, you will probably need to be modify the btraceback script to elevate privi-
       leges for the call to gdb/dbx, to ensure it has the proper permissions to debug when called by the daemon.

       Although Bacula's use of btraceback within its exception handlers is always safe, manual or interactive use of btraceback is subject to the
       same  risks  than  live debugging of any program, which means it could cause Bacula to crash under rare and abnormal circumstances.  Conse-
       quently we do not recommend manual use of btraceback in production environments unless it is required for debugging a problem.

ENVIRONMENT

       btracback relies on $PATH to find the debugger.

FILES

       /usr/lib/bacula/btraceback
	      The script itself.

       /usr/sbin/btraceback
	      symbolic link to /usr/lib/bacula/btraceback

       /etc/bacula/scripts/btraceback.gdb
	      the GDB command batch used to output a stack trace

AUTHOR

       This manual page was written by Lucas B. Cohen <lbc@members.fsf.org>

SEE ALSO

       bsmtp(1)

Kern Sibbald							  6 December 2009						     BTRACEBACK(1)