[pre]grep p2030 job_log_einstein* | cut -d\ -f11 | tail -25
^^[/pre]
But a double space is a tricky thing to post for another user to copy without warning - anybody who re-keys rather than copying (say if they're viewing on one screen, while working on a different computer) might miss it, even like this.
Gary, Richard and
)
Gary, Richard and AgentB:
Thanks for the input/guidance. Most helpful.
AgentB:
small correction to the above (unless your file structure uses a "\" as a delimeter:
grep p2030 job_log_einstein* | cut -d ' ' -f11 | tail -25
RE: RE: grep p2030
)
Ah yes i see my second space got eaten!
Oddly it disappears after posting - if you quote it - you will see in the compose window
cut-d-f11
which is another way to escape the space character as the delimiter for cut.
The message board seems to do some weird things with multiple spaces, no matter how many spaces i type it shows only one.
So i would like to type it correctly with two spaces, you will have to remove the underscore below.
grep p2030 job_log_einstein* | cut -d\ _ -f11 | tail -25
Use {pre} tags to preserve
)
Use {pre} tags to preserve white space:
[pre]grep p2030 job_log_einstein* | cut -d\ -f11 | tail -25
^^[/pre]
But a double space is a tricky thing to post for another user to copy without warning - anybody who re-keys rather than copying (say if they're viewing on one screen, while working on a different computer) might miss it, even like this.