On Mon, 11.08.14 19:48, tomw ([email protected]) wrote:
>
> > This looks weird. You first become user "xyzuser", then you run sudo
> > again, to become "xyzuser"? What's that supposed to do? Why involve
> > "sudo" here at all? You could also use PAMName= directly...?
>
> Thanks for your helpful co
> This looks weird. You first become user "xyzuser", then you run sudo
> again, to become "xyzuser"? What's that supposed to do? Why involve
> "sudo" here at all? You could also use PAMName= directly...?
Thanks for your helpful comments. This setup is intended to boot
directly into an application
On Fri, 08.08.14 10:44, tomw ([email protected]) wrote:
> Hi,
>
> migrating from sysV to systemd I ran into some issues with random
> behavior of session bus availability. The setup is as follows:
>
> systemd starts a service which starts an x-session like this:
>
> [Unit]
> Description=Master P
Hi,
migrating from sysV to systemd I ran into some issues with random
behavior of session bus availability. The setup is as follows:
systemd starts a service which starts an x-session like this:
[Unit]
Description=Master Process
After=systemd-user-sessions.service systemd-udedvd.service dbus.se
