Hi, let me start by expressing my gratitude for creating/offering this excellent application. Have been using it without hiccups for a long time. But after my Arch Linux box got the systemd v254 recently, I did notice some peculiarity. Where before this upgrade swapon consistently reported /dev/zram0, it now shows /zram0 instead.
UPDATE:
After doing some more experimenting it turned out we can keep PrivateNetwork and explicitly disable PrivateMounts.
Nothing crucial apparently, the zram device is created and still resides under /dev/zram0. But it's confusing and I opted to disable PrivateNetworkPrivateMounts to get back to the output one would expect from swapon.
$ cat /etc/systemd/system/zramd.service.d/fix-swapon-output.conf
[Service]
# systemd v254 introduced some changes that apparently affected
# swapon output - bring back known good behaviour
# https://github.com/systemd/systemd/commit/6b2d576f2b38c0385bb056af328754ec8966f9fd
PrivateMounts=no
Not sure whether there might be better ways to deal with this systemd change. I'll leave that up to you.
Hi, let me start by expressing my gratitude for creating/offering this excellent application. Have been using it without hiccups for a long time. But after my Arch Linux box got the systemd v254 recently, I did notice some peculiarity. Where before this upgrade
swaponconsistently reported /dev/zram0, it now shows /zram0 instead.UPDATE: After doing some more experimenting it turned out we can keep
PrivateNetworkand explicitly disablePrivateMounts.Nothing crucial apparently, the zram device is created and still resides under /dev/zram0. But it's confusing and I opted to disable
PrivateNetworkPrivateMountsto get back to the output one would expect from swapon.https://github.com/maximumadmin/zramd/blob/a21eb478ee91974d57abf164508f1c991ae80044/build/package/zramd.service#L11
Not sure whether there might be better ways to deal with this systemd change. I'll leave that up to you.