[NCLUG] Shell script

Alan Silverstein ajs at frii.com
Thu Feb 20 17:39:57 MST 2014


> Or git gist, or pastebin

Or if it's just plain old text, skip attaching it and just read a copy
of the script into your email at the end.  (Assuming you use a text
editor and not some WYSWYG mouse-based email client of course.  :-)

But like someone said but I'll reword, any solid troubleshooting begins
with focusing specifically on the first anomaly (symptom of failure).

Anyway without knowing anything more, is it possible that you overloaded
the system somehow with too many umount processes at once, or failed to
check return codes and/or stdout+stderr for anomalies?  For example one
common umount complaint is that the file system is in use.  Don't know
if it's still true in Linux today, I'm an old dog, but certainly if you
are, say, cd'd to a directory in the tree, it's busy.

Cheers,
Alan Silverstein


More information about the NCLUG mailing list