Return only the portion of a line after a matching patternGrep specific data from stringReturning only the portion of a line after a matching patternReplacing XML entity values with positive lookaroundReturning a portion of a line matching a patternPrint youtube video id to file from mpv stdouthow can I merge two txt files by one similar stringReturning only the portion of a line after a matching pattern (Unix)Match from current line until a line that doesn't match a patternsed match pattern and act on x lines afterPrint some lines before and after pattern match excluding lines matching another patternsPrint only the Nth line before each line that matches a patternawk to cut portion of a field and still print entire lineHow to match a pattern in lines before another pattern matchPrint match and line afterDelete n lines after pattern and m lines before patternHow to edit the entire file after match a grep pattern?

How old can references or sources in a thesis be?

How do I deal with an unproductive colleague in a small company?

Languages that we cannot (dis)prove to be Context-Free

Can an x86 CPU running in real mode be considered to be basically an 8086 CPU?

Add text to same line using sed

Approximately how much travel time was saved by the opening of the Suez Canal in 1869?

Alternative to sending password over mail?

What does the "remote control" for a QF-4 look like?

Has there ever been an airliner design involving reducing generator load by installing solar panels?

Was any UN Security Council vote triple-vetoed?

Why can't I see bouncing of switch on oscilloscope screen?

Is it inappropriate for a student to attend their mentor's dissertation defense?

What are these boxed doors outside store fronts in New York?

Did Shadowfax go to Valinor?

Are the number of citations and number of published articles the most important criteria for a tenure promotion?

Is it legal for company to use my work email to pretend I still work there?

Can a Cauchy sequence converge for one metric while not converging for another?

Do I have a twin with permutated remainders?

How does quantile regression compare to logistic regression with the variable split at the quantile?

What doth I be?

Theorems that impeded progress

Is it unprofessional to ask if a job posting on GlassDoor is real?

DC-DC converter from low voltage at high current, to high voltage at low current

Client team has low performances and low technical skills: we always fix their work and now they stop collaborate with us. How to solve?



Return only the portion of a line after a matching pattern


Grep specific data from stringReturning only the portion of a line after a matching patternReplacing XML entity values with positive lookaroundReturning a portion of a line matching a patternPrint youtube video id to file from mpv stdouthow can I merge two txt files by one similar stringReturning only the portion of a line after a matching pattern (Unix)Match from current line until a line that doesn't match a patternsed match pattern and act on x lines afterPrint some lines before and after pattern match excluding lines matching another patternsPrint only the Nth line before each line that matches a patternawk to cut portion of a field and still print entire lineHow to match a pattern in lines before another pattern matchPrint match and line afterDelete n lines after pattern and m lines before patternHow to edit the entire file after match a grep pattern?






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








97















So pulling open a file with cat and then using grep to get matching lines only gets me so far when I am working with the particular log set that I am dealing with. It need a way to match lines to a pattern, but only to return the portion of the line after the match. The portion before and after the match will consistently vary. I have played with using sed or awk, but have not been able to figure out how to filter the line to either delete the part before the match, or just return the part after the match, either will work.
This is an example of a line that I need to filter:



2011-11-07T05:37:43-08:00 <0.4> isi-udb5-ash4-1(id1) /boot/kernel.amd64/kernel: [gmp_info.c:1758](pid 40370="kt: gmp-drive-updat")(tid=100872) new group: <15,1773>: 1:0-25,27-34,37-38, 2:0-33,35-36, 3:0-35, 4:0-9,11-14,16-32,34-38, 5:0-35, 6:0-15,17-36, 7:0-16,18-36, 8:0-14,16-32,34-36, 9:0-10,12-36, 10-11:0-35, 12:0-5,7-30,32-35, 13-19:0-35, 20:0,2-35, down: 8:15, soft_failed: 1:27, 8:15, stalled: 12:6,31, 20:1 


The portion I need is everything after "stalled".



The background behind this is that I can find out how often something stalls:



cat messages | grep stalled | wc -l


