-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, Feb 20, 2017 at 12:08:00PM +0100, Vincent Lefevre wrote:
> On 2017-02-19 19:52:24 +0000, Brian wrote:
> > On Sun 19 Feb 2017 at 11:00:25 +0100, Vincent Lefevre wrote:
> > 
> > > On 2017-02-18 20:59:44 +0000, Brian wrote:
> > > > The advice in startx(1) is sound but nothing stops you using a ,xinitrc.
> > > > The command doesn't work in a ,xinitrc? Perhaps it is incorrect or the
> > > > DM ignores it.
> > > 
> > > AFAIK, .xinitrc is not used by DM's, in particular because X has
> > > already been started.
> > 
> > I'd agree with the first statement. I am very unsure about the reason
> > advanced.
> 
> Indeed. I think that the reason is that the DM runs /etc/X11/Xsession
> (which starts the window manager at the end), so that this would clash
> with the .xinitrc file, which could do the same thing (the session
> files would be run twice).

No, no, no. Xsession is invoked by the display manager (DM) as you
said (or by startx). Its job is to... uh... get the session running
(window manager, environment, ssh and/or gpg agent, session dbus
(not on my box ;-) that kind of thing -- it used to "do" desktop
environments last time I looked, but that's a while ago)

So far I agree with you :-)

As part of that, it "typically" (that is configurable!) it looks
whether there is a user session RC (typically -- also configurable!)
called ~/.xsessionrc and *sources* it, as part of the session start
up process. The "sourcing" part is important, otherwise you couldn't
set environment variables which get inherited by all your session's
processes.

See man (5) Xsession and poke a bit through the scripts in
/etc/X11/Xsession.d/, then have a look at /etc/X11/Xsession.options,
then at /etc/X11/Xsession.

Regards
- -- t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAliq184ACgkQBcgs9XrR2kZ22wCaAjQMiWHci/BVadoxB+JDzB53
YWAAn3MaFbxOrPXwLN6fnszooo5RJktk
=TEAJ
-----END PGP SIGNATURE-----

Reply via email to