14.06.2019 17:13, Germano Massullo пишет:
> I have two different options at the moment, and I would like to ask
> you for a feedback.
>
>
> A file
>
> /usr/lib/udev/rules.d/01-boinc-gpu-plugged.rules
>
> containing
>
> ACTION=="add", SUBSYSTEM=="drm", RUN+=systemctl --no-block restart
> boinc-
Am 14.06.19 um 17:07 schrieb Dorian ROSSE:
> Hello, *[list of programs broken : (1) netword-dispatcher , (2) udisks2
> , (3) thermald , (4) ModemManager , (5) systemd-logind , (6)
> avahi-daemon , (7) wpa_supplicant , (8) accounts-daemon , (9) lxc-net ,
> (10) ctdb , (11) dnsmasq , (12) apa
Hello, [list of programs broken : (1) netword-dispatcher , (2) udisks2 , (3)
thermald , (4) ModemManager , (5) systemd-logind , (6) avahi-daemon , (7)
wpa_supplicant , (8) accounts-daemon , (9) lxc-net , (10) ctdb , (11) dnsmasq
, (12) apache2 , (13) NetworkManager ,
I was launch a fast
Hi
On 6/13/19 2:44 PM, Bruce A. Johnson wrote:
We recently decided to add a Wi-Fi interface as an
option to the Ethernet interface, and it was easy enough to set up
wpa_supplicant to handle connecting the lower layer, after which
systemd-networkd uses the .network file to bring up IP, either usi
I have two different options at the moment, and I would like to ask
you for a feedback.
A file
/usr/lib/udev/rules.d/01-boinc-gpu-plugged.rules
containing
ACTION=="add", SUBSYSTEM=="drm", RUN+=systemctl --no-block restart
boinc-client.service
should restart BOINC client when a new DRM device
