Ummm..<br><br>How about <br><br>grep synaptic ~/.xsession-errors<br><br>or (to get preceding and following lines)<br><br>grep -n -A5 -B5 synaptic ~/.xsession-errors<br><br>...<br><br>the cat is redundant. I do, however, love cats. :)<br>
<br><div class="gmail_quote">On Wed, Nov 18, 2009 at 9:23 PM, Charles W Downing <span dir="ltr"><<a href="mailto:chuckdowning@earthlink.net">chuckdowning@earthlink.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im"><br>
<br>
Jed S. Baer wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Wed, 18 Nov 2009 17:50:28 -0700<br>
WILLIAM PATTERSON+I*I SMITH wrote:<br>
<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
[bill@localhost ~]$ tail -f --lines=20 ~/.xsession-errors<br>
<br>
</blockquote>
<br>
The point of this exercise is to locate the error message relating to<br>
synaptic not starting. That error message should contain the string<br>
'synaptic'.<br>
<br>
<br>
</blockquote></div>
What would wrong with:<br>
<br>
cat -n .xsession-errors | grep synaptic<br>
<br>
The -n would number the lines from .xsession-errors. By "grepping" for synaptic, at least William would get to the ballpark of the lines we are looking for.<br><font color="#888888">
<br>
-- <br>
Chuck Downing<br>
Highlands Ranch, Colorado USA <br></font><div><div></div><div class="h5">
_______________________________________________<br>
clue-tech mailing list<br>
<a href="mailto:clue-tech@cluedenver.org" target="_blank">clue-tech@cluedenver.org</a><br>
<a href="http://www.cluedenver.org/mailman/listinfo/clue-tech" target="_blank">http://www.cluedenver.org/mailman/listinfo/clue-tech</a><br>
</div></div></blockquote></div><br>