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 --
--
The key to getting good answers is to ask good questions.