Am 04.07.2014 14:21, schrieb VALETTE Eric OLNC/OLPS: > I continued my slow but constant march on systemd migration at home and > I'm now sure the things are a bit more complex than *only* > CONFIG_FHANDLE stuff I had at work. The good point is that two more > machines were fixed by regenerating a kernel so it was clearly a kernel > configuration <<bug>> (kernel was correctly configured for sysv init but > not systemd...) on my side BUT I had two computers were I had the > pulseaudio symptom, and were the only kernel compilation flags I > changed were (unless my wife give me drugs without telling) > CONFIG_SECCOMP and CONFIG_NET_NS (and I have no clue why they are needed > by systemd. Education appreciated).
seccomp filters [1] are an (optional) feature of systemd.
See the README files:
Optional but strongly recommended:
CONFIG_SECCOMP
As for CONFIG_NET_NS:
Required for PrivateNetwork in service units:
CONFIG_NET_NS
rtkit-daemon seems to use this feature:
/lib/systemd/system/rtkit-daemon.service:PrivateNetwork=yes
I guess we are getting closer to the problem.
[1] http://lwn.net/Articles/507067/
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
