Re: [systemd-devel] info/request

2016-01-10 Thread Tomasz Torcz
On Sun, Jan 10, 2016 at 02:45:30PM +0200, Moreanu Robert - Nicolae wrote: > how i would resolve this > > user system [474]: Failed at step EXEC spawning /usr/sbin/alsactl: No such > file or directory > - subject: Process /usr/sbin/alsactl could not be executed > - The process /usr/sbin/alsactl

[systemd-devel] info/request

2016-01-10 Thread Moreanu Robert - Nicolae
how i would resolve this user system [474]: Failed at step EXEC spawning /usr/sbin/alsactl: No such file or directory - subject: Process /usr/sbin/alsactl could not be executed - Defined-By: systemd - Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel - - The process

Re: [systemd-devel] user unit blocking login shell from popping out because wanted by default target?

2016-01-10 Thread Tom Yan
That's exactly what I meant. There should be a target for units that "need to be waited" and "no need to be waited" respectively. One can argue which one should a sound service fall into with whatever point, but that's out of the scope of the issue I am talking about here. I just thought systemd

Re: [systemd-devel] user unit blocking login shell from popping out because wanted by default target?

2016-01-10 Thread Tom Yan
Ugh I am not talking about system units, but user units... P.S. Although not really relevant here, but I am using the (user) service file provided by upstream pulseaudio On 11 January 2016 at 01:30, Reindl Harald wrote: > > > Am 10.01.2016 um 18:15 schrieb Mantas

Re: [systemd-devel] user unit blocking login shell from popping out because wanted by default target?

2016-01-10 Thread Reindl Harald
Am 10.01.2016 um 18:42 schrieb Tom Yan: Ugh I am not talking about system units, but user units... P.S. Although not really relevant here, but I am using the (user) service file provided by upstream pulseaudio well, and i am talking about solutions and working setups and yes i know that

Re: [systemd-devel] user unit blocking login shell from popping out because wanted by default target?

2016-01-10 Thread Reindl Harald
Am 10.01.2016 um 18:15 schrieb Mantas Mikulėnas: I remember this discussed before, I think one suggestion was to split into two targets, and only hold the login until the first target. Nobody implemented it though. But yes, pulseaudio.socket would be a requirement of that. If you don't want

Re: [systemd-devel] user unit blocking login shell from popping out because wanted by default target?

2016-01-10 Thread Michał Zegan
The only thing seems to be you cannot go low latency with system mode pulseaudio W dniu 10.01.2016 o 18:53, Reindl Harald pisze: Am 10.01.2016 um 18:42 schrieb Tom Yan: Ugh I am not talking about system units, but user units... P.S. Although not really relevant here, but I am using the

Re: [systemd-devel] user unit blocking login shell from popping out because wanted by default target?

2016-01-10 Thread Ahmed S. Darwish
On Sun, Jan 10, 2016 at 07:08:51PM +0100, Michał Zegan wrote: > > W dniu 10.01.2016 o 18:53, Reindl Harald pisze: > > > > Am 10.01.2016 um 18:42 schrieb Tom Yan: > > > Ugh I am not talking about system units, but user units... > > > > > > P.S. Although not really relevant here, but I am using the