On Wednesday December 29 2010, Patrick Shanahan wrote:
* Randall R Schulz
[12-29-10 14:31]: Try launching an interactive shell (in misbehaving mode) with the "-x" option. You can see exactly what it's executing right up to (and possibly beyond) the "have" diagnostic.
Aha, I see a lot and have appears quite frequently. But there are 4500+ lines of output :^(, how do I caputre them all? bash -x >> bash.log bash -x | tee > bash.log bash -x | tee -ia > bash.log do not work....
tks,
Yeah, it's voluminous. Shows you how much is really going on in the shell! If you expressly invoke it as an interactive shell and redirect standard error, you can capture the execution trace: outer-shell-prompt> bash -i 2>/tmp/bash-start-log exit outer-shell-prompt> (Note that the sub-shell, while interactive, will show no prompt 'cause it uses the same stream as the error stream to print prompts.) You can optionally include --login along with -i. The distinction between the two may actually tell you something about what's going wrong. For whatever reason, if you give both --login and -i, they have to be in that order.
-- Patrick Shanahan
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org