Re: [systemd-devel] Not able to start Weston dependent application

2018-10-31 Thread Lennart Poettering
added that dependency. > > App2 is started but app1 not able to find that dependency. Iam getting > error as not able to find weston. > > If I start both manually, it's working fine. Does app2 have the right Type= set so that systemd actually knows when the service is pr

Re: [systemd-devel] [PATCH weston] doc/systemd: system service example

2017-12-01 Thread Lennart Poettering
figure only the bits you need. > > > > > > > Oh, so could it just be that we needed something other than > > "PAMName=login"? > > What are they key bits in the PAM configuration we must have, and are > there any often used bits we must not

Re: [systemd-devel] [PATCH weston] doc/systemd: system service example

2017-11-30 Thread Lennart Poettering
, it must be logind that starts it for you at the right moment. If you do anyway, XDG_RUNTIME_DIR won't be set, and things fall apart. We should fix that though... Lennart -- Lennart Poettering, Red Hat ___ wayland-devel mailing list waylan

Re: [systemd-devel] [PATCH weston] doc/systemd: system service example

2017-11-30 Thread Lennart Poettering
tros. Sorry. The distros even patch PAM differently, so that slightly difference constructs are available... Lennart -- Lennart Poettering, Red Hat ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel

Re: [systemd-devel] [PATCH weston] doc/systemd: system service example

2017-11-30 Thread Lennart Poettering
ope. > +# Set up a full user session for the user, required by Weston. > +PAMName=login Piggy-backing on "login" is a bad idea. "login" is a text tool, and thus the PAM rules for it usually pull in some TTY specific PAM modules. YOu shoudl really use your own PAM fragm