Hi. On Sat, 29 Aug 2015 11:49:12 +1200 Chris Bannister <cbannis...@slingshot.co.nz> wrote:
> On Fri, Aug 28, 2015 at 07:12:32PM +0300, Reco wrote: > > To: > > > > Well, there have been long discussions about this, but the problem is > > that what "su" is supposed to do is very unclear. On one hand it's > > supposed *to open a new session* and change a number of execution > > context parameters (uid, gid, env, ...), and on the other it's supposed > > to inherit a lot concepts from the originating session (tty, cgroup, > > audit, ...). > > > > > > I'm kind of surprised that the bug was not closed as WONTFIX. su(1) is > > not a "full login", but it's not supposed to provide one anyway. > > su - <name> > > Has always worked fine for me. What's the problem? https://github.com/systemd/systemd/issues/825 says: su[1980]: pam_systemd(su-l:session): Cannot create session: Already running in a session Why the bug report implies that pam_systemd shoud create a new 'session' (whatever it means by 'session') *and* set some obscure environment variables is beyond me. Especially since su(1) directly says that su should not create session, it should reuse an existing one. Reco
