Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #247274

Re: disable IPv6 debian

Show all headers | View raw

On Fri, Apr 15, 2022 at 09:47:11PM -0400, The Wanderer wrote:
> On 2022-04-15 at 20:47, Greg Wooledge wrote:
> > On Sat, Apr 16, 2022 at 08:20:40AM +0800, wilson wrote:
> 
> >> ps -efw |grep $PS |grep -v grep
> 
> > You're also going to exit your script with the exit status from that
> > last grep command.  That's probably not what you want.  If it's not,
> > then an explicit "exit 0" at the end might be a good idea.
> > 
> > Or, as another choice, you might want to exit with the exit status
> > of the *first* grep.  In that case, switching them around would be
> > better:
> > 
> > ps -efw | grep -v grep | grep "$PS"
> 
> This would probably result in undesired behavior. I recognize this
> pattern; for reasons that I don't entirely grasp but which seem somehow
> intuitive to me, invoking ps in any of the ways that I've yet found
> useful and piping the output to grep will result in that grep process -
> with its arguments - being listed in the ps output.
> 
> Because the string you're grepping for is included in that argument
> list, that line will be matched, and so will be printed.
> 
> In order to avoid that, the obvious thing to do is just append ' | grep
> -v grep' to the pipeline, so that the unwanted result line gets stripped
> out. I've used that pattern many times.
> 
> IOW: Having the "cut out any lines that mention the command that got the
> search pattern passed to it" command come last is likely to be a necessity.

Your conclusion is not correct.

foobar | grep b | grep -v c

foobar | grep -v c | grep b

both give the same lines of output.  The difference is that the exit
status of the pipeline is that of the last command in the pipeline.

If you go with the first command, you end up with the exit status of
"grep -v c".  When c is grep, and this filter is being used to suppress
the extra race-conditional output of a "grep" command from the process
list (which may not be there), the resulting exit status will be
unpredictable.

With the second command, the exit status will be 0 (success) if there is
at least one matching "b" in the output, and 1 (failure) if not.

Of course, if you put "exit 0" after it, then it doesn't matter.

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

disable IPv6 debian wilson <info@bigcount.xyz> - 2022-04-15 13:50 +0200
  Re: disable IPv6 debian 황병희 <soyeomul@doraji.xyz> - 2022-04-15 14:00 +0200
    Re: disable IPv6 debian wilson <info@bigcount.xyz> - 2022-04-15 14:30 +0200
      Re: disable IPv6 debian Greg Wooledge <greg@wooledge.org> - 2022-04-15 17:00 +0200
        Re: disable IPv6 debian Greg Wooledge <greg@wooledge.org> - 2022-04-15 18:00 +0200
          Re: disable IPv6 debian Tim Woodall <debianuser@woodall.me.uk> - 2022-04-15 18:10 +0200
        Re: disable IPv6 debian wilson <info@bigcount.xyz> - 2022-04-16 02:10 +0200
          Re: disable IPv6 debian Greg Wooledge <greg@wooledge.org> - 2022-04-16 02:20 +0200
            Re: disable IPv6 debian wilson <info@bigcount.xyz> - 2022-04-16 02:30 +0200
              Re: disable IPv6 debian Charles Curley <charlescurley@charlescurley.com> - 2022-04-16 02:40 +0200
              Re: disable IPv6 debian Greg Wooledge <greg@wooledge.org> - 2022-04-16 02:50 +0200
                Re: disable IPv6 debian wilson <info@bigcount.xyz> - 2022-04-16 03:10 +0200
                Re: disable IPv6 debian The Wanderer <wanderer@fastmail.fm> - 2022-04-16 03:50 +0200
                Re: disable IPv6 debian wilson <info@bigcount.xyz> - 2022-04-16 04:10 +0200
                Re: disable IPv6 debian Greg Wooledge <greg@wooledge.org> - 2022-04-16 05:00 +0200
                Re: disable IPv6 debian The Wanderer <wanderer@fastmail.fm> - 2022-04-16 14:10 +0200
                Re: disable IPv6 debian Greg Wooledge <greg@wooledge.org> - 2022-04-16 15:10 +0200
                Re: disable IPv6 debian David Wright <deblis@lionunicorn.co.uk> - 2022-04-16 18:10 +0200
                Re: disable IPv6 debian <tomas@tuxteam.de> - 2022-04-16 08:20 +0200
                Re: disable IPv6 debian Tim Woodall <debianuser@woodall.me.uk> - 2022-04-16 08:40 +0200
                Re: disable IPv6 debian wilson <info@bigcount.xyz> - 2022-04-16 10:30 +0200
                Re: disable IPv6 debian David <bouncingcats@gmail.com> - 2022-04-16 10:50 +0200
                Re: disable IPv6 debian Greg Wooledge <greg@wooledge.org> - 2022-04-16 15:00 +0200
            Re: disable IPv6 debian Michael Stone <mstone@debian.org> - 2022-04-16 20:00 +0200
          Re: disable IPv6 debian <tomas@tuxteam.de> - 2022-04-16 08:20 +0200
      Re: disable IPv6 debian Chuck Zmudzinski <brchuckz@netscape.net> - 2022-04-15 19:40 +0200
      Re: disable IPv6 debian Andy Smith <andy@strugglers.net> - 2022-04-16 01:00 +0200
        Re: disable IPv6 debian didar <nosferatu@purlo.in> - 2022-04-16 07:10 +0200
          Re: disable IPv6 debian Andy Smith <andy@strugglers.net> - 2022-04-16 11:50 +0200
  Re: disable IPv6 debian Reco <recoverym4n@enotuniq.net> - 2022-04-15 14:30 +0200
    Re: disable IPv6 debian wilson <info@bigcount.xyz> - 2022-04-15 14:40 +0200
      Re: disable IPv6 debian Erwan David <erwan@rail.eu.org> - 2022-04-15 16:00 +0200
        Re: disable IPv6 debian Jeremy Ardley <jeremy@ardley.org> - 2022-04-15 16:20 +0200
      Re: disable IPv6 debian Reco <recoverym4n@enotuniq.net> - 2022-04-15 16:20 +0200
  Re: disable IPv6 debian wilson <info@bigcount.xyz> - 2022-04-16 02:20 +0200
  Re: disable IPv6 debian Ash Joubert <ash@transient.nz> - 2022-04-16 02:20 +0200

csiph-web