What I need to do is find out how many times a certain node has stalled (indicated by the portion before each colon after "stalled". If I just grep for that (ie 20:) it may return lines that have soft fails, but no stalls, which doesn't help me. I need to filter only the stalled portion so I can then grep for a specific node out of those that have stalled.



For all intents and purposes, this is a freebsd system with standard GNU core utils, but I cannot install anything extra to assist.










share|improve this question
























  • @Gilles, Odd how that didn't pop up when I searched, though I didn't use the title I eventually went with...but it didn't show up in the screen below my title. Anyway, that aside, that might get me where I want, though I need the entire line after the match, not the first word - but might not take much of a change.

    – MaQleod
    Nov 7 '11 at 23:52












  • Its title sucked. I stole yours which is very nice. Take the sed solution and don't treat whitespace specially.

    – Gilles
    Nov 7 '11 at 23:55











  • @Gilles, that is something I'm not entirely sure how to do. I am still learning sed.

    – MaQleod
    Nov 8 '11 at 0:06











  • similar to unix.stackexchange.com/questions/24089/… as well.

    – Tim Kennedy
    Nov 8 '11 at 0:43






  • 1





    @shaa0601 I don't understand your question, it's especially difficult to follow in a comment with no formatting. Ask a new, self-contained question.

    – Gilles
    Aug 28 '14 at 15:37

















97















So pulling open a file with cat and then using grep to get matching lines only gets me so far when I am working with the particular log set that I am dealing with. It need a way to match lines to a pattern, but only to return the portion of the line after the match. The portion before and after the match will consistently vary. I have played with using sed or awk, but have not been able to figure out how to filter the line to either delete the part before the match, or just return the part after the match, either will work.
This is an example of a line that I need to filter:



2011-11-07T05:37:43-08:00 <0.4> isi-udb5-ash4-1(id1) /boot/kernel.amd64/kernel: [gmp_info.c:1758](pid 40370="kt: gmp-drive-updat")(tid=100872) new group: <15,1773>: 1:0-25,27-34,37-38, 2:0-33,35-36, 3:0-35, 4:0-9,11-14,16-32,34-38, 5:0-35, 6:0-15,17-36, 7:0-16,18-36, 8:0-14,16-32,34-36, 9:0-10,12-36, 10-11:0-35, 12:0-5,7-30,32-35, 13-19:0-35, 20:0,2-35, down: 8:15, soft_failed: 1:27, 8:15, stalled: 12:6,31, 20:1 


The portion I need is everything after "stalled".



The background behind this is that I can find out how often something stalls:



cat messages | grep stalled | wc -l


What I need to do is find out how many times a certain node has stalled (indicated by the portion before each colon after "stalled". If I just grep for that (ie 20:) it may return lines that have soft fails, but no stalls, which doesn't help me. I need to filter only the stalled portion so I can then grep for a specific node out of those that have stalled.



For all intents and purposes, this is a freebsd system with standard GNU core utils, but I cannot install anything extra to assist.










share|improve this question
























  • @Gilles, Odd how that didn't pop up when I searched, though I didn't use the title I eventually went with...but it didn't show up in the screen below my title. Anyway, that aside, that might get me where I want, though I need the entire line after the match, not the first word - but might not take much of a change.

    – MaQleod
    Nov 7 '11 at 23:52












  • Its title sucked. I stole yours which is very nice. Take the sed solution and don't treat whitespace specially.

    – Gilles
    Nov 7 '11 at 23:55











  • @Gilles, that is something I'm not entirely sure how to do. I am still learning sed.

    – MaQleod
    Nov 8 '11 at 0:06











  • similar to unix.stackexchange.com/questions/24089/… as well.

    – Tim Kennedy
    Nov 8 '11 at 0:43






  • 1





    @shaa0601 I don't understand your question, it's especially difficult to follow in a comment with no formatting. Ask a new, self-contained question.

    – Gilles
    Aug 28 '14 at 15:37













97












97








97


37






So pulling open a file with cat and then using grep to get matching lines only gets me so far when I am working with the particular log set that I am dealing with. It need a way to match lines to a pattern, but only to return the portion of the line after the match. The portion before and after the match will consistently vary. I have played with using sed or awk, but have not been able to figure out how to filter the line to either delete the part before the match, or just return the part after the match, either will work.
This is an example of a line that I need to filter:



2011-11-07T05:37:43-08:00 <0.4> isi-udb5-ash4-1(id1) /boot/kernel.amd64/kernel: [gmp_info.c:1758](pid 40370="kt: gmp-drive-updat")(tid=100872) new group: <15,1773>: 1:0-25,27-34,37-38, 2:0-33,35-36, 3:0-35, 4:0-9,11-14,16-32,34-38, 5:0-35, 6:0-15,17-36, 7:0-16,18-36, 8:0-14,16-32,34-36, 9:0-10,12-36, 10-11:0-35, 12:0-5,7-30,32-35, 13-19:0-35, 20:0,2-35, down: 8:15, soft_failed: 1:27, 8:15, stalled: 12:6,31, 20:1 


The portion I need is everything after "stalled".



The background behind this is that I can find out how often something stalls:



cat messages | grep stalled | wc -l


What I need to do is find out how many times a certain node has stalled (indicated by the portion before each colon after "stalled". If I just grep for that (ie 20:) it may return lines that have soft fails, but no stalls, which doesn't help me. I need to filter only the stalled portion so I can then grep for a specific node out of those that have stalled.



For all intents and purposes, this is a freebsd system with standard GNU core utils, but I cannot install anything extra to assist.










share|improve this question
















So pulling open a file with cat and then using grep to get matching lines only gets me so far when I am working with the particular log set that I am dealing with. It need a way to match lines to a pattern, but only to return the portion of the line after the match. The portion before and after the match will consistently vary. I have played with using sed or awk, but have not been able to figure out how to filter the line to either delete the part before the match, or just return the part after the match, either will work.
This is an example of a line that I need to filter:



2011-11-07T05:37:43-08:00 <0.4> isi-udb5-ash4-1(id1) /boot/kernel.amd64/kernel: [gmp_info.c:1758](pid 40370="kt: gmp-drive-updat")(tid=100872) new group: <15,1773>: 1:0-25,27-34,37-38, 2:0-33,35-36, 3:0-35, 4:0-9,11-14,16-32,34-38, 5:0-35, 6:0-15,17-36, 7:0-16,18-36, 8:0-14,16-32,34-36, 9:0-10,12-36, 10-11:0-35, 12:0-5,7-30,32-35, 13-19:0-35, 20:0,2-35, down: 8:15, soft_failed: 1:27, 8:15, stalled: 12:6,31, 20:1 


The portion I need is everything after "stalled".



The background behind this is that I can find out how often something stalls:



cat messages | grep stalled | wc -l


What I need to do is find out how many times a certain node has stalled (indicated by the portion before each colon after "stalled". If I just grep for that (ie 20:) it may return lines that have soft fails, but no stalls, which doesn't help me. I need to filter only the stalled portion so I can then grep for a specific node out of those that have stalled.



For all intents and purposes, this is a freebsd system with standard GNU core utils, but I cannot install anything extra to assist.







text-processing sed grep






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 13 '15 at 15:21









Beryllium

1034




1034










asked Nov 7 '11 at 23:18









MaQleodMaQleod

1,00931318




1,00931318












  • @Gilles, Odd how that didn't pop up when I searched, though I didn't use the title I eventually went with...but it didn't show up in the screen below my title. Anyway, that aside, that might get me where I want, though I need the entire line after the match, not the first word - but might not take much of a change.

    – MaQleod
    Nov 7 '11 at 23:52












  • Its title sucked. I stole yours which is very nice. Take the sed solution and don't treat whitespace specially.

    – Gilles
    Nov 7 '11 at 23:55











  • @Gilles, that is something I'm not entirely sure how to do. I am still learning sed.

    – MaQleod
    Nov 8 '11 at 0:06











  • similar to unix.stackexchange.com/questions/24089/… as well.

    – Tim Kennedy
    Nov 8 '11 at 0:43






  • 1





    @shaa0601 I don't understand your question, it's especially difficult to follow in a comment with no formatting. Ask a new, self-contained question.

    – Gilles
    Aug 28 '14 at 15:37

















  • @Gilles, Odd how that didn't pop up when I searched, though I didn't use the title I eventually went with...but it didn't show up in the screen below my title. Anyway, that aside, that might get me where I want, though I need the entire line after the match, not the first word - but might not take much of a change.

    – MaQleod
    Nov 7 '11 at 23:52












  • Its title sucked. I stole yours which is very nice. Take the sed solution and don't treat whitespace specially.

    – Gilles
    Nov 7 '11 at 23:55











  • @Gilles, that is something I'm not entirely sure how to do. I am still learning sed.

    – MaQleod
    Nov 8 '11 at 0:06











  • similar to unix.stackexchange.com/questions/24089/… as well.

    – Tim Kennedy
    Nov 8 '11 at 0:43






  • 1





    @shaa0601 I don't understand your question, it's especially difficult to follow in a comment with no formatting. Ask a new, self-contained question.

    – Gilles
    Aug 28 '14 at 15:37
















@Gilles, Odd how that didn't pop up when I searched, though I didn't use the title I eventually went with...but it didn't show up in the screen below my title. Anyway, that aside, that might get me where I want, though I need the entire line after the match, not the first word - but might not take much of a change.

– MaQleod
Nov 7 '11 at 23:52






@Gilles, Odd how that didn't pop up when I searched, though I didn't use the title I eventually went with...but it didn't show up in the screen below my title. Anyway, that aside, that might get me where I want, though I need the entire line after the match, not the first word - but might not take much of a change.

– MaQleod
Nov 7 '11 at 23:52














Its title sucked. I stole yours which is very nice. Take the sed solution and don't treat whitespace specially.

– Gilles
Nov 7 '11 at 23:55





Its title sucked. I stole yours which is very nice. Take the sed solution and don't treat whitespace specially.

– Gilles
Nov 7 '11 at 23:55













@Gilles, that is something I'm not entirely sure how to do. I am still learning sed.

– MaQleod
Nov 8 '11 at 0:06





@Gilles, that is something I'm not entirely sure how to do. I am still learning sed.

– MaQleod
Nov 8 '11 at 0:06













similar to unix.stackexchange.com/questions/24089/… as well.

– Tim Kennedy
Nov 8 '11 at 0:43





similar to unix.stackexchange.com/questions/24089/… as well.

– Tim Kennedy
Nov 8 '11 at 0:43




1




1





@shaa0601 I don't understand your question, it's especially difficult to follow in a comment with no formatting. Ask a new, self-contained question.

– Gilles
Aug 28 '14 at 15:37





@shaa0601 I don't understand your question, it's especially difficult to follow in a comment with no formatting. Ask a new, self-contained question.

– Gilles
Aug 28 '14 at 15:37










4 Answers
4






active

oldest

votes


















123














The canonical tool for that would be sed.



sed -n -e 's/^.*stalled: //p'


Detailed explanation:




  • -n means not to print anything by default.


  • -e is followed by a sed command.


  • s is the pattern replacement command.

  • The regular expression ^.*stalled: matches the pattern you're looking for, plus any preceding text (.* meaning any text, with an initial ^ to say that the match begins at the beginning of the line). Note that if stalled: occurs several times on the line, this will match the last occurrence.

  • The match, i.e. everything on the line up to stalled:, is replaced by the empty string (i.e. deleted).

  • The final p means to print the transformed line.

If you want to retain the matching portion, use a backreference: 1 in the replacement part designates what is inside a group (…) in the pattern. Here, you could write stalled: again in the replacement part; this feature is useful when the pattern you're looking for is more general than a simple string.



sed -n -e 's/^.*(stalled: )/1/p'


Sometimes you'll want to remove the portion of the line after the match. You can include it in the match by including .*$ at the end of the pattern (any text .* followed by the end of the line $). Unless you put that part in a group that you reference in the replacement text, the end of the line will not be in the output.



As a further illustration of groups and backreferences, this command swaps the part before the match and the part after the match.



sed -n -e 's/^(.*)(stalled: )(.*)$/321/p'





share|improve this answer























  • I've tried the first two examples and it just seems to hang. I don't get an error message, nor do I get a new prompt, just nothing.

    – MaQleod
    Nov 8 '11 at 1:00






  • 2





    @MaQleod Oh, it's waiting for input on standard input, which here is the terminal because you haven't redirected it. Here you'd do an input redirection sed … <messages, since you want to process data from a file. To act on data produced by another command, you'd use a pipe: somecommand | sed ….

    – Gilles
    Nov 8 '11 at 1:02






  • 1





    right, end of day blackout there. command works perfectly, thanks.

    – MaQleod
    Nov 8 '11 at 16:37











  • Best sed explanation I've seen so far -- thanks!

    – Jon Wadsworth
    Sep 16 '16 at 17:47






  • 1





    @ungalcrys Shorter version of what? This isn't equivalent to any of the commands in my answer. I'd recommend writing it as sed 's/^.*stalled//' since -r is specific to Linux and doesn't work on other systems such as macOS and here you aren't getting any benefit from it.

    – Gilles
    Aug 9 '17 at 10:19



















67














The other canonical tool you already use: grep:



For example:



grep -o 'stalled.*'


Has the same result as the second option of Gilles:



sed -n -e 's/^.*(stalled: )/1/p'


The -o flag returns the --only-matching part of the expression, so not the entire line which is - of course - normally done by grep.



To remove the "stalled :" from the output, we can use a third canonical tool, cut:



grep -o 'stalled.*' | cut -f2- -d:


The cut command uses delimiter : and prints field 2 till the end. It's a matter of preference of course, but the cut syntax I find very easy to remember.






share|improve this answer




















  • 1





    Thanks for mentioning the -o option! I wanted to point out that grep doesn't recognize the n as a newline, so your first example only matches to the first n character. For example, echo "Hello Anne" | grep -o 'A[^n]*' returns the string A. However, echo "Hello Anne" | grep -o 'A.*' returns the expected Anne, since . matches any character except the newline.

    – adamlamar
    Mar 16 '15 at 21:52






  • 1





    Note that the quotes around the cut delimiter -d':' are removed by @poige. I find it easier to remember with quotes, e.g. with -d' ' or -d';'.

    – Anne van Rossum
    Jul 10 '17 at 20:44











  • According to your finding it should be easier to remember to use quotes with -f 2 too. Seriously, why not?

    – poige
    Aug 26 '17 at 10:26











  • Because a delimiter like a semi-colon ; rather than a colon : will be interpreted differently if not quoted. Of course that's logical behavior, but still I like to rely on muscle memory. I don't like to quote the delimiter one time but not the other time. Just personal preference, like I said before: easier to remember.

    – Anne van Rossum
    Oct 7 '17 at 18:09











  • the period that is part of the .* is needed, worked well for me: cat filename | grep 'Return only this line xyz text' | grep -o 'xyz.*' returns xyz text

    – ron
    Dec 12 '17 at 19:01



















4














I used ifconfig | grep eth0 | cut -f3- -d: to take this



 [root@MyPC ~]# ifconfig
eth0 Link encap:Ethernet HWaddr AC:B4:CA:DD:E6:F8
inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:78998810244 errors:1 dropped:0 overruns:0 frame:1
TX packets:20113430261 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:110947036025418 (100.9 TiB) TX bytes:15010653222322 (13.6 TiB)


and make it look like this



 [root@MyPC ~]# ifconfig | grep eth0 | cut -f3- -d:
C4:7A:4D:F6:B8





share|improve this answer




















  • 1





    Does this answer the question?

    – Stephen Rauch
    Mar 31 '17 at 4:56






  • 1





    You can use cat /sys/class/net/*/address, no parsing required.

    – Anne van Rossum
    Dec 13 '17 at 16:58


















1














Yet another canonical tool you considered awk could be used with the following line:



awk -F"stalled" '/stalled/print $2' messages


Detailed explanation:




  • -F defines a separator for the line, i.e., "stalled". Everything before the separator is addressed with $1 and everything after with $2.


  • /reg-ex/ Searches for the matching regular expression, in this case "stalled".


  • print $<n> - prints n column. Since your separator is defined as stalled, everything after stalled is considered to be the second column.





share|improve this answer










New contributor




robertm.tum is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















    Your Answer








    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f24140%2freturn-only-the-portion-of-a-line-after-a-matching-pattern%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    4 Answers
    4






    active

    oldest

    votes








    4 Answers
    4






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    123














    The canonical tool for that would be sed.



    sed -n -e 's/^.*stalled: //p'


    Detailed explanation:




    • -n means not to print anything by default.


    • -e is followed by a sed command.


    • s is the pattern replacement command.

    • The regular expression ^.*stalled: matches the pattern you're looking for, plus any preceding text (.* meaning any text, with an initial ^ to say that the match begins at the beginning of the line). Note that if stalled: occurs several times on the line, this will match the last occurrence.

    • The match, i.e. everything on the line up to stalled:, is replaced by the empty string (i.e. deleted).

    • The final p means to print the transformed line.

    If you want to retain the matching portion, use a backreference: 1 in the replacement part designates what is inside a group (…) in the pattern. Here, you could write stalled: again in the replacement part; this feature is useful when the pattern you're looking for is more general than a simple string.



    sed -n -e 's/^.*(stalled: )/1/p'


    Sometimes you'll want to remove the portion of the line after the match. You can include it in the match by including .*$ at the end of the pattern (any text .* followed by the end of the line $). Unless you put that part in a group that you reference in the replacement text, the end of the line will not be in the output.



    As a further illustration of groups and backreferences, this command swaps the part before the match and the part after the match.



    sed -n -e 's/^(.*)(stalled: )(.*)$/321/p'





    share|improve this answer























    • I've tried the first two examples and it just seems to hang. I don't get an error message, nor do I get a new prompt, just nothing.

      – MaQleod
      Nov 8 '11 at 1:00






    • 2





      @MaQleod Oh, it's waiting for input on standard input, which here is the terminal because you haven't redirected it. Here you'd do an input redirection sed … <messages, since you want to process data from a file. To act on data produced by another command, you'd use a pipe: somecommand | sed ….

      – Gilles
      Nov 8 '11 at 1:02






    • 1





      right, end of day blackout there. command works perfectly, thanks.

      – MaQleod
      Nov 8 '11 at 16:37











    • Best sed explanation I've seen so far -- thanks!

      – Jon Wadsworth
      Sep 16 '16 at 17:47






    • 1





      @ungalcrys Shorter version of what? This isn't equivalent to any of the commands in my answer. I'd recommend writing it as sed 's/^.*stalled//' since -r is specific to Linux and doesn't work on other systems such as macOS and here you aren't getting any benefit from it.

      – Gilles
      Aug 9 '17 at 10:19
















    123














    The canonical tool for that would be sed.



    sed -n -e 's/^.*stalled: //p'


    Detailed explanation:




    • -n means not to print anything by default.


    • -e is followed by a sed command.


    • s is the pattern replacement command.

    • The regular expression ^.*stalled: matches the pattern you're looking for, plus any preceding text (.* meaning any text, with an initial ^ to say that the match begins at the beginning of the line). Note that if stalled: occurs several times on the line, this will match the last occurrence.

    • The match, i.e. everything on the line up to stalled:, is replaced by the empty string (i.e. deleted).

    • The final p means to print the transformed line.

    If you want to retain the matching portion, use a backreference: 1 in the replacement part designates what is inside a group (…) in the pattern. Here, you could write stalled: again in the replacement part; this feature is useful when the pattern you're looking for is more general than a simple string.



    sed -n -e 's/^.*(stalled: )/1/p'


    Sometimes you'll want to remove the portion of the line after the match. You can include it in the match by including .*$ at the end of the pattern (any text .* followed by the end of the line $). Unless you put that part in a group that you reference in the replacement text, the end of the line will not be in the output.



    As a further illustration of groups and backreferences, this command swaps the part before the match and the part after the match.



    sed -n -e 's/^(.*)(stalled: )(.*)$/321/p'





    share|improve this answer























    • I've tried the first two examples and it just seems to hang. I don't get an error message, nor do I get a new prompt, just nothing.

      – MaQleod
      Nov 8 '11 at 1:00






    • 2





      @MaQleod Oh, it's waiting for input on standard input, which here is the terminal because you haven't redirected it. Here you'd do an input redirection sed … <messages, since you want to process data from a file. To act on data produced by another command, you'd use a pipe: somecommand | sed ….

      – Gilles
      Nov 8 '11 at 1:02






    • 1





      right, end of day blackout there. command works perfectly, thanks.

      – MaQleod
      Nov 8 '11 at 16:37











    • Best sed explanation I've seen so far -- thanks!

      – Jon Wadsworth
      Sep 16 '16 at 17:47






    • 1





      @ungalcrys Shorter version of what? This isn't equivalent to any of the commands in my answer. I'd recommend writing it as sed 's/^.*stalled//' since -r is specific to Linux and doesn't work on other systems such as macOS and here you aren't getting any benefit from it.

      – Gilles
      Aug 9 '17 at 10:19














    123












    123








    123







    The canonical tool for that would be sed.



    sed -n -e 's/^.*stalled: //p'


    Detailed explanation:




    • -n means not to print anything by default.


    • -e is followed by a sed command.


    • s is the pattern replacement command.

    • The regular expression ^.*stalled: matches the pattern you're looking for, plus any preceding text (.* meaning any text, with an initial ^ to say that the match begins at the beginning of the line). Note that if stalled: occurs several times on the line, this will match the last occurrence.

    • The match, i.e. everything on the line up to stalled:, is replaced by the empty string (i.e. deleted).

    • The final p means to print the transformed line.

    If you want to retain the matching portion, use a backreference: 1 in the replacement part designates what is inside a group (…) in the pattern. Here, you could write stalled: again in the replacement part; this feature is useful when the pattern you're looking for is more general than a simple string.



    sed -n -e 's/^.*(stalled: )/1/p'


    Sometimes you'll want to remove the portion of the line after the match. You can include it in the match by including .*$ at the end of the pattern (any text .* followed by the end of the line $). Unless you put that part in a group that you reference in the replacement text, the end of the line will not be in the output.



    As a further illustration of groups and backreferences, this command swaps the part before the match and the part after the match.



    sed -n -e 's/^(.*)(stalled: )(.*)$/321/p'





    share|improve this answer













    The canonical tool for that would be sed.



    sed -n -e 's/^.*stalled: //p'


    Detailed explanation:




    • -n means not to print anything by default.


    • -e is followed by a sed command.


    • s is the pattern replacement command.

    • The regular expression ^.*stalled: matches the pattern you're looking for, plus any preceding text (.* meaning any text, with an initial ^ to say that the match begins at the beginning of the line). Note that if stalled: occurs several times on the line, this will match the last occurrence.

    • The match, i.e. everything on the line up to stalled:, is replaced by the empty string (i.e. deleted).

    • The final p means to print the transformed line.

    If you want to retain the matching portion, use a backreference: 1 in the replacement part designates what is inside a group (…) in the pattern. Here, you could write stalled: again in the replacement part; this feature is useful when the pattern you're looking for is more general than a simple string.



    sed -n -e 's/^.*(stalled: )/1/p'


    Sometimes you'll want to remove the portion of the line after the match. You can include it in the match by including .*$ at the end of the pattern (any text .* followed by the end of the line $). Unless you put that part in a group that you reference in the replacement text, the end of the line will not be in the output.



    As a further illustration of groups and backreferences, this command swaps the part before the match and the part after the match.



    sed -n -e 's/^(.*)(stalled: )(.*)$/321/p'






    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Nov 8 '11 at 0:22









    GillesGilles

    546k12911101624




    546k12911101624












    • I've tried the first two examples and it just seems to hang. I don't get an error message, nor do I get a new prompt, just nothing.

      – MaQleod
      Nov 8 '11 at 1:00






    • 2





      @MaQleod Oh, it's waiting for input on standard input, which here is the terminal because you haven't redirected it. Here you'd do an input redirection sed … <messages, since you want to process data from a file. To act on data produced by another command, you'd use a pipe: somecommand | sed ….

      – Gilles
      Nov 8 '11 at 1:02






    • 1





      right, end of day blackout there. command works perfectly, thanks.

      – MaQleod
      Nov 8 '11 at 16:37











    • Best sed explanation I've seen so far -- thanks!

      – Jon Wadsworth
      Sep 16 '16 at 17:47






    • 1





      @ungalcrys Shorter version of what? This isn't equivalent to any of the commands in my answer. I'd recommend writing it as sed 's/^.*stalled//' since -r is specific to Linux and doesn't work on other systems such as macOS and here you aren't getting any benefit from it.

      – Gilles
      Aug 9 '17 at 10:19


















    • I've tried the first two examples and it just seems to hang. I don't get an error message, nor do I get a new prompt, just nothing.

      – MaQleod
      Nov 8 '11 at 1:00






    • 2





      @MaQleod Oh, it's waiting for input on standard input, which here is the terminal because you haven't redirected it. Here you'd do an input redirection sed … <messages, since you want to process data from a file. To act on data produced by another command, you'd use a pipe: somecommand | sed ….

      – Gilles
      Nov 8 '11 at 1:02






    • 1





      right, end of day blackout there. command works perfectly, thanks.

      – MaQleod
      Nov 8 '11 at 16:37











    • Best sed explanation I've seen so far -- thanks!

      – Jon Wadsworth
      Sep 16 '16 at 17:47






    • 1





      @ungalcrys Shorter version of what? This isn't equivalent to any of the commands in my answer. I'd recommend writing it as sed 's/^.*stalled//' since -r is specific to Linux and doesn't work on other systems such as macOS and here you aren't getting any benefit from it.

      – Gilles
      Aug 9 '17 at 10:19

















    I've tried the first two examples and it just seems to hang. I don't get an error message, nor do I get a new prompt, just nothing.

    – MaQleod
    Nov 8 '11 at 1:00





    I've tried the first two examples and it just seems to hang. I don't get an error message, nor do I get a new prompt, just nothing.

    – MaQleod
    Nov 8 '11 at 1:00




    2




    2





    @MaQleod Oh, it's waiting for input on standard input, which here is the terminal because you haven't redirected it. Here you'd do an input redirection sed … <messages, since you want to process data from a file. To act on data produced by another command, you'd use a pipe: somecommand | sed ….

    – Gilles
    Nov 8 '11 at 1:02





    @MaQleod Oh, it's waiting for input on standard input, which here is the terminal because you haven't redirected it. Here you'd do an input redirection sed … <messages, since you want to process data from a file. To act on data produced by another command, you'd use a pipe: somecommand | sed ….

    – Gilles
    Nov 8 '11 at 1:02




    1




    1





    right, end of day blackout there. command works perfectly, thanks.

    – MaQleod
    Nov 8 '11 at 16:37





    right, end of day blackout there. command works perfectly, thanks.

    – MaQleod
    Nov 8 '11 at 16:37













    Best sed explanation I've seen so far -- thanks!

    – Jon Wadsworth
    Sep 16 '16 at 17:47





    Best sed explanation I've seen so far -- thanks!

    – Jon Wadsworth
    Sep 16 '16 at 17:47




    1




    1





    @ungalcrys Shorter version of what? This isn't equivalent to any of the commands in my answer. I'd recommend writing it as sed 's/^.*stalled//' since -r is specific to Linux and doesn't work on other systems such as macOS and here you aren't getting any benefit from it.

    – Gilles
    Aug 9 '17 at 10:19






    @ungalcrys Shorter version of what? This isn't equivalent to any of the commands in my answer. I'd recommend writing it as sed 's/^.*stalled//' since -r is specific to Linux and doesn't work on other systems such as macOS and here you aren't getting any benefit from it.

    – Gilles
    Aug 9 '17 at 10:19














    67














    The other canonical tool you already use: grep:



    For example:



    grep -o 'stalled.*'


    Has the same result as the second option of Gilles:



    sed -n -e 's/^.*(stalled: )/1/p'


    The -o flag returns the --only-matching part of the expression, so not the entire line which is - of course - normally done by grep.



    To remove the "stalled :" from the output, we can use a third canonical tool, cut:



    grep -o 'stalled.*' | cut -f2- -d:


    The cut command uses delimiter : and prints field 2 till the end. It's a matter of preference of course, but the cut syntax I find very easy to remember.






    share|improve this answer




















    • 1





      Thanks for mentioning the -o option! I wanted to point out that grep doesn't recognize the n as a newline, so your first example only matches to the first n character. For example, echo "Hello Anne" | grep -o 'A[^n]*' returns the string A. However, echo "Hello Anne" | grep -o 'A.*' returns the expected Anne, since . matches any character except the newline.

      – adamlamar
      Mar 16 '15 at 21:52






    • 1





      Note that the quotes around the cut delimiter -d':' are removed by @poige. I find it easier to remember with quotes, e.g. with -d' ' or -d';'.

      – Anne van Rossum
      Jul 10 '17 at 20:44











    • According to your finding it should be easier to remember to use quotes with -f 2 too. Seriously, why not?

      – poige
      Aug 26 '17 at 10:26











    • Because a delimiter like a semi-colon ; rather than a colon : will be interpreted differently if not quoted. Of course that's logical behavior, but still I like to rely on muscle memory. I don't like to quote the delimiter one time but not the other time. Just personal preference, like I said before: easier to remember.

      – Anne van Rossum
      Oct 7 '17 at 18:09











    • the period that is part of the .* is needed, worked well for me: cat filename | grep 'Return only this line xyz text' | grep -o 'xyz.*' returns xyz text

      – ron
      Dec 12 '17 at 19:01
















    67














    The other canonical tool you already use: grep:



    For example:



    grep -o 'stalled.*'


    Has the same result as the second option of Gilles:



    sed -n -e 's/^.*(stalled: )/1/p'


    The -o flag returns the --only-matching part of the expression, so not the entire line which is - of course - normally done by grep.



    To remove the "stalled :" from the output, we can use a third canonical tool, cut:



    grep -o 'stalled.*' | cut -f2- -d:


    The cut command uses delimiter : and prints field 2 till the end. It's a matter of preference of course, but the cut syntax I find very easy to remember.






    share|improve this answer




















    • 1





      Thanks for mentioning the -o option! I wanted to point out that grep doesn't recognize the n as a newline, so your first example only matches to the first n character. For example, echo "Hello Anne" | grep -o 'A[^n]*' returns the string A. However, echo "Hello Anne" | grep -o 'A.*' returns the expected Anne, since . matches any character except the newline.

      – adamlamar
      Mar 16 '15 at 21:52






    • 1





      Note that the quotes around the cut delimiter -d':' are removed by @poige. I find it easier to remember with quotes, e.g. with -d' ' or -d';'.

      – Anne van Rossum
      Jul 10 '17 at 20:44











    • According to your finding it should be easier to remember to use quotes with -f 2 too. Seriously, why not?

      – poige
      Aug 26 '17 at 10:26











    • Because a delimiter like a semi-colon ; rather than a colon : will be interpreted differently if not quoted. Of course that's logical behavior, but still I like to rely on muscle memory. I don't like to quote the delimiter one time but not the other time. Just personal preference, like I said before: easier to remember.

      – Anne van Rossum
      Oct 7 '17 at 18:09











    • the period that is part of the .* is needed, worked well for me: cat filename | grep 'Return only this line xyz text' | grep -o 'xyz.*' returns xyz text

      – ron
      Dec 12 '17 at 19:01














    67












    67








    67







    The other canonical tool you already use: grep:



    For example:



    grep -o 'stalled.*'


    Has the same result as the second option of Gilles:



    sed -n -e 's/^.*(stalled: )/1/p'


    The -o flag returns the --only-matching part of the expression, so not the entire line which is - of course - normally done by grep.



    To remove the "stalled :" from the output, we can use a third canonical tool, cut:



    grep -o 'stalled.*' | cut -f2- -d:


    The cut command uses delimiter : and prints field 2 till the end. It's a matter of preference of course, but the cut syntax I find very easy to remember.






    share|improve this answer















    The other canonical tool you already use: grep:



    For example:



    grep -o 'stalled.*'


    Has the same result as the second option of Gilles:



    sed -n -e 's/^.*(stalled: )/1/p'


    The -o flag returns the --only-matching part of the expression, so not the entire line which is - of course - normally done by grep.



    To remove the "stalled :" from the output, we can use a third canonical tool, cut:



    grep -o 'stalled.*' | cut -f2- -d:


    The cut command uses delimiter : and prints field 2 till the end. It's a matter of preference of course, but the cut syntax I find very easy to remember.







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Aug 26 '16 at 1:50









    poige

    4,1951646




    4,1951646










    answered Aug 8 '14 at 11:46









    Anne van RossumAnne van Rossum

    869711




    869711







    • 1





      Thanks for mentioning the -o option! I wanted to point out that grep doesn't recognize the n as a newline, so your first example only matches to the first n character. For example, echo "Hello Anne" | grep -o 'A[^n]*' returns the string A. However, echo "Hello Anne" | grep -o 'A.*' returns the expected Anne, since . matches any character except the newline.

      – adamlamar
      Mar 16 '15 at 21:52






    • 1





      Note that the quotes around the cut delimiter -d':' are removed by @poige. I find it easier to remember with quotes, e.g. with -d' ' or -d';'.

      – Anne van Rossum
      Jul 10 '17 at 20:44











    • According to your finding it should be easier to remember to use quotes with -f 2 too. Seriously, why not?

      – poige
      Aug 26 '17 at 10:26











    • Because a delimiter like a semi-colon ; rather than a colon : will be interpreted differently if not quoted. Of course that's logical behavior, but still I like to rely on muscle memory. I don't like to quote the delimiter one time but not the other time. Just personal preference, like I said before: easier to remember.

      – Anne van Rossum
      Oct 7 '17 at 18:09











    • the period that is part of the .* is needed, worked well for me: cat filename | grep 'Return only this line xyz text' | grep -o 'xyz.*' returns xyz text

      – ron
      Dec 12 '17 at 19:01













    • 1





      Thanks for mentioning the -o option! I wanted to point out that grep doesn't recognize the n as a newline, so your first example only matches to the first n character. For example, echo "Hello Anne" | grep -o 'A[^n]*' returns the string A. However, echo "Hello Anne" | grep -o 'A.*' returns the expected Anne, since . matches any character except the newline.

      – adamlamar
      Mar 16 '15 at 21:52






    • 1





      Note that the quotes around the cut delimiter -d':' are removed by @poige. I find it easier to remember with quotes, e.g. with -d' ' or -d';'.

      – Anne van Rossum
      Jul 10 '17 at 20:44











    • According to your finding it should be easier to remember to use quotes with -f 2 too. Seriously, why not?

      – poige
      Aug 26 '17 at 10:26











    • Because a delimiter like a semi-colon ; rather than a colon : will be interpreted differently if not quoted. Of course that's logical behavior, but still I like to rely on muscle memory. I don't like to quote the delimiter one time but not the other time. Just personal preference, like I said before: easier to remember.

      – Anne van Rossum
      Oct 7 '17 at 18:09











    • the period that is part of the .* is needed, worked well for me: cat filename | grep 'Return only this line xyz text' | grep -o 'xyz.*' returns xyz text

      – ron
      Dec 12 '17 at 19:01








    1




    1





    Thanks for mentioning the -o option! I wanted to point out that grep doesn't recognize the n as a newline, so your first example only matches to the first n character. For example, echo "Hello Anne" | grep -o 'A[^n]*' returns the string A. However, echo "Hello Anne" | grep -o 'A.*' returns the expected Anne, since . matches any character except the newline.

    – adamlamar
    Mar 16 '15 at 21:52





    Thanks for mentioning the -o option! I wanted to point out that grep doesn't recognize the n as a newline, so your first example only matches to the first n character. For example, echo "Hello Anne" | grep -o 'A[^n]*' returns the string A. However, echo "Hello Anne" | grep -o 'A.*' returns the expected Anne, since . matches any character except the newline.

    – adamlamar
    Mar 16 '15 at 21:52




    1




    1





    Note that the quotes around the cut delimiter -d':' are removed by @poige. I find it easier to remember with quotes, e.g. with -d' ' or -d';'.

    – Anne van Rossum
    Jul 10 '17 at 20:44





    Note that the quotes around the cut delimiter -d':' are removed by @poige. I find it easier to remember with quotes, e.g. with -d' ' or -d';'.

    – Anne van Rossum
    Jul 10 '17 at 20:44













    According to your finding it should be easier to remember to use quotes with -f 2 too. Seriously, why not?

    – poige
    Aug 26 '17 at 10:26





    According to your finding it should be easier to remember to use quotes with -f 2 too. Seriously, why not?

    – poige
    Aug 26 '17 at 10:26













    Because a delimiter like a semi-colon ; rather than a colon : will be interpreted differently if not quoted. Of course that's logical behavior, but still I like to rely on muscle memory. I don't like to quote the delimiter one time but not the other time. Just personal preference, like I said before: easier to remember.

    – Anne van Rossum
    Oct 7 '17 at 18:09





    Because a delimiter like a semi-colon ; rather than a colon : will be interpreted differently if not quoted. Of course that's logical behavior, but still I like to rely on muscle memory. I don't like to quote the delimiter one time but not the other time. Just personal preference, like I said before: easier to remember.

    – Anne van Rossum
    Oct 7 '17 at 18:09













    the period that is part of the .* is needed, worked well for me: cat filename | grep 'Return only this line xyz text' | grep -o 'xyz.*' returns xyz text

    – ron
    Dec 12 '17 at 19:01






    the period that is part of the .* is needed, worked well for me: cat filename | grep 'Return only this line xyz text' | grep -o 'xyz.*' returns xyz text

    – ron
    Dec 12 '17 at 19:01












    4














    I used ifconfig | grep eth0 | cut -f3- -d: to take this



     [root@MyPC ~]# ifconfig
    eth0 Link encap:Ethernet HWaddr AC:B4:CA:DD:E6:F8
    inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:78998810244 errors:1 dropped:0 overruns:0 frame:1
    TX packets:20113430261 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:110947036025418 (100.9 TiB) TX bytes:15010653222322 (13.6 TiB)


    and make it look like this



     [root@MyPC ~]# ifconfig | grep eth0 | cut -f3- -d:
    C4:7A:4D:F6:B8





    share|improve this answer




















    • 1





      Does this answer the question?

      – Stephen Rauch
      Mar 31 '17 at 4:56






    • 1





      You can use cat /sys/class/net/*/address, no parsing required.

      – Anne van Rossum
      Dec 13 '17 at 16:58















    4














    I used ifconfig | grep eth0 | cut -f3- -d: to take this



     [root@MyPC ~]# ifconfig
    eth0 Link encap:Ethernet HWaddr AC:B4:CA:DD:E6:F8
    inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:78998810244 errors:1 dropped:0 overruns:0 frame:1
    TX packets:20113430261 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:110947036025418 (100.9 TiB) TX bytes:15010653222322 (13.6 TiB)


    and make it look like this



     [root@MyPC ~]# ifconfig | grep eth0 | cut -f3- -d:
    C4:7A:4D:F6:B8





    share|improve this answer




















    • 1





      Does this answer the question?

      – Stephen Rauch
      Mar 31 '17 at 4:56






    • 1





      You can use cat /sys/class/net/*/address, no parsing required.

      – Anne van Rossum
      Dec 13 '17 at 16:58













    4












    4








    4







    I used ifconfig | grep eth0 | cut -f3- -d: to take this



     [root@MyPC ~]# ifconfig
    eth0 Link encap:Ethernet HWaddr AC:B4:CA:DD:E6:F8
    inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:78998810244 errors:1 dropped:0 overruns:0 frame:1
    TX packets:20113430261 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:110947036025418 (100.9 TiB) TX bytes:15010653222322 (13.6 TiB)


    and make it look like this



     [root@MyPC ~]# ifconfig | grep eth0 | cut -f3- -d:
    C4:7A:4D:F6:B8





    share|improve this answer















    I used ifconfig | grep eth0 | cut -f3- -d: to take this



     [root@MyPC ~]# ifconfig
    eth0 Link encap:Ethernet HWaddr AC:B4:CA:DD:E6:F8
    inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:78998810244 errors:1 dropped:0 overruns:0 frame:1
    TX packets:20113430261 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:110947036025418 (100.9 TiB) TX bytes:15010653222322 (13.6 TiB)


    and make it look like this



     [root@MyPC ~]# ifconfig | grep eth0 | cut -f3- -d:
    C4:7A:4D:F6:B8






    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited 2 hours ago









    Rui F Ribeiro

    41.9k1483142




    41.9k1483142










    answered Mar 31 '17 at 4:52









    Luis PerezLuis Perez

    411




    411







    • 1





      Does this answer the question?

      – Stephen Rauch
      Mar 31 '17 at 4:56






    • 1





      You can use cat /sys/class/net/*/address, no parsing required.

      – Anne van Rossum
      Dec 13 '17 at 16:58












    • 1





      Does this answer the question?

      – Stephen Rauch
      Mar 31 '17 at 4:56






    • 1





      You can use cat /sys/class/net/*/address, no parsing required.

      – Anne van Rossum
      Dec 13 '17 at 16:58







    1




    1





    Does this answer the question?

    – Stephen Rauch
    Mar 31 '17 at 4:56





    Does this answer the question?

    – Stephen Rauch
    Mar 31 '17 at 4:56




    1




    1





    You can use cat /sys/class/net/*/address, no parsing required.

    – Anne van Rossum
    Dec 13 '17 at 16:58





    You can use cat /sys/class/net/*/address, no parsing required.

    – Anne van Rossum
    Dec 13 '17 at 16:58











    1














    Yet another canonical tool you considered awk could be used with the following line:



    awk -F"stalled" '/stalled/print $2' messages


    Detailed explanation:




    • -F defines a separator for the line, i.e., "stalled". Everything before the separator is addressed with $1 and everything after with $2.


    • /reg-ex/ Searches for the matching regular expression, in this case "stalled".


    • print $<n> - prints n column. Since your separator is defined as stalled, everything after stalled is considered to be the second column.





    share|improve this answer










    New contributor




    robertm.tum is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.
























      1














      Yet another canonical tool you considered awk could be used with the following line:



      awk -F"stalled" '/stalled/print $2' messages


      Detailed explanation:




      • -F defines a separator for the line, i.e., "stalled". Everything before the separator is addressed with $1 and everything after with $2.


      • /reg-ex/ Searches for the matching regular expression, in this case "stalled".


      • print $<n> - prints n column. Since your separator is defined as stalled, everything after stalled is considered to be the second column.





      share|improve this answer










      New contributor




      robertm.tum is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






















        1












        1








        1







        Yet another canonical tool you considered awk could be used with the following line:



        awk -F"stalled" '/stalled/print $2' messages


        Detailed explanation:




        • -F defines a separator for the line, i.e., "stalled". Everything before the separator is addressed with $1 and everything after with $2.


        • /reg-ex/ Searches for the matching regular expression, in this case "stalled".


        • print $<n> - prints n column. Since your separator is defined as stalled, everything after stalled is considered to be the second column.





        share|improve this answer










        New contributor




        robertm.tum is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.










        Yet another canonical tool you considered awk could be used with the following line:



        awk -F"stalled" '/stalled/print $2' messages


        Detailed explanation:




        • -F defines a separator for the line, i.e., "stalled". Everything before the separator is addressed with $1 and everything after with $2.


        • /reg-ex/ Searches for the matching regular expression, in this case "stalled".


        • print $<n> - prints n column. Since your separator is defined as stalled, everything after stalled is considered to be the second column.






        share|improve this answer










        New contributor




        robertm.tum is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        share|improve this answer



        share|improve this answer








        edited 1 hour ago









        Rui F Ribeiro

        41.9k1483142




        41.9k1483142






        New contributor




        robertm.tum is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        answered 2 days ago









        robertm.tumrobertm.tum

        113




        113




        New contributor




        robertm.tum is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.





        New contributor





        robertm.tum is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.






        robertm.tum is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.



























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f24140%2freturn-only-the-portion-of-a-line-after-a-matching-pattern%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Àrd-bhaile Cathair chruinne/Baile mòr cruinne | Artagailean ceangailte | Clàr-taice na seòladaireachd

            Cannot Extend partition with GParted The 2019 Stack Overflow Developer Survey Results Are In Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) 2019 Community Moderator Election ResultsCan't increase partition size with GParted?GParted doesn't recognize the unallocated space after my current partitionWhat is the best way to add unallocated space located before to Ubuntu 12.04 partition with GParted live?I can't figure out how to extend my Arch home partition into free spaceGparted Linux Mint 18.1 issueTrying to extend but swap partition is showing as Unknown in Gparted, shows proper from fdiskRearrange partitions in gparted to extend a partitionUnable to extend partition even though unallocated space is next to it using GPartedAllocate free space to root partitiongparted: how to merge unallocated space with a partition

            대한민국 목차 국명 지리 역사 정치 국방 경제 사회 문화 국제 순위 관련 항목 각주 외부 링크 둘러보기 메뉴북위 37° 34′ 08″ 동경 126° 58′ 36″ / 북위 37.568889° 동경 126.976667°  / 37.568889; 126.976667ehThe Korean Repository문단을 편집문단을 편집추가해Clarkson PLC 사Report for Selected Countries and Subjects-Korea“Human Development Index and its components: P.198”“http://www.law.go.kr/%EB%B2%95%EB%A0%B9/%EB%8C%80%ED%95%9C%EB%AF%BC%EA%B5%AD%EA%B5%AD%EA%B8%B0%EB%B2%95”"한국은 국제법상 한반도 유일 합법정부 아니다" - 오마이뉴스 모바일Report for Selected Countries and Subjects: South Korea격동의 역사와 함께한 조선일보 90년 : 조선일보 인수해 혁신시킨 신석우, 임시정부 때는 '대한민국' 국호(國號) 정해《우리가 몰랐던 우리 역사: 나라 이름의 비밀을 찾아가는 역사 여행》“남북 공식호칭 ‘남한’‘북한’으로 쓴다”“Corea 대 Korea, 누가 이긴 거야?”국내기후자료 - 한국[김대중 前 대통령 서거] 과감한 구조개혁 'DJ노믹스'로 최단기간 환란극복 :: 네이버 뉴스“이라크 "韓-쿠르드 유전개발 MOU 승인 안해"(종합)”“해외 우리국민 추방사례 43%가 일본”차기전차 K2'흑표'의 세계 최고 전력 분석, 쿠키뉴스 엄기영, 2007-03-02두산인프라, 헬기잡는 장갑차 'K21'...내년부터 공급, 고뉴스 이대준, 2008-10-30과거 내용 찾기mk 뉴스 - 구매력 기준으로 보면 한국 1인당 소득 3만弗과거 내용 찾기"The N-11: More Than an Acronym"Archived조선일보 최우석, 2008-11-01Global 500 2008: Countries - South Korea“몇년째 '시한폭탄'... 가계부채, 올해는 터질까”가구당 부채 5000만원 처음 넘어서“‘빚’으로 내몰리는 사회.. 위기의 가계대출”“[경제365] 공공부문 부채 급증…800조 육박”“"소득 양극화 다소 완화...불평등은 여전"”“공정사회·공생발전 한참 멀었네”iSuppli,08年2QのDRAMシェア・ランキングを発表(08/8/11)South Korea dominates shipbuilding industry | Stock Market News & Stocks to Watch from StraightStocks한국 자동차 생산, 3년 연속 세계 5위자동차수출 '현대-삼성 웃고 기아-대우-쌍용은 울고' 과거 내용 찾기동반성장위 창립 1주년 맞아Archived"중기적합 3개업종 합의 무시한 채 선정"李대통령, 사업 무분별 확장 소상공인 생계 위협 질타삼성-LG, 서민업종인 빵·분식사업 잇따라 철수상생은 뒷전…SSM ‘몸집 불리기’ 혈안Archived“경부고속도에 '아시안하이웨이' 표지판”'철의 실크로드' 앞서 '말(言)의 실크로드'부터, 프레시안 정창현, 2008-10-01“'서울 지하철은 안전한가?'”“서울시 “올해 안에 모든 지하철역 스크린도어 설치””“부산지하철 1,2호선 승강장 안전펜스 설치 완료”“전교조, 정부 노조 통계서 처음 빠져”“[Weekly BIZ] 도요타 '제로 이사회'가 리콜 사태 불러들였다”“S Korea slams high tuition costs”““정치가 여론 양극화 부채질… 합리주의 절실””“〈"`촛불집회'는 민주주의의 질적 변화 상징"〉”““촛불집회가 민주주의 왜곡 초래””“국민 65%, "한국 노사관계 대립적"”“한국 국가경쟁력 27위‥노사관계 '꼴찌'”“제대로 형성되지 않은 대한민국 이념지형”“[신년기획-갈등의 시대] 갈등지수 OECD 4위…사회적 손실 GDP 27% 무려 300조”“2012 총선-대선의 키워드는 '국민과 소통'”“한국 삶의 질 27위, 2000년과 2008년 연속 하위권 머물러”“[해피 코리아] 행복점수 68점…해외 평가선 '낙제점'”“한국 어린이·청소년 행복지수 3년 연속 OECD ‘꼴찌’”“한국 이혼율 OECD중 8위”“[통계청] 한국 이혼율 OECD 4위”“오피니언 [이렇게 생각한다] `부부의 날` 에 돌아본 이혼율 1위 한국”“Suicide Rates by Country, Global Health Observatory Data Repository.”“1. 또 다른 차별”“오피니언 [편집자에게] '왕따'와 '패거리 정치' 심리는 닮은꼴”“[미래한국리포트] 무한경쟁에 빠진 대한민국”“대학생 98% "외모가 경쟁력이라는 말 동의"”“특급호텔 웨딩·200만원대 유모차… "남보다 더…" 호화病, 고질병 됐다”“[스트레스 공화국] ① 경쟁사회, 스트레스 쌓인다”““매일 30여명 자살 한국, 의사보다 무속인에…””“"자살 부르는 '우울증', 환자 중 85% 치료 안 받아"”“정신병원을 가다”“대한민국도 ‘묻지마 범죄’,안전지대 아니다”“유엔 "학생 '성적 지향'에 따른 차별 금지하라"”“유엔아동권리위원회 보고서 및 번역본 원문”“고졸 성공스토리 담은 '제빵왕 김탁구' 드라마 나온다”“‘빛 좋은 개살구’ 고졸 취업…실습 대신 착취”원본 문서“정신건강, 사회적 편견부터 고쳐드립니다”‘소통’과 ‘행복’에 목 마른 사회가 잠들어 있던 ‘심리학’ 깨웠다“[포토] 사유리-곽금주 교수의 유쾌한 심리상담”“"올해 한국인 평균 영화관람횟수 세계 1위"(종합)”“[게임연중기획] 게임은 문화다-여가활동 1순위 게임”“영화속 ‘영어 지상주의’ …“왠지 씁쓸한데””“2월 `신문 부수 인증기관` 지정..방송법 후속작업”“무료신문 성장동력 ‘차별성’과 ‘갈등해소’”대한민국 국회 법률지식정보시스템"Pew Research Center's Religion & Public Life Project: South Korea"“amp;vwcd=MT_ZTITLE&path=인구·가구%20>%20인구총조사%20>%20인구부문%20>%20 총조사인구(2005)%20>%20전수부문&oper_YN=Y&item=&keyword=종교별%20인구& amp;lang_mode=kor&list_id= 2005년 통계청 인구 총조사”원본 문서“한국인이 좋아하는 취미와 운동 (2004-2009)”“한국인이 좋아하는 취미와 운동 (2004-2014)”Archived“한국, `부분적 언론자유국' 강등〈프리덤하우스〉”“국경없는기자회 "한국, 인터넷감시 대상국"”“한국, 조선산업 1위 유지(S. Korea Stays Top Shipbuilding Nation) RZD-Partner Portal”원본 문서“한국, 4년 만에 ‘선박건조 1위’”“옛 마산시,인터넷속도 세계 1위”“"한국 초고속 인터넷망 세계1위"”“인터넷·휴대폰 요금, 외국보다 훨씬 비싸”“한국 관세행정 6년 연속 세계 '1위'”“한국 교통사고 사망자 수 OECD 회원국 중 2위”“결핵 후진국' 한국, 환자가 급증한 이유는”“수술은 신중해야… 자칫하면 생명 위협”대한민국분류대한민국의 지도대한민국 정부대표 다국어포털대한민국 전자정부대한민국 국회한국방송공사about korea and information korea브리태니커 백과사전(한국편)론리플래닛의 정보(한국편)CIA의 세계 정보(한국편)마리암 부디아 (Mariam Budia),『한국: 하늘이 내린 한 폭의 그림』, 서울: 트랜스라틴 19호 (2012년 3월)대한민국ehehehehehehehehehehehehehehWorldCat132441370n791268020000 0001 2308 81034078029-6026373548cb11863345f(데이터)00573706ge128495