At boot, zramen complains it cannot use its log file because of a readonly filesystem.
After boot, it starts and run just fine, so I guess it is started too early in the boot process.
How could this be fixed ? May be a waits-for or depends-on directive in /etc/dinit.d/zramen ?
Edit its init service file to start after 'logger'.
In my case, it would probably be metalog.
Thanks!
No, logger it is. Service files offer a provide keyword which allows "competing" daemons to satisfy the same dependency. Examples: logger for metalog and syslog-ng, net for dhcpcd, connman and networkmanager, cron for cronie and fcron. You can of course use the real service name if you want to be explicit, but the former solution safeguards from conflicts.
It makes sense, but adding a 'waits-for = logger' brings a failed boot (which is strange in itself, why
aborting the boot process for a non-critical service ?).
So, I had to remove the logger line in /etc/dinit.d/zramen in recovery mode.
A 'grep provide' in /etc/dinit.d gives nothing, I'm starting to wonder if there's something missing
in the dinit directory.
Oh, I was talking about openrc, I don't know if the dinit service files for loggers have the 'provides' functionality.
Every service that has logfile should have dependency on read-write rootfs. Add this to service file:
depends-on: early-root-rw.target
And it should be fixed.
If zramem-dinit is a official Artix package and has this problem, this is a bug and should be reported to get fixed.
solved, thank you!
I'll gladly report it, what is the correct way to do it ?
(I don't have a gitea or a bugs.archlinux.org account to report there)
@konimex Can you fix this in repo? Thanks
Unfortunately I don't maintain zramen-dinit.
@ndowens seems to be the last packager since I can't find it in our gitea at all.