grep: Not a recognized flag: o











up vote
3
down vote

favorite












I am trying to extract the date and timestamps from my log file string ($Data in the below code) on AIX using a regex and loading it into a text file as below:



Data="Logs/2018-12-03/log.txt:3:2018-12-03 00:00:04,333 452621453 [blah blah blah"

echo "$data" | grep -o -n '[0-9]{4}-(0[1-9]|1[0-2])-(0[1-9]|[1-2][0-9]|3[0-1]) (2[0-3]|[01][0-9]):[0-5][0-9]' >  timestamps.txt


I get the below error most probably due to the unix version in my host being too old and it doesn't recognize the -o option. Is there any alternative method in which I can get the functionality of -o done?



grep: Not a recognized flag: o

Usage: grep [-r] [-R] [-H] [-L] [-E|-F] [-c|-l|-q] [-insvxbhwyu] [-p[parasep]] -e pattern_list...

    [-f pattern_file...] [file...]

Usage: grep [-r] [-R] [-H] [-L]  [-E|-F] [-c|-l|-q] [-insvxbhwyu] [-p[parasep]] [-e pattern_list...]

    -f pattern_file... [file...]

Usage: grep [-r] [-R] [-H] [-L] [-E|-F] [-c|-l|-q] [-insvxbhwyu] [-p[parasep]] pattern_list [file...]





grep variable aix







share|improve this question
























  • What operating system are you using?
    – terdon♦
    Dec 4 at 9:16










  • The command uname -s gives me 'AIX'
    – BlueNinja
    Dec 4 at 9:21






  • 1




    It's not that your Unix is "too old", it's that you are relying on non-standard functionality.
    – Kusalananda
    Dec 4 at 9:24










  • Is your Data variable a line from the output of grep? If it is, you can probably do whatever you are doing a fair bit more efficiently by running perl or awk over the original log files. Parsing the output of grep is not an ideal solution.
    – Kusalananda
    Dec 4 at 10:41

















up vote
3
down vote

favorite












I am trying to extract the date and timestamps from my log file string ($Data in the below code) on AIX using a regex and loading it into a text file as below:



Data="Logs/2018-12-03/log.txt:3:2018-12-03 00:00:04,333 452621453 [blah blah blah"

echo "$data" | grep -o -n '[0-9]{4}-(0[1-9]|1[0-2])-(0[1-9]|[1-2][0-9]|3[0-1]) (2[0-3]|[01][0-9]):[0-5][0-9]' >  timestamps.txt


I get the below error most probably due to the unix version in my host being too old and it doesn't recognize the -o option. Is there any alternative method in which I can get the functionality of -o done?



grep: Not a recognized flag: o

Usage: grep [-r] [-R] [-H] [-L] [-E|-F] [-c|-l|-q] [-insvxbhwyu] [-p[parasep]] -e pattern_list...

    [-f pattern_file...] [file...]

Usage: grep [-r] [-R] [-H] [-L]  [-E|-F] [-c|-l|-q] [-insvxbhwyu] [-p[parasep]] [-e pattern_list...]

    -f pattern_file... [file...]

Usage: grep [-r] [-R] [-H] [-L] [-E|-F] [-c|-l|-q] [-insvxbhwyu] [-p[parasep]] pattern_list [file...]





grep variable aix







share|improve this question
























  • What operating system are you using?
    – terdon♦
    Dec 4 at 9:16










  • The command uname -s gives me 'AIX'
    – BlueNinja
    Dec 4 at 9:21






  • 1




    It's not that your Unix is "too old", it's that you are relying on non-standard functionality.
    – Kusalananda
    Dec 4 at 9:24










  • Is your Data variable a line from the output of grep? If it is, you can probably do whatever you are doing a fair bit more efficiently by running perl or awk over the original log files. Parsing the output of grep is not an ideal solution.
    – Kusalananda
    Dec 4 at 10:41















up vote
3
down vote

favorite









up vote
3
down vote

favorite











I am trying to extract the date and timestamps from my log file string ($Data in the below code) on AIX using a regex and loading it into a text file as below:



Data="Logs/2018-12-03/log.txt:3:2018-12-03 00:00:04,333 452621453 [blah blah blah"

echo "$data" | grep -o -n '[0-9]{4}-(0[1-9]|1[0-2])-(0[1-9]|[1-2][0-9]|3[0-1]) (2[0-3]|[01][0-9]):[0-5][0-9]' >  timestamps.txt


I get the below error most probably due to the unix version in my host being too old and it doesn't recognize the -o option. Is there any alternative method in which I can get the functionality of -o done?



grep: Not a recognized flag: o

Usage: grep [-r] [-R] [-H] [-L] [-E|-F] [-c|-l|-q] [-insvxbhwyu] [-p[parasep]] -e pattern_list...

    [-f pattern_file...] [file...]

Usage: grep [-r] [-R] [-H] [-L]  [-E|-F] [-c|-l|-q] [-insvxbhwyu] [-p[parasep]] [-e pattern_list...]

    -f pattern_file... [file...]

Usage: grep [-r] [-R] [-H] [-L] [-E|-F] [-c|-l|-q] [-insvxbhwyu] [-p[parasep]] pattern_list [file...]





grep variable aix







share|improve this question















I am trying to extract the date and timestamps from my log file string ($Data in the below code) on AIX using a regex and loading it into a text file as below:



Data="Logs/2018-12-03/log.txt:3:2018-12-03 00:00:04,333 452621453 [blah blah blah"

echo "$data" | grep -o -n '[0-9]{4}-(0[1-9]|1[0-2])-(0[1-9]|[1-2][0-9]|3[0-1]) (2[0-3]|[01][0-9]):[0-5][0-9]' >  timestamps.txt


I get the below error most probably due to the unix version in my host being too old and it doesn't recognize the -o option. Is there any alternative method in which I can get the functionality of -o done?



grep: Not a recognized flag: o

Usage: grep [-r] [-R] [-H] [-L] [-E|-F] [-c|-l|-q] [-insvxbhwyu] [-p[parasep]] -e pattern_list...

    [-f pattern_file...] [file...]

Usage: grep [-r] [-R] [-H] [-L]  [-E|-F] [-c|-l|-q] [-insvxbhwyu] [-p[parasep]] [-e pattern_list...]

    -f pattern_file... [file...]

Usage: grep [-r] [-R] [-H] [-L] [-E|-F] [-c|-l|-q] [-insvxbhwyu] [-p[parasep]] pattern_list [file...]





grep variable aix




grep variable aix






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 9 at 14:29









Jeff Schaller

37.8k1053122




37.8k1053122










asked Dec 4 at 9:03









BlueNinja

213




213












  • What operating system are you using?
    – terdon♦
    Dec 4 at 9:16










  • The command uname -s gives me 'AIX'
    – BlueNinja
    Dec 4 at 9:21






  • 1




    It's not that your Unix is "too old", it's that you are relying on non-standard functionality.
    – Kusalananda
    Dec 4 at 9:24










  • Is your Data variable a line from the output of grep? If it is, you can probably do whatever you are doing a fair bit more efficiently by running perl or awk over the original log files. Parsing the output of grep is not an ideal solution.
    – Kusalananda
    Dec 4 at 10:41




















  • What operating system are you using?
    – terdon♦
    Dec 4 at 9:16










  • The command uname -s gives me 'AIX'
    – BlueNinja
    Dec 4 at 9:21






  • 1




    It's not that your Unix is "too old", it's that you are relying on non-standard functionality.
    – Kusalananda
    Dec 4 at 9:24










  • Is your Data variable a line from the output of grep? If it is, you can probably do whatever you are doing a fair bit more efficiently by running perl or awk over the original log files. Parsing the output of grep is not an ideal solution.
    – Kusalananda
    Dec 4 at 10:41


















What operating system are you using?
– terdon♦
Dec 4 at 9:16




What operating system are you using?
– terdon♦
Dec 4 at 9:16












The command uname -s gives me 'AIX'
– BlueNinja
Dec 4 at 9:21




The command uname -s gives me 'AIX'
– BlueNinja
Dec 4 at 9:21




1




1




It's not that your Unix is "too old", it's that you are relying on non-standard functionality.
– Kusalananda
Dec 4 at 9:24




It's not that your Unix is "too old", it's that you are relying on non-standard functionality.
– Kusalananda
Dec 4 at 9:24












Is your Data variable a line from the output of grep? If it is, you can probably do whatever you are doing a fair bit more efficiently by running perl or awk over the original log files. Parsing the output of grep is not an ideal solution.
– Kusalananda
Dec 4 at 10:41






Is your Data variable a line from the output of grep? If it is, you can probably do whatever you are doing a fair bit more efficiently by running perl or awk over the original log files. Parsing the output of grep is not an ideal solution.
– Kusalananda
Dec 4 at 10:41












1 Answer
1






active

oldest

votes

















up vote
4
down vote



accepted










Note that your regex wouldn't work even if -o was recognized by your grep implementation. You also need -E to enable extended regular expressions. Assuming you have perl, which you probably do, you can try:



$ Data="Logs/2018-12-03/log.txt:3:2018-12-03 00:00:04,333 452621453 [blah blah blah"

$ echo "$Data" | perl -lne '/[0-9]{4}-(0[1-9]|1[0-2])-(0[1-9]|[1-2][0-9]|3[0-1]) (2[0-3]|[01][0-9]):[0-5][0-9]/ && print "$.:$&"'

1:2018-12-03 00:00


But do you really need to make your regex that complicated? Isn't this enough?



$ echo "$Data" | perl -lne '/d{4}-d{2}-d{2} d{2}:d{2}/ && print "$.:$&"'

1:2018-12-03 00:00





share|improve this answer



















  • 1




    Note also that the data in the Data variable is a line produced by grep. This makes me think that the user is first running a grep of some kind to get the lines they want, and then iterating in a shell loop over these lines. This is quite an suboptimal approach to log file parsing.
    – Kusalananda
    Dec 4 at 10:43













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',
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%2f485850%2fgrep-not-a-recognized-flag-o%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
4
down vote



accepted










Note that your regex wouldn't work even if -o was recognized by your grep implementation. You also need -E to enable extended regular expressions. Assuming you have perl, which you probably do, you can try:



$ Data="Logs/2018-12-03/log.txt:3:2018-12-03 00:00:04,333 452621453 [blah blah blah"

$ echo "$Data" | perl -lne '/[0-9]{4}-(0[1-9]|1[0-2])-(0[1-9]|[1-2][0-9]|3[0-1]) (2[0-3]|[01][0-9]):[0-5][0-9]/ && print "$.:$&"'

1:2018-12-03 00:00


But do you really need to make your regex that complicated? Isn't this enough?



$ echo "$Data" | perl -lne '/d{4}-d{2}-d{2} d{2}:d{2}/ && print "$.:$&"'

1:2018-12-03 00:00





share|improve this answer



















  • 1




    Note also that the data in the Data variable is a line produced by grep. This makes me think that the user is first running a grep of some kind to get the lines they want, and then iterating in a shell loop over these lines. This is quite an suboptimal approach to log file parsing.
    – Kusalananda
    Dec 4 at 10:43

















up vote
4
down vote



accepted










Note that your regex wouldn't work even if -o was recognized by your grep implementation. You also need -E to enable extended regular expressions. Assuming you have perl, which you probably do, you can try:



$ Data="Logs/2018-12-03/log.txt:3:2018-12-03 00:00:04,333 452621453 [blah blah blah"

$ echo "$Data" | perl -lne '/[0-9]{4}-(0[1-9]|1[0-2])-(0[1-9]|[1-2][0-9]|3[0-1]) (2[0-3]|[01][0-9]):[0-5][0-9]/ && print "$.:$&"'

1:2018-12-03 00:00


But do you really need to make your regex that complicated? Isn't this enough?



$ echo "$Data" | perl -lne '/d{4}-d{2}-d{2} d{2}:d{2}/ && print "$.:$&"'

1:2018-12-03 00:00





share|improve this answer



















  • 1




    Note also that the data in the Data variable is a line produced by grep. This makes me think that the user is first running a grep of some kind to get the lines they want, and then iterating in a shell loop over these lines. This is quite an suboptimal approach to log file parsing.
    – Kusalananda
    Dec 4 at 10:43















up vote
4
down vote



accepted







up vote
4
down vote



accepted






Note that your regex wouldn't work even if -o was recognized by your grep implementation. You also need -E to enable extended regular expressions. Assuming you have perl, which you probably do, you can try:



$ Data="Logs/2018-12-03/log.txt:3:2018-12-03 00:00:04,333 452621453 [blah blah blah"

$ echo "$Data" | perl -lne '/[0-9]{4}-(0[1-9]|1[0-2])-(0[1-9]|[1-2][0-9]|3[0-1]) (2[0-3]|[01][0-9]):[0-5][0-9]/ && print "$.:$&"'

1:2018-12-03 00:00


But do you really need to make your regex that complicated? Isn't this enough?



$ echo "$Data" | perl -lne '/d{4}-d{2}-d{2} d{2}:d{2}/ && print "$.:$&"'

1:2018-12-03 00:00





share|improve this answer














Note that your regex wouldn't work even if -o was recognized by your grep implementation. You also need -E to enable extended regular expressions. Assuming you have perl, which you probably do, you can try:



$ Data="Logs/2018-12-03/log.txt:3:2018-12-03 00:00:04,333 452621453 [blah blah blah"

$ echo "$Data" | perl -lne '/[0-9]{4}-(0[1-9]|1[0-2])-(0[1-9]|[1-2][0-9]|3[0-1]) (2[0-3]|[01][0-9]):[0-5][0-9]/ && print "$.:$&"'

1:2018-12-03 00:00


But do you really need to make your regex that complicated? Isn't this enough?



$ echo "$Data" | perl -lne '/d{4}-d{2}-d{2} d{2}:d{2}/ && print "$.:$&"'

1:2018-12-03 00:00






share|improve this answer














share|improve this answer



share|improve this answer








edited Dec 4 at 9:28

























answered Dec 4 at 9:20









terdon♦

127k31245422




127k31245422








  • 1




    Note also that the data in the Data variable is a line produced by grep. This makes me think that the user is first running a grep of some kind to get the lines they want, and then iterating in a shell loop over these lines. This is quite an suboptimal approach to log file parsing.
    – Kusalananda
    Dec 4 at 10:43
















  • 1




    Note also that the data in the Data variable is a line produced by grep. This makes me think that the user is first running a grep of some kind to get the lines they want, and then iterating in a shell loop over these lines. This is quite an suboptimal approach to log file parsing.
    – Kusalananda
    Dec 4 at 10:43










1




1




Note also that the data in the Data variable is a line produced by grep. This makes me think that the user is first running a grep of some kind to get the lines they want, and then iterating in a shell loop over these lines. This is quite an suboptimal approach to log file parsing.
– Kusalananda
Dec 4 at 10:43






Note also that the data in the Data variable is a line produced by grep. This makes me think that the user is first running a grep of some kind to get the lines they want, and then iterating in a shell loop over these lines. This is quite an suboptimal approach to log file parsing.
– Kusalananda
Dec 4 at 10:43




















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.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • 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%2f485850%2fgrep-not-a-recognized-flag-o%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

Bressuire

Image
.mw-parser-output .infobox{border:1px solid #aaa;background-color:#f9f9f9;color:black;margin:.5em 0 .5em 1em;padding:.2em;float:right;clear:right;width:22em;text-align:left;font-size:88%;line-height:1.6em}.mw-parser-output .infobox td,.mw-parser-output .infobox th{vertical-align:top;padding:0 .2em}.mw-parser-output .infobox caption{font-size:larger}.mw-parser-output .infobox.bordered{border-collapse:collapse}.mw-parser-output .infobox.bordered td,.mw-parser-output .infobox.bordered th{border:1px solid #aaa}.mw-parser-output .infobox.bordered .borderless td,.mw-parser-output .infobox.bordered .borderless th{border:0}.mw-parser-output .infobox-showbutton .mw-collapsible-text{color:inherit}.mw-parser-output .infobox.bordered .mergedtoprow td,.mw-parser-output .infobox.bordered .mergedtoprow th{border:0;border-top:1px solid #aaa;border-right:1px solid #aaa}.mw-parser-output .infobox.bordered .mergedrow td,.mw-parser-output .infobox.bordered .mergedrow th{border:0;border-right:1px solid ...
Read more

Cabo Verde

Image
  Nota: Cabo-verdiano redireciona para este artigo. Para a língua falada em Cabo Verde, veja crioulo cabo-verdiano. Para outros significados, veja Cabo Verde (desambiguação). Coordenadas: 14° 55' N 23° 31' O Cabo Verde República de Cabo Verde Bandeira Brasão de Armas Lema: Unidade, Trabalho, Progresso Hino nacional: Cântico da Liberdade Gentílico: cabo-verdiano [ 1 ] Capital Praia 14° 55' N 23° 31' O Cidade mais populosa Praia Língua oficial Português Governo República unitária semipresidencialista [ 2 ]  - Presidente Jorge Carlos Fonseca  - Primeiro-ministro Ulisses Correia e Silva História    - Descoberta 1460   - Independência 00 • de Portugal 5 de Julho de 1975   - Multipartidarismo 13 de Janeiro de 1990  Área    - Total 4 033 km² (146.º)  - Água (%) 0,08 População    - Estimativa para 2017 560 899 [ 3 ] hab. (173.º) ...
Read more

Gyllenstierna

Image
.mw-parser-output .infobox{border:1px solid #aaa;background-color:#f9f9f9;color:black;margin:.5em 0 .5em 1em;padding:.2em;float:right;clear:right;width:22em;text-align:left;font-size:88%;line-height:1.6em}.mw-parser-output .infobox td,.mw-parser-output .infobox th{vertical-align:top;padding:0 .2em}.mw-parser-output .infobox caption{font-size:larger}.mw-parser-output .infobox.bordered{border-collapse:collapse}.mw-parser-output .infobox.bordered td,.mw-parser-output .infobox.bordered th{border:1px solid #aaa}.mw-parser-output .infobox.bordered .borderless td,.mw-parser-output .infobox.bordered .borderless th{border:0}.mw-parser-output .infobox-showbutton .mw-collapsible-text{color:inherit}.mw-parser-output .infobox.bordered .mergedtoprow td,.mw-parser-output .infobox.bordered .mergedtoprow th{border:0;border-top:1px solid #aaa;border-right:1px solid #aaa}.mw-parser-output .infobox.bordered .mergedrow td,.mw-parser-output .infobox.bordered .mergedrow th{border:0;border-right:1px solid ...
Read more