Some network types use longer or shorter addresses, not all of them try to
mimic Ethernet.
For example FireWire uses 64-bit hardware addresses but IP-over-FW extends
it to 128-bit addresses in ARP for technical reasons, and I think it's the
same for Infiniband and IPoIB.
Unfortunately Networkd do
I can't tell more about the IPoIB going down after networkd restart
without additional debugging info. But from the complains, did you try
removing the problematic keys (ipoib is part of netdev, not network.
network has no knowledge of the device type)?
Also are you sure
80:00:02:08:fe:80:00:
I'm not sure if that's related to homectl - it seems that you're trying to
specify User= and Group= within a user service. The whole "systemd --user"
service manager (user@xxx.service) is unprivileged and runs as your user,
so it cannot change its UID anyway or set any supplementary groups except
t
Is it wise to use only `homectl` to manage human users *without* reciprocal
entries in /etc/passwd, /etc/group, or /etc/shadow?
$ systemd-analyze security wireplumber --user
| NAME | Description| Exposure|
| --| -- | --- |
| ❌ Use
On Mon, Jul 29, 2024 at 2:12 PM Mantas Mikulėnas wrote:
>>
>> Furthermore it seems to be necessary to run the service unit itself, too
>> (assuming it must be enabled also, right?)
>
>
> No. The purpose of the timer is to start the service, so starting the service
> manually (or "enabling" it,
On Mon, Jul 29, 2024 at 9:33 AM Windl, Ulrich wrote:
> Hi!
>
>
>
> I tried to use my first systemd timer, but failed: Either I don’t
> understand it correctly, or there is a bug in systemd (228 of SLES12 SP5):
>
> (See also https://unix.stackexchange.com/q/779714/320598)
>
>
>
> It seems it’s not
On Mon, Jul 29, 2024 at 9:33 AM Windl, Ulrich wrote:
>
> Hi!
>
>
>
> I tried to use my first systemd timer, but failed: Either I don’t understand
> it correctly, or there is a bug in systemd (228 of SLES12 SP5):
>
> (See also https://unix.stackexchange.com/q/779714/320598)
>
>
>
> It seems it’s n
