On Sa, 07.07.18 09:09, Rick Beldin (rick.bel...@hpe.com) wrote:
> Hi...
>
> I was trying to understand some systemd-udevd interactions and from source I
> could see that if systemd-udevd was started with --debug option, it would log
> additional items, for example:
>
>
> 786 /*
On Sa, 07.07.18 08:23, Colin Walters (walt...@verbum.org) wrote:
> Came up in this bug:
> https://bugzilla.redhat.com/show_bug.cgi?id=1572944#c44
>
> As far as I can see it never did, but here the entropy is fully trusted;
> seems like using the ioctl would help avoid some entropy fallout
> from
On Sa, 07.07.18 14:35, Michael Biebl (mbi...@gmail.com) wrote:
> 2018-07-06 13:23 GMT+02:00 Lennart Poettering :
> > Yes, Mantas is right, PrivateNetwork= disconnects the whole of
> > AF_NETLINK from the rest of the system, which means services that
> > require libudev device events can't use it.
On 07/07/2018 09:54 AM, Michael Chapman wrote:
> On Sat, 7 Jul 2018, Rick Beldin wrote:
> [...]
>> # systemctl restart systemd-udevd --debug
>> systemctl: unrecognized option '--debug'
>
> You would need to override the service's ExecStart= setting if you wanted
> to do it that way.
>
Ok, so
On Sat, 7 Jul 2018, Rick Beldin wrote:
[...]
> # systemctl restart systemd-udevd --debug
> systemctl: unrecognized option '--debug'
You would need to override the service's ExecStart= setting if you wanted
to do it that way.
> Is there a more supported way of doing this with systemctl for system
Am 07.07.2018 um 14:35 schrieb Michael Biebl:
> Tbh, I find it a bit confusing that we have three mechanisms now
> (PrivateNetwork, RestrictAddressFamilies, IPAddressDeny) and when one
> is supposed to use which one of these.
why
* PrivateNetwork -> big hammer
service needs no network stuff a
Hi...
I was trying to understand some systemd-udevd interactions and from source I
could see that if systemd-udevd was started with --debug option, it would log
additional items, for example:
786 /*
787 * We have partitions but re-reading the partition table
di
2018-07-06 13:23 GMT+02:00 Lennart Poettering :
> Yes, Mantas is right, PrivateNetwork= disconnects the whole of
> AF_NETLINK from the rest of the system, which means services that
> require libudev device events can't use it.
Thank you Lennart and Mantas.
I was indeed not aware that PrivateNetwor
Came up in this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1572944#c44
As far as I can see it never did, but here the entropy is fully trusted;
seems like using the ioctl would help avoid some entropy fallout
from the recent kernel random changes, right?
_
