- Registriert
- 19 Jan. 2012
- Beiträge
- 434
Folge dem Video um zu sehen, wie unsere Website als Web-App auf dem Startbildschirm installiert werden kann.
Anmerkung: Diese Funktion ist in einigen Browsern möglicherweise nicht verfügbar.
if_up_strictness = 'address',
${if_up enp2s0}
${color}eth0 up: ${alignr}${color3} ${upspeed enp2s0}
${color}${alignr}${upspeedgraph enp2s0 20,170 144556 144556}
${color}eth0 down: ${alignr}${color3} ${downspeed enp2s0}
${color2}${alignr}${downspeedgraph enp2s0 20,170 144556 144556}${endif}${if_up eth1}
${color}eth1 up: ${alignr}${color3} ${upspeed eth1}
${color}${alignr}${upspeedgraph eth1 20,170 5599cc 5599cc}
${color}eth1 down: ${alignr}${color3} ${downspeed eth1}
${color2}${alignr}${downspeedgraph eth1 20,170 5599cc 5599cc}${endif}${if_up wlan0}
${color}wlan0 up: ${alignr}${color3} ${upspeed wlan0}
${color2}${alignr}${upspeedgraph wlan0 20,170 5599cc 5599cc}
${color}wlan0 down: ${alignr}${color3} ${downspeed wlan0}
${color2}${alignr}${downspeedgraph wlan0 20,170 5599cc 5599cc}${endif}${if_up wlan1}
${color}wlan1 up: ${alignr}${color3} ${upspeed wlan1}
${color2}${alignr}${upspeedgraph wlan1 20,170 5599cc 5599cc}
${color}wlan1 down: ${alignr}${color3} ${downspeed wlan1}
${color2}${alignr}${downspeedgraph wlan1 20,170 5599cc 5599cc}${endif}
Diese Datei gibt es nicht.Nimm den Texteditor deines Vertrauens und öffne ~/.conkyrc
# Network
#----------------------------------------------------------------------------------------------------------------------------------------
${color1}${voffset 2}${hr 1}
${color1}${voffset 5}Hostname: $color$alignr$nodename
${if_up ${template7}}${template0 ${template7}}${else}${template0 ${template6}}${endif}
${if_up ${template5} }${template1 ${template5} }${else}${template1 ${template4} }${endif}
${if_up ${template7}}${template2 ${template7}}${else}${if_up ${template6}}${template2 ${template6}}${else}${if_up ${template5}}${template2 ${template5}}${else}${if_up ${template4}}${template2 ${template4}}${else}${template2 no-link} ${endif}${endif}${endif}${endif}
... und mit der Konsoleneingabe >> netstat -i -n << erfährst du die Namen deiner Schnittstellen
Hier gab es schon den einen oder anderen Post zu conky.
Wenn du danach suchst, kannst du vllt. etwas für dich editieren.
$ netstat -i -n
Kernel-Schnittstellentabelle
Iface MTU RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP TX-OVR Flg
eth0 1500 0 0 0 0 0 0 0 0 BMU
lo 65536 42 0 0 0 42 0 0 0 LRU
wlan0 1500 7346 0 0 0 4213 0 0 0 BMRU
$ inxi -nxxx
Network:
Device-1: Intel 82566MM Gigabit Network vendor: Lenovo driver: e1000e
v: 3.2.6-k port: 1840 bus ID: 00:19.0 chip ID: 8086:1049
IF: eth0 state: down mac: 00:16:d3:cc:f8:f1
Device-2: Broadcom Limited BCM4322 802.11a/b/g/n Wireless LAN
vendor: Hewlett-Packard driver: wl v: kernel port: 1c40
bus ID: 03:00.0 chip ID: 14e4:432b
IF: wlan0 state: up mac: 00:21:00:53:5d:c3
IF-ID-1: wwan0 state: down mac: 2a:25:9a:0c:47:fe
0: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
2: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
$ lsusb
Bus 002 Device 002: ID 1199:68a2 Sierra Wireless, Inc.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 062a:4182 MosArt Semiconductor Corp.
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 003: ID 0483:2016 STMicroelectronics Fingerprint Reader
Bus 003 Device 002: ID 0a5c:2110 Broadcom Corp. BCM2045B (BDC-2) [Bluetooth Controller]
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
$ nmcli dev
DEVICE TYPE STATE CONNECTION
wlan0 wifi verbunden BlubBlub
cdc-wdm0 gsm nicht verbunden --
eth0 ethernet nicht verfügbar --
lo loopback nicht verwaltet --
$ inxi -nxxx
Network:
Device-1: Intel 82566MM Gigabit Network vendor: Lenovo driver: e1000e
v: 3.2.6-k port: 1840 bus ID: 00:19.0 chip ID: 8086:1049
IF: eth0 state: down mac: 00:16:d3:cc:f8:f1
Device-2: Broadcom Limited BCM4322 802.11a/b/g/n Wireless LAN
vendor: Hewlett-Packard driver: wl v: kernel port: 1c40
bus ID: 03:00.0 chip ID: 14e4:432b
IF: wlan0 state: dormant mac: 00:21:00:53:5d:c3
IF-ID-1: wwan0 state: unknown mac: 0a:16:73:5d:b7:f7
$ rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
2: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
3: hci1: Bluetooth
Soft blocked: no
Hard blocked: no
$ lsusb
Bus 004 Device 003: ID 1199:68a2 Sierra Wireless, Inc.
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 002: ID 062a:4182 MosArt Semiconductor Corp.
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 0a5c:2101 Broadcom Corp. BCM2045 Bluetooth
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 0483:2016 STMicroelectronics Fingerprint Reader
Bus 001 Device 002: ID 0a5c:2110 Broadcom Corp. BCM2045B (BDC-2) [Bluetooth Controller]
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
$ nmcli dev
DEVICE TYPE STATE CONNECTION
cdc-wdm1 gsm verbunden MedionMobile
wlan0 wifi nicht verbunden --
eth0 ethernet nicht verfügbar --
lo loopback nicht verwaltet --