On Sat, Nov 4, 2017 at 2:17 PM, Nikos Chantziaras <rea...@gmail.com> wrote: > On 04/11/17 18:15, siefke_lis...@web.de wrote: >> >> I have a short question to systemd. I would like to ask your experience >> in the changeover. Was it easy? Were there problems? >> Change or reinstall? What mean the profis here? > > > I did both. Changed one system to systemd, re-installed one from scratch > with systemd. > > Both worked. The only problem I have with systemd is that it's unable to > reliably restore the ALSA mixer volumes/settings on startup. It fails 50% of > the time. Which is very annoying, but not the end of the world. >
Out of curiosity - are you using alsa-state or alsa-restore? Apparently alsa provides two different ways of preserving state. You might consider switching them (which is triggered by the existence of /etc/alsa/state-daemon.conf - but it might have some other requirements which I didn't bother to check on). I've seen similar issues with iptables-restore. To be fair those are rare and I've also seen issues with that under openrc. With any save/restore tool like these I always keep a copy of the state somewhere where it doesn't get overwritten at shutdown if I have a complex configuration. If you get one of those situations where something isn't detected by the kernel/udev/etc and then your state gets blown away it is really nice to be able to run iptables-restore < backupfile. I believe the way alsa-restore operates is frowned upon in Gentoo systemd circles, though to be honest I'm not sure what the specific concern is. The oneshot/RemainAfterExit approach seems straightforward enough, and it is my guess that it is the upstream way of doing things... -- Rich
