On Do, 17.10.19 10:23, Stephen Hemminger (step...@networkplumber.org) wrote:
> Ethernet flow control (pause) is a setting which often is best disabled.
> Systemd has nice way to configure other link settings like WoL, TSO, etc
> but doesn't have a way to configure pause.
>
> It would be good to
Ethernet flow control (pause) is a setting which often is best disabled.
Systemd has nice way to configure other link settings like WoL, TSO, etc
but doesn't have a way to configure pause.
It would be good to have something like:
[Match]
Driver=ixgbe
[Link]
Pause=off
Possible values should
On Thu, Oct 17, 2019 at 4:55 PM Martin Townsend wrote:
>
> Hi,
>
> Does systemd support the networkd DHCP Server on multiple network
> interfaces. I ask as we have an embedded system running systemd 239
> and we want to configure a DHCP server on a bluetooth PAN and one of
> the Ethernet
Am 17.10.19 um 17:55 schrieb Martin Townsend:
> Does systemd support the networkd DHCP Server on multiple network
> interfaces. I ask as we have an embedded system running systemd 239
> and we want to configure a DHCP server on a bluetooth PAN and one of
> the Ethernet interfaces both of which
Hi,
Does systemd support the networkd DHCP Server on multiple network
interfaces. I ask as we have an embedded system running systemd 239
and we want to configure a DHCP server on a bluetooth PAN and one of
the Ethernet interfaces both of which are used for configuring the
device.
I've set up
Dear systemd folks,
I couldn’t find a simple documentation for “normal” users how
to use systemd timers instead of cron/crontab? The Arch Wiki
has a page [1], but I am afraid it’s still too complicated
for our users.
Kind regards,
Paul
[1]:
Am 17.10.19 um 08:02 schrieb Ulrich Windl:
>> Or did I miss something and the second flock somehow obtains the inode
>> number of the old lock?
>
> I guess any new process arriving late cannot aquire the (same) lock once the
> first process has removed the name when the crowd has finished.
>
>>> Alexander Koch schrieb am 16.10.2019 um 16:14 in
Nachricht <9fb9c1a157e92baef1107ed3b66aa...@alexanderkoch.net>:
> * flock leaves the lock file behind so you'd need some type of
> cleanup in case you really want the jobs to be trace‑free. This is
> not as trivial is it might seem,
