![]() ![]() ![]() I don't particularly want to change my existing answer, which already addresses the fundamental question. I'm posting this as a separate answer in response to your recent edit. (Or you could run xargs on a wrapper which always returns success if the exit code from grep is either 0 or 1, but that is more complex, and you will then see "success" even in the case of zero matches.) which will report success if there was any output. You can reduce the chances by omitting the -n 100 (which hardly seems to serve any useful pupose anyway) but if you want to absolutely prevent it, you can feed the entire pipeline to | grep. The exit code will still be 123 if there are grep invocations which return zero matches. You only have two predicates so there is no need to parenthesize anything, and then the -a can be dropped, too.) (Notice also the much simplified parameters to find. If you want to parametrize the first argument to grep, maybe do something like #!/bin/sh The eval looks superfluous and the double redirection is probably not accomplishing what you want ( grep's standard input cannot simultaneously be connected to the pipe from eval and to. Perhaps you should explain what you are trying to accomplish. So xargs ran grep at least twice (because you fed it so many files that they would exceed the maximum command line length, which you limited to 100 files) and at least one of the invocations was on a set of files which contained no matches, which caused the exit code from grep to be nonzero (failure). ![]() #!/bin/bashĮval ARGV=($(getopt -l '' -o 'e:li' - || exit '"Ĭmd="find \\( -type f -a \\( $find_options \\) \\) -print0"Įval "$cmd" | xargs -0 grep $grep_options -f <(echo "$grep_patterns")ġ23 means "any invocation exited with a non-zero status". The use of the -f option instead of -e is to avoid troubles in escaping single or double quotes within the patterns. Is to execute find -name *.c -o -name *.h | xargs grep -f <(echo "$PATTEN1 For example, xgrep -e PATTERN1 -e PATTERN2. Something is found but the exit code is still 123.Īctually I just want to write a small script to make find+xargs+grep easier. Is that it? is there any way to be sure? I am about to rip it out and double check it but I didn't see anything wrong with it when I cleaned it.Here is my script eval "find \\( -type f -a \\( -name '*.h' \\) \\) -print0" | xargs -0 -n100 grep -f. The salt cell has a S/N of D11GH0251 so if what I've been reading correctly it was replaced in 2011. Is it a bad cell? Is it a bad circuit board? The pool was built in 2007, and I think that all the equipment is original (I bought it in 2015). I can follow directions very well if I know where to begin but at this point I'm lost. Then it would go away, and eventually come back as 194 and 125. I opened the pool up for this season and I immediately got the service warning again w/ the 194 and 125 service codes. So since it was the very end of the season when I started getting the codes I cleaned the cell out (which was dirty) and closed the pool. I figured I was getting the 194 low current, which generated the 125, which was due to the cell being dirty. Since last summer in the NY metro was a lot hotter than normal I had bumped my chlorine production to 85% to maintain balance. So I ordered a new port sensor from Amazon (it came with a new sensor indicator module : Zodiac R0452500 16-Feet Port Sensor with O-Ring Replacement Kit for Select Zodiac Jandy PureLink AquaPure Water Purification System : Swimming Pool Chlorine Alternatives : Patio, Lawn Garden ) and all was good for a little bit.Īt the end of last season I started getting the 125/194 error codes.ġ94Ĝell Current is 85% lower than desired and cell voltage above 19V (Generates 125 code – Cell dirty or needs replacement) I clean my salt cell at the end of every season, and everything was pointing to the sensor that I read online. I believe it was the 125/194 codes (could be wrong on this). Towards the beginning of last season I got some error codes. I'm desperately looking for assistance with my Aquapure 1400 system. Thanks in advance for all replies / help. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |