Edit - Unix & Linux Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

The sed approach might be better because there is additional data in the log file that doesn't conform to the strings that I posted in this thread. Using "Agent Identifier" as the common criteria will probably work. I will have to test.

Heisenberg
– Heisenberg

2017-04-20 21:02:08 +00:00
Commented Apr 20, 2017 at 21:02
Thanks @RomanPerekhrest. The sed approach works like a charm. Gives me a starting point to learn text processing further. I'm looking for a good resource with examples to get better using grep/sed/awk.

Heisenberg
– Heisenberg

2017-04-21 17:31:50 +00:00
Commented Apr 21, 2017 at 17:31
@Heisenberg, you're welcome. To learn awk - find the book "GAWK: Effective AWK Programming", for other tools - official documentation is good(it's also good for awk)

RomanPerekhrest
– RomanPerekhrest

2017-04-21 19:48:01 +00:00
Commented Apr 21, 2017 at 19:48

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »