<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jul 16, 2015 at 11:13 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 Thu, 2015-07-16 at 07:56 -0700, Christopher Larson wrote:<br>
><br>
> On Thu, Jul 16, 2015 at 3:19 AM, Tanu Kaskinen<br>
</span><span class="">> <<a href="mailto:tanu.kaskinen@linux.intel.com">tanu.kaskinen@linux.intel.com</a>> wrote:<br>
> 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>
</span><div><div class="">> > <<a href="mailto:pespin.shar@gmail.com">pespin.shar@gmail.com</a>> wrote:<br>
><br>
> > So, pulseaudio is intended to be used as a systemd<br>
> user<br>
> > service, not<br>
> > as a systemd system service, and that means it needs<br>
> to end up<br>
> > in<br>
> > /usr/lib/systemd/user and not<br>
> in /lib/systemd/system/.<br>
> ><br>
> > All these changes are part of my efforts to improve<br>
> systemd<br>
> > user<br>
> > service support in OE, which is kind of bad nowadays<br>
> imho.<br>
> ><br>
> > Fair enough, thanks for the clarification. Given that<br>
> systemd user<br>
> > services require pam, and most embedded distros disable pam,<br>
> I wonder<br>
> > if we shouldn’t have an option, at least for daemons in<br>
> recipes that<br>
> > can handle it, to switch from user to system via a<br>
> PACKAGECONFIG, and<br>
> > possibly default that for the non-pam case.. Hmm.<br>
><br>
> Do you mean that there are many distros that have systemd but<br>
> don't have<br>
> pam, and that the lack of pam strongly suggests that the<br>
> system won't<br>
> have any regular users? If so, then your proposal sounds good.<br>
><br>
> No, I mean that systemd user services require pam, as far as I know,<br>
> because it’s a systemd pam plugin which actually starts and stops the<br>
> user services. Without that hook, they won’t be run at all.<br>
<br>
</div></div>OK, then it's less clear that services should be run in system mode by<br>
default when pam isn't present. If the lack of pam doesn't imply lack of<br>
regular users, at least pulseaudio should still run as a user service by<br>
default (but not started by systemd if pam isn't enabled).</blockquote></div><br>Running it as a user service by default when it’ll not actually ever be run, lacking a mechanism to run it, seems pretty pointless to me. If someone installs pulseaudio, presumably they want it to actually run.<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>