On Tue, 28 Nov 2017 12:14:29 +0200
Pekka Paalanen wrote:
> From: Pekka Paalanen
>
> There are many bad and even worse attempts to make Weston run as a
> systemd service, and very few good ones. Let's add a good one as an
> example in upstream: does not use weston-launch, does not run weston as
On Mon, Jan 22, 2018 at 7:49 AM, Pekka Paalanen wrote:
> On Fri, 29 Dec 2017 15:09:28 -0600
> Matt Hoosier wrote:
>
>> Hi Lennart,
>>
>> On Mon, Dec 4, 2017 at 9:11 AM, Pekka Paalanen wrote:
>> > On Fri, 1 Dec 2017 18:25:35 +0100
>> > Lennart Poettering wrote:
>> >
>
>> >> So, as long as weston
On Fri, 29 Dec 2017 15:09:28 -0600
Matt Hoosier wrote:
> Hi Lennart,
>
> On Mon, Dec 4, 2017 at 9:11 AM, Pekka Paalanen wrote:
> > On Fri, 1 Dec 2017 18:25:35 +0100
> > Lennart Poettering wrote:
> >
> >> So, as long as weston runs from a PAM enabled service (and its PAM
> >> snippet pulls i
On Fri, Dec 29, 2017 at 11:09 PM, Matt Hoosier
wrote:
>
> The approach that you and Pekka most recently put on record here:
>
> * User=foo
> * PAMName=weston
>
> with a /etc/pam.d/weston that just does minimal stuff (enforce the
> account exists and then execute pam_systemd.so for the session pha
On Dec 29, 2017 15:32, "Mantas Mikulėnas" wrote:
On Fri, Dec 29, 2017 at 11:09 PM, Matt Hoosier
wrote:
>
> The approach that you and Pekka most recently put on record here:
>
> * User=foo
> * PAMName=weston
>
> with a /etc/pam.d/weston that just does minimal stuff (enforce the
> account exists
Hi Lennart,
On Mon, Dec 4, 2017 at 9:11 AM, Pekka Paalanen wrote:
> On Fri, 1 Dec 2017 18:25:35 +0100
> Lennart Poettering wrote:
>
>> On Fr, 01.12.17 13:42, Pekka Paalanen (ppaala...@gmail.com) wrote:
>>
>> > > > > This is racy, as the session ID is not really reliably predictable,
>> > > > > a
On Fri, 1 Dec 2017 18:25:35 +0100
Lennart Poettering wrote:
> On Fr, 01.12.17 13:42, Pekka Paalanen (ppaala...@gmail.com) wrote:
>
> > > > > This is racy, as the session ID is not really reliably predictable,
> > > > > and is synthesized in different contexts in different ways, for
> > > > > exa
On Fr, 01.12.17 13:42, Pekka Paalanen (ppaala...@gmail.com) wrote:
> > > > This is racy, as the session ID is not really reliably predictable,
> > > > and is synthesized in different contexts in different ways, for
> > > > example depnding on whether audit is enabled in the kernel it might be
> >
On Thu, 30 Nov 2017 11:16:19 +
Martyn Welch wrote:
> On Thu, 2017-11-30 at 12:09 +0200, Pekka Paalanen wrote:
> > On Wed, 29 Nov 2017 19:05:07 +0100
> > Lennart Poettering wrote:
> >
> > > On Di, 28.11.17 12:14, Pekka Paalanen (ppaala...@gmail.com) wrote:
> > >
> > > > +
> > > > +[Unit
On Thu, 30 Nov 2017 13:29:22 +0100
Lennart Poettering wrote:
> On Do, 30.11.17 12:09, Pekka Paalanen (ppaala...@gmail.com) wrote:
>
> > > Hmm, what is this about?
> > >
> > > This is racy, as the session ID is not really reliably predictable,
> > > and is synthesized in different contexts in di
On Do, 30.11.17 11:16, Martyn Welch (martyn.we...@collabora.co.uk) wrote:
> Debugging suggested that XDG_RUNTIME_DIR was not being created when it
> failed. There are 2 processes setting a PAMName, the failing Weston
> service and the user@.service (IIRC this gets called as part of user
> session
On Do, 30.11.17 12:09, Pekka Paalanen (ppaala...@gmail.com) wrote:
> > Hmm, what is this about?
> >
> > This is racy, as the session ID is not really reliably predictable,
> > and is synthesized in different contexts in different ways, for
> > example depnding on whether audit is enabled in the k
On Di, 28.11.17 12:14, Pekka Paalanen (ppaala...@gmail.com) wrote:
> +
> +[Unit]
> +Description=Weston, a Wayland compositor, as a system service
> +Documentation=man:weston(1) man:weston.ini(5)
> +Documentation=http://wayland.freedesktop.org/
> +
> +# Make sure we are started after logins are per
On Thu, 2017-11-30 at 12:09 +0200, Pekka Paalanen wrote:
> On Wed, 29 Nov 2017 19:05:07 +0100
> Lennart Poettering wrote:
>
> > On Di, 28.11.17 12:14, Pekka Paalanen (ppaala...@gmail.com) wrote:
> >
> > > +
> > > +[Unit]
> > > +Description=Weston, a Wayland compositor, as a system service
> > >
On Wed, 29 Nov 2017 19:05:07 +0100
Lennart Poettering wrote:
> On Di, 28.11.17 12:14, Pekka Paalanen (ppaala...@gmail.com) wrote:
>
> > +
> > +[Unit]
> > +Description=Weston, a Wayland compositor, as a system service
> > +Documentation=man:weston(1) man:weston.ini(5)
> > +Documentation=http://wa
On Wed, 29 Nov 2017 09:32:02 +0100
Jérémy Rosen wrote:
> I had a quick glance but didn't actually test...
> 2) you probably want to add Alias=display-manager.service, so it can
> pull it other graphical services
Hi,
that sounds like a good idea.
Thanks,
pq
(adding back all the CCs)
> On 2
From: Pekka Paalanen
There are many bad and even worse attempts to make Weston run as a
systemd service, and very few good ones. Let's add a good one as an
example in upstream: does not use weston-launch, does not run weston as
root, does not need wrapper scripts, and relies on logind and PAM.
T
17 matches
Mail list logo
