Re: [systemd-devel] syscvall-filters killing CGI after update to Fedora 33

2021-04-21 Thread Dan Nicholson
On Mon, Apr 19, 2021 at 10:24 AM Reindl Harald wrote: > > after a long time using this SystemCallFilter perl-cgi with Fedora 33 > get killed - anyone an idea what changed that's obviously covered by the > second line > > SystemCallFilter=@system-service @network-io @privileged > SystemCallFilter=~

Re: [systemd-devel] RFC: one more time: SCSI device identification

2021-04-21 Thread Martin K. Petersen
Martin, > Hm, it sounds intriguing, but it has issues in its own right. For > years to come, user space will have to probe whether these attribute > exist, and fall back to the current ones ("wwid", "vpd_pg83") > otherwise. So user space can't be simplified any time soon. Speaking > for an impor

[systemd-devel] resolved: wrong address w/ cache off, wo/ querying DNS server

2021-04-21 Thread Dénes Türei
Dear Systemd Developers, I got stuck with investigating an issue and I would be very grateful for some advice. Briefly, systemd-resolved keeps returning a wrong answer to a query, despite the cache is disabled. The debug log doesn't show the origin of the answer. Systemd-resolved doesn't query the

Re: [systemd-devel] "Correct" way to obtain DHCP lease info?

2021-04-21 Thread Silvio Knizek
Am Mittwoch, dem 21.04.2021 um 14:24 -0400 schrieb Bruce A. Johnson: > Is there a correct way to obtain information about the DHCP lease > received by systemd-networkd's DHCP client functionality? It was easy > enough to find SERVER_ADDRESS in /var/run/systemd/netif/leases/4, but > there is a bi

[systemd-devel] "Correct" way to obtain DHCP lease info?

2021-04-21 Thread Bruce A. Johnson
Is there a correct way to obtain information about the DHCP lease received by systemd-networkd's DHCP client functionality? It was easy enough to find SERVER_ADDRESS in /var/run/systemd/netif/leases/4, but there is a big fat warning stamped at the top of the file: # This is private data. Do n

Re: [systemd-devel] Request for Feedback on Design Issue with Systemd and "Consistent Network Device Naming"

2021-04-21 Thread Lennart Poettering
On Mi, 21.04.21 10:13, Simon Foley (si...@simonfoley.net) wrote: > The issue is around the depreciation of the support for the HWADDR= argument > in the ifcfg files (RHEL, other distros are available). systemd upstream is not involved in that. ifcfg is specific to Red Hat distributions and system

Re: [systemd-devel] Request for Feedback on Design Issue with Systemd and "Consistent Network Device Naming"

2021-04-21 Thread Andrei Borzenkov
On Wed, Apr 21, 2021 at 12:20 PM Simon Foley wrote: ... > Here we can use the HWADDR= variable in the ifcfg-[device name] files to > move a *specific* device name to these targeted NIC cards and ports. Read man systemd.link. [Match] MACAddress= (or PermanentMACAddress=) [Link] Name=whatever-nam