#better do not change parameters below here unless you know what you are doing
#Integrity check
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 check if I have the official getsysinfo.sh script or a modified ?
Simply run “cksum getsysinfo.sh” and verify with the below values.
The cksum outputs of getsysinfo.sh version 9.23 official revisions are:
2176148563 54116 getsysinfo.sh
3089166024 230078 getsysinfo.all.sh
164757447 88606 getsysinfo.sd2.sh
4145209390 170673 getsysinfo.mp.sh
351488249 205162 getsysinfo.ms.sh
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.
Comentarios a estos manuales