Re: I need help with "nmcli device status"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, Aug 01, 2020 at 05:50:58PM -0700, ToddAndMargo via users wrote:
> On 2020-08-01 16:27, Ed Greshko wrote:
> > On 2020-08-02 07:26, Ed Greshko wrote:
> > > On 2020-08-02 07:05, Samuel Sieb wrote:
> > > > On 8/1/20 3:20 PM, Joe Zeff wrote:
> > > > > On 08/01/2020 03:06 PM, ToddAndMargo via users wrote:
> > > > > > Any way around grep and awk or Raku?
> > > > > > 
> > > > > >        $ nmcli device status | grep eno2 | awk '{print $3}'
> > > > > >       connected
> > > > > nmcli device status | grep eno2 | grep connected
> > > > > 
> > > > > This will either return connected, or a blank line, without using awk or any other string manipulation.
> > > > Or even easier, you can send the output to null and check the exit code.
> > > > if nmcli device status | grep eno2 | grep connected > /dev/null; then
> > > >    # connected
> > > > else
> > > >    # not connected
> > > > fi
> > > > 
> > > Actually, doesn't one have to be a bit more careful with the pattern?
> > > 
> > > Notice what the status is for wlp4s0.
> > > 
> > > [egreshko@meimei ~]$ if nmcli device status | grep wlp4s0 | grep connected > /dev/null; then echo connected; else echo not connected; fi
> > > connected
> > > 
> > > oops...
> > > 
> > 
> > Forgot to include...
> > 
> > [egreshko@meimei ~]$ nmcli device status
> > DEVICE             TYPE      STATE         CONNECTION
> > enp2s0             ethernet  connected     enp2s0
> > virbr0             bridge    connected     virbr0
> > vnet0              tun       connected     vnet0
> > 78:00:9E:27:6B:3D  bt        disconnected  --
> > wlp4s0             wifi      disconnected  --
> > lo                 loopback  unmanaged     --
> > virbr0-nic         tun       unmanaged     --
> > 
> 
> Ah poop!  "disconnected" contains "connected"!

if nmcli device status | grep -E "^eno2 +.* +connected " > /dev/null
then
  # connected
else
  # not connected
fi

jon
-- 
Jon H. LaBadie                  jonfu@xxxxxxxxxx
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux