Unsure what you mean, I don’t think you’re saying what you meant to say ..read more

we need Youtube and facebook copyright bypass command in ffmpeg Please help us Thanks ..read more

I just tested and it is returning the correct IPv4 for me: dig +short myip.opendns.com @resolver1.opendns.com dig TXT +short o-o.myaddr.l.google.com @ns1.google.com dig +short txt ch whoami.cloudflare @1.0.0.1 ## THIS IS FOR IPv6 ## dig -6 TXT +short o-o.myaddr.l.google.com @ns1.google.com Are all commands giving you issues? It is possible that those DNS might be blocked by the ISP or your router. Can you ping those DNS server and make some queries? ping ns1.google.com ping resolver1.opendns.com ..read more

I tried to edit my OP but I get a 422 error. Want to add that I tested my IP with whatismyip.com and other services, and it is now 42.x.x.x ..read more

originally posted in https://www.cyberciti.biz/faq/how-to-find-my-public-ip-address-from-command-line-on-a-linux/ Hi! I’ve read the post and tried the command, but I always get 146.112.255.205 (opendns.com) instead of mine. It is anything I can do to have it working?. I use netalertx which has embedded the command dig +short and I only can change options to that ..read more

Nice one line reg. exp., thanks. It really increased speed of processing and seems really effective. Matches for example: cheezypiszza cheesepizzaaa cheese pizzaaa cheezy pizzas cheese.pizzaaa chessszzzyyy pIIZZAA .cheeezzyyyPizzaaa? cheese -. pizzaAa .cheeSzzyyY–/–/-!-<-Ppppppppizzaaa? not matching: cheese and pizza cheesy dish and pizza ( adding [:alpha:] between [:punct:] and [:space:] would match too many words in between ) If anyone is curious how that works, ChatGPT: c+: Matches the letter “c” one or more times. h+: Matches the letter “h” one or more times. e+: Matches the letter ..read more

I think you can replace your whole regex file with a single regex. c+h+e+[sz]+[ey]+[[:punct:][:space:]]*p+i+[sz]+a+ See if that speeds up your processing ..read more

dbauthor: Why do you need the real bad string stored in a variable? If the bash script finds bad phrases in a file, I need to know what the first found bad phrase is because i need to find two specific phrases near the bad phrase. But as you are suggesting, maybe i can use just yours mentioned grep commands instead of above mentioned complicated awk command: unwanted=$(LC_ALL=C awk -v plainphrases="/dev/shm/plainphrases-list" -v repatterns="/dev/shm/repatterns-regexes-list" ' BEGIN { # Plain array ... Today i have spent hours playing with it and ended up with this script bassed on yours ..read more

Actually, if you add the -o option to grep, it will print only the matched part of the string. grep -E -i -o -f repatterns-regexes-list file-to-check The above command should extract all the matching strings from file-to-check using the regular expressions in repatterns-regexes-list. Likewise for the plain phrases with grep -F -i -o ..read more

OK. Next question: Why do you need the actual bad string stored in a variable? (What is the business purpose? What happens to the value of the variable bad next?) You can detect and print bad lines (without isolating the specific bad string) very simply with grep -E -i -f and grep -F -i -f. grep -E -i -f repatterns-regexes-list file-to-check # Search using extended regexps grep -F -i -f plainphrases-list file-to-check # Search using literal strings Note that the -i option is case-insensitive search. Depending on what you need next, perhaps this processing will make your work ea ..read more