shell script to change directory to the tail result path

Question

I'm using Tail to an error happen on the log lines like: and this gives results like: So what I do manually is to change the path using cd: Is there any script to change directory automatically? As I run another manual script to change file names for the files contained in /003217899/, those like /003217899/ are happening many times

Accepted Answer

Script modified again for additional requirements.(As I did not get answers to all questions I modified the script based on the incomplete information.)Instead of processing two directories separately the script now uses find in the parent directory (or the only directory), renames and touches all files that contain a &#8216;?&#8217; in the name. (-name '*?*').#! /bin/bash# Two possible variants because the question was modified.## To process the complete input file as it is now#  fgrep "ERROR processEvent: /mnt/docs/"  syschecklog.log | ...## To continuously follow the file# tail -f syschecklog.log| fgrep "ERROR processEvent: /mnt/docs/" | ... # The "LANG=C sed ..." avoids problems with invalid UTF-8 characters that do not match '.' in sed's patternfgrep "ERROR processEvent: /mnt/docs/"  syschecklog.log | LANG=C sed 's#.*ERROR processEvent: (/mnt/docs/[^/]*)/.*#1#' | while IFS= read -r DIRdo    find "$DIR" -name '*?*' | while IFS= read -r FILE    do        NEW=$(echo "$FILE"| tr '?' $'xBF')        mv "$FILE" "$NEW"        touch "$NEW"    donedoneNote that grep and sed will switch to buffered output when used in a pipeline. This will delay the processing of the extracted lines. You might have to disable buffering for the commands in the pipeline, see http://mywiki.wooledge.org/BashFAQ/009 2nd major updateThere was a problem with invalid characters. In a UTF-8 environment sed behaves strangely when the input contains bytes that are not valid UTF-8 charactes. The pattern . does not match these invalid characters. (The example file contains a byte with the value 0xBF. See http://www.linuxproblem.org/art_21.html. Setting LANG=C for the sed command fixes this problem. I tested my script with the grep output added to the question. I wrote this into a file somelog.log. I modified my script to use grep pattern somelog.log | ... with a local file instead of using a log file with a full path which does not exist on my test system.After adding LANG=C to the sed command the script ran successfully with the raw input file provided as an external link.The output is$ grep "ERROR processEvent: /mnt/docs/"  syschecklog.log | sed 's#.*ERROR processEvent: (/.*)/.*#1#' | while read -r DIR; do     BASEDIR=${DIR%/*};     if [ "$BASEDIR" != /mnt/docs/ ];     then         ( cd "$BASEDIR" && renameFiles);     fi;     ( cd "$DIR" && renameFiles); donebash: cd: /mnt/docs/001234567: No such file or directorybash: cd: /mnt/docs/001234567/Subdir9876543: No such file or directorybash: cd: /mnt/docs/002345678: No such file or directorybash: cd: /mnt/docs/003456789: No such file or directorybash: cd: /mnt/docs/003456789/Subdir8765432: No such file or directory... (more similar lines removed)You can see that it tried to cd into the directories from the log messages. It does not show parts of the file name. In my case it simply failed because the directories don&#8217;t exist. I think the script should work.After replacing the two cd and renameFiles commands with find&#8230; the output with my test isfind: ‘/mnt/docs/001234567’: No such file or directoryfind: ‘/mnt/docs/002345678’: No such file or directoryfind: ‘/mnt/docs/003456789’: No such file or directory...

Advertisement

Answer