How To Transfer Data Via Ascii Terminal Applications With Cut&Paste; Can I Run The Script Regularly From Cron - HP 9000 rp3410 Faq

MAXFILESIZE=1024 # Maximum size of some logfile in kbytes
GETFIRSTLINES=2000 # if logfiles are truncated, also the first lines are saved
MAXBACKDATE=180 # for some logfiles: get information less than 180 days old
RUNCRASHINFO=0 #1=run crashinfo on last crash
#2=run crashinfo for all crashes
SAN=0 #do not capture fcddiag by default
NET=0 #do not capture nettl and netstat logs by default
diskjn=0 #do not query all disks with diskinfo or scsimgr by default
INITDATA=0 # do not capture initdata stuff by default
PMANI=0 # do not use print_manifest by default
SASOPTION=1 # 0: run sasmgr in any case
XPINFO=0 #1: run XPINFO
NOHIST=0 #evweb -b history by default (set to 1 if it makes problems)
NMVMUNIX=0 # do not collect symbols from vmunix by default
ESCSIDIAG=0 #do not capture escsi_diag output
SWINFO=0 #higher values capture more data for SW suport
OSELOGS=1 #capturing of /var/opt/psb/oselogs
#better do not change parameters below here unless you know what you are doing
Note: when the script is modified and the CKSUM: line is not adjusted properly, a warning about the
modification will be printed and the script will pause for 15 seconds when started.
How to transfer data via ASCII terminal applications with cut&paste ?
getsysinfo.sh can be transferred via cut&paste to the target server via a terminal application (like
putty). No line is longer than 80 chars.
cat > /tmp/getsysinfo.sh
#then paste the script into your terminal application
CTRL-D
You can use the "-u" option to transfer the result back to you PC.
ksh /tmp/getsysinfo.sh -u
#now start logging to a file on your terminal application
cat /tmp/sysinfo.uu
#stop logging
You can then unpack the file on a Unix Server by deleting everything before "begin" with
uudecode logfile
and you have a gzipped tar archive that can be unpacked with WinZIP or gunzip and tar.

Can I run the script regularly from cron ?

This is not recommended.
Although the script is not known to cause problems, it was not written for collecting configuration
data but to troubleshoot hardware problems. A lot of commands are used which directly interact
with internal and external hardware, LVM and other system resources which may cause strange
logs in syslog.log or device logs if running too often.