<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jul 16, 2015 at 3:19 AM, Tanu Kaskinen <span dir="ltr"><<a href="mailto:tanu.kaskinen@linux.intel.com" target="_blank">tanu.kaskinen@linux.intel.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Mon, 2015-07-13 at 09:22 -0700, Christopher Larson wrote:<br>
><br>
> On Mon, Jul 13, 2015 at 9:17 AM, Pau Espin Pedrol<br>
> <<a href="mailto:pespin.shar@gmail.com">pespin.shar@gmail.com</a>> wrote:<br>
<br>
</span><span class="">> So, pulseaudio is intended to be used as a systemd user<br>
> service, not<br>
> as a systemd system service, and that means it needs to end up<br>
> in<br>
> /usr/lib/systemd/user and not in /lib/systemd/system/.<br>
><br>
> All these changes are part of my efforts to improve systemd<br>
> user<br>
> service support in OE, which is kind of bad nowadays imho.<br>
><br>
> Fair enough, thanks for the clarification. Given that systemd user<br>
> services require pam, and most embedded distros disable pam, I wonder<br>
> if we shouldn’t have an option, at least for daemons in recipes that<br>
> can handle it, to switch from user to system via a PACKAGECONFIG, and<br>
> possibly default that for the non-pam case.. Hmm.<br>
<br>
</span>Do you mean that there are many distros that have systemd but don't have<br>
pam, and that the lack of pam strongly suggests that the system won't<br>
have any regular users? If so, then your proposal sounds good.</blockquote></div><br>No, I mean that systemd user services require pam, as far as I know, because it’s a systemd pam plugin which actually starts and stops the user services. Without that hook, they won’t be run at all.<br>-- <br><div class="gmail_signature">Christopher Larson<br>clarson at kergoth dot com<br>Founder - BitBake, OpenEmbedded, OpenZaurus<br>Maintainer - Tslib<br>Senior Software Engineer, Mentor Graphics</div>
</div></div>