If I understand your question, this may help. Understand prog is the program that errors out in this example: prog 2>&1 | tee prog.err Look for all output including errors in the file prog.err which tee will have created for you and before opening prog.err try wc-l prog.err and grep -i error prog.err to do initial inspection. If the wc command returns 0 then no need to do the grep search since the file is empty.
-- Jude <jdashiel at panix dot com> "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." Ed Howdershelt 1940. On Sun, 8 Oct 2023, Dale wrote: > Howdy, > > I use Konsole a lot, that thing within KDE that acts like a console. > Anyway, I'm running a offline file system check on a rather large file > system. For some reason, Konsole decided to crash. I can see the file > system is still running with top, ps etc but I can't see anything to > know what it is doing. Is there a way to get that back? Should I kill > it and restart now that Konsole is running again? I'd think a regular > term signal would give it a safe stopping place but still kinda chicken > to do it. Then again, what if it stops and needs my input or worse yet, > it displays a error that I can't see but I need to know and see? > > Any thoughts? Is there a way to get it back? Kill it and restart? Do > nothing and hope for the best? > > Thanks. > > Dale > > :-) :-) > >
