I just installed the new-to-EPEL ndppd service and am seeing this in my log:
Oct 17 21:10:08 saruman systemd: Can't open PID file
/var/run/ndppd/ndppd.pid (yet?) after start: No such file or directory
Examining the source, I see that the pidfile is created by the child
process, not the
Am Montag, dem 18.10.2021 um 12:43 -0700 schrieb Kenneth Porter:
> I just installed the new-to-EPEL ndppd service and am seeing this in my log:
>
> Oct 17 21:10:08 saruman systemd: Can't open PID file
> /var/run/ndppd/ndppd.pid (yet?) after start: No such file or directory
>
> Examining the
On 18.10.2021 23:08, Silvio Knizek wrote:
> Am Montag, dem 18.10.2021 um 12:43 -0700 schrieb Kenneth Porter:
>> I just installed the new-to-EPEL ndppd service and am seeing this in my log:
>>
>> Oct 17 21:10:08 saruman systemd: Can't open PID file
>> /var/run/ndppd/ndppd.pid (yet?) after start: No
On 10/18/2021 1:08 PM, Silvio Knizek wrote:
OTOH, systemd-networkd itself has inbuilt NDPProxy capabilities.
How well does it coexist with RHEL/CentOS 7? I don't really understand
how the various network management ecosystems interact. Pointers welcome.
On Mon, Oct 18, 2021 at 4:44 PM Kenneth Porter wrote:
>
> I just installed the new-to-EPEL ndppd service and am seeing this in my log:
>
> Oct 17 21:10:08 saruman systemd: Can't open PID file
> /var/run/ndppd/ndppd.pid (yet?) after start: No such file or directory
>
> Examining the source, I see
On Mi, 13.10.21 13:38, Umut Tezduyar Lindskog (umut.tezdu...@axis.com) wrote:
> Hi, we have been playing around more with the portable services and
> lots of loose thoughts came up. Hopefully we can initiate
> discussions.
>
> The PrivateUsers and DynamicUsers are turned off for the trusted
>
