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