I have a simple application that does provides property table for network
devices (maybe it would be useful for a more complete example somewhere).
The app is more to show how to use sdbus, not to replace network manager.
The next step is to add ethtool statistics. Each type of network device
The libsystemd bus event loop is:
while (e->state != SD_EVENT_FINISHED) {
r = sd_event_run(e, (uint64_t) -1);
But since e->state is changed by another thread it
should be marked volatile to avoid compiler thinking
the state doesn't get changed.
diff --git
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 Tue, 7 Jan 2020 19:11:19 +0100
Lennart Poettering wrote:
> On Di, 07.01.20 09:53, Stephen Hemminger (step...@networkplumber.org) wrote:
>
> > On Tue, 7 Jan 2020 15:01:25 +0100
> > Lennart Poettering wrote:
> >
> > > On Mo, 06.01.20 15:36, Stephen Hemm
About a year ago there was some discussion on having persistent network names
on Hyper-V/Azure. Haiyang did some patches to add an attribute which
could be used by udev to do this. But there are some reluctance because
of how the channel id works.
The motivation to provide network naming is to
On Tue, 7 Jan 2020 15:01:25 +0100
Lennart Poettering wrote:
> On Mo, 06.01.20 15:36, Stephen Hemminger (step...@networkplumber.org) wrote:
>
> > About a year ago there was some discussion on having persistent network
> > names
> > on Hyper-V/Azure. Haiyang did some pat
On Fri, 6 Sep 2019 16:04:33 +0100
Simon McVittie wrote:
> On Fri, 06 Sep 2019 at 06:57:22 +, Ray, Ian (GE Healthcare) wrote:
> > If thread-safety is a design goal (and I don’t believe that it is [1])
> > then atomic or thread-safe primitives should be used.
> >
> > [1]
> >
On Sat, 29 Jan 2022 14:46:52 -0800
Daniel Farina wrote:
> I am using SELinux enforced AlmaLinux, and am wondering where the customary
> place to put a ListenStream directive that is opening a unix socket should
> be.
>
> Old-school customarily, /tmp suffices, but SELinux blocks that: "init_t"
On Fri, 11 Feb 2022 00:57:11 +
Wol wrote:
> I've found the pid0 blog, and had no real trouble (I think, I haven't
> tested it yet :-) converting an xinetd setup.
>
> But the documentation (man systemd.service) didn't tell me how to
> convert a couple of settings, namely xinetd had "user="
On Fri, 11 Feb 2022 01:53:32 +
Wol wrote:
> On 11/02/2022 01:08, Stephen Hemminger wrote:
> > On Fri, 11 Feb 2022 00:57:11 +
> > Wol wrote:
> >
> >> I've found the pid0 blog, and had no real trouble (I think, I haven't
> >> teste
On Mon, 24 Jan 2022 10:33:58 +0800 (CST)
www wrote:
> Hi，
>
>
> When the busctl command is used to call the method corresponding to this
> function, the memory used by the process will increase after 65 ~ 70 times.
> If continue to call, the memory usage will continue to increase.
> Refer
On Thu, 12 May 2022 14:36:44 -0400
Dan Streetman wrote:
> On Thu, May 12, 2022 at 2:27 PM Dan Streetman wrote:
> >
> > On Thu, May 12, 2022 at 1:50 PM Dusty Mabe wrote:
> > >
> > >
> > >
> > > On 5/12/22 13:36, Dan Streetman wrote:
> > > > On Thu, May 12, 2022 at 11:11 AM Thomas Haller
>
On Sun, 21 May 2023 15:32:14 +0530
Virendra Negi wrote:
> It's been over a week I have been chasing this
> https://github.com/rsyslog/rsyslog/issues/5137
>
> I was unsure how to ensure that the systemd (since I was getting nowhere
> with rsyslog) split the message instead of the application
On Wed, 02 Aug 2023 06:39:47 +
Stanislav Angelovič wrote:
> Hi folks,
>
> I have a quick question: is there a way to get container size when
> deserializing an array from a D-Bus message (be it an array of trivial or
> non-trivial D-Bus types)? Say I enter a container with
>
On Wed, 26 Jul 2023 19:17:53 +
"Muggeridge, Matt" wrote:
> > -Original Message-
> > From: Stephen Hemminger
> > Sent: Thursday, July 27, 2023 2:04 AM
> > To: Muggeridge, Matt
> > Cc: systemd-devel@lists.freedesktop.org
> > Subject:
On Wed, 26 Jul 2023 03:23:14 +
"Muggeridge, Matt" wrote:
> Hi,
>
> Recently, we ran a test suite to check networkd's conformance to IPv6
> Protocol (see https://www.ipv6ready.org/resources.html). I found a large
> number of test failures (more than 80) and after examining a small number
On Tue, 12 Dec 2023 03:51:37 +
"Muggeridge, Matt" wrote:
> >
> > If you need these problems fixed so that you can use systemd-networkd in
> > your commercial products, I recommend getting your company to pay
> > developers to fix systemd-networkd.
> > --
> > Sincerely,
> > Demi Marie
17 matches
Mail list logo
