Re: [systemd-devel] Mounting a new device to a mount point with an old (auto-generated) but inactive mount unit triggers an immediate unmount

Hey Mantas, On 08/07/2021 10:39, Mantas Mikulėnas wrote: I am then just wondering why the issue referred to (https://github.com/systemd/systemd/issues/1741 ) is still open? Are there still further plans to make systemd properly

Re: [systemd-devel] Mounting a new device to a mount point with an old (auto-generated) but inactive mount unit triggers an immediate unmount

Hey Silvio, On 07/07/2021 20:04, Silvio Knizek wrote: after touching /etc/fstab you're supposed to run `systemctl daemon- reload` to re-trigger the generators. This is in fact a feature to announce changes in configuration files to systemd. See man:systemd.generator for more information.

[systemd-devel] Mounting a new device to a mount point with an old (auto-generated) but inactive mount unit triggers an immediate unmount

Hello systemd-devel, we recently replaced a broken drive on a server and ran into a strange issue in regards to a mount 1) It started with the old device not being reachable anymore and therefore the crypt setup and mount was just failing: --- cut --- [...] Jul  2 03:41:11

[systemd-devel] systemd-networkd version 241 not setting up tunnel of type GRE with Local=any

Hello systemd-devel, after a recent update to systemd 241 my previously working GRE tunnel does not work anymore: Jun 28 13:58:54 localhost systemd-networkd[637]: mytunnel: vti/ipip/sit/gre/gretap/erspan tunnel without a local IPv4 address configured in /etc/systemd/network/mytunnel.netdev.