Unix tip: Monitor disk arrays with sccli commands
Disk arrays take a lot of worry about disk failure off your shoulders, but that's no reason not to notice when one goes bad. The sccli command can tell you a lot about what's happening with your StorEdge arrays. Let it warn you about disks gone bad.
View full article »
Esther Schindler
If the comments are ugly, the code is ugly
claird
SVG a graphics format for 21st century
pasmith
Take Chrome OS for a test spin
Sandra Henry-Stocker
Solaris Tip: Have Your Files Changed Since Installation?
jfruh
Android fragments vs. the iPhone monolith
mikelgan
What Gizmodo missed about the Pro WX Wireless USB disk drive
Sidekick: The Good News & the Bad News
Either way you look at it Microsoft Data Center management did not follow standards or best practices in this failure. In which case it makes me wonder more about the outsourcing of corporate data much less personal data.
- mburton325
Join the conversation here
Quick, practical advice for IT pros. Made fresh daily.
Want to cash in on your IT savvy? Send your tip to tips@itworld.com. If we post it, we'll send you a $25 Amazon e-gift card.
Bug?
It would seem that you have a bug in your script:sccli < /tmp/$$
show disks
show ld
exit
EOF
I suppose that "/tmp/$$" should contain
show disks
show ld
exit
Otherwise, the script will fail because "/tmp/$$" doesn't exist beforehand.
May I also suggest to refrain from using bash? bash is full of bugs and usually not found on traditional UNIX systems, making it a poor choice for scripts (programs) which are meant to be, or should be portable across systems. /bin/ksh is likely to be a good choice between usability and portability.
Also, may I suggest you trap SIGINT, so that if your script is ever ^Ced during execution/debugging, the self-defined Cleanup() function will clean up "/tmp/$$" automatically.
EXAMPLE
#!/sbin/sh
Rm="/bin/rm"
Self="`basename $0`"
TmpDir="/tmp"
TmpFile0="$TmpDir/${Self}.$$"
trap Cleanup 2
Cleanup()
{
$Rm -f "$TmpFile0"
}