Timeline for find log files recursively and print "INVALID" if no log found (bash)
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 22, 2018 at 21:35 | history | edited | fra-san | CC BY-SA 4.0 |
Added hint for code highlighting
|
| Nov 29, 2018 at 14:43 | comment | added | fra-san | Well, I meant that: 1) the loop I proposed should find the same files that your original script finds 2) if it yields no results, it probably means that it's not running from the proper path. Are you executing it in the same directory in which you used to execute your original script? Also, is that in your question just a snippet of a bigger script? If so, the rest of it might be influencing our loop (e.g. changing working directory, operating on file descriptors, ...). | |
| Nov 29, 2018 at 13:54 | comment | added | SSDdude | Thx fra-san. it may be the 'expected result' but, it does not work as I need it to. I will mod my script as you suggested and keep trying. Thx! | |
| Nov 29, 2018 at 13:36 | comment | added | fra-san |
This is the expected result if there is no matching file in the current directory and its sub-directories, so it's hard to tell what is going wrong. You could also try your original script, changing only the find line (the whole line). Making a small change at a time might help.
|
|
| Nov 29, 2018 at 13:23 | comment | added | SSDdude | import_Asbeg_DA_Config3_*.log INVALID (and repeat ~750x. | |
| Nov 29, 2018 at 13:21 | comment | added | SSDdude | Hey fra-san thanks for the suggestion. This is returning the correct number of records but it is not letting the wild card find the LATEST log file in those paths. it simply is appending "INVALID" to every line. | |
| Nov 28, 2018 at 15:11 | history | answered | fra-san | CC BY-SA 4.0 |