[systemd-devel] Reason for su command to be ignored in target?

[Lennart Poettering]

On Wed, 17.04.13 13:21, Mark Hounschell (markh at compro.net) wrote:

> >>The only thing I see in /var/log/messages is:
> >>
> >>2013-04-17T11:36:51.667308-04:00 utils-linux su: (to lcrs) root on
> >>/dev/ttyS0
> >
> >Bu that's run on ttyS0? Is that really script? How do spawn that script?
> >
> 
> From the service file:
> ExecStart=/sbin/qlogin /dev/ttyS0 root --homedir=/lcrs --noutmp
> --command=/bin/bash --login -c /lcrs/sh.lcrs
> 
> Then in the sh.lcrs "script" ANY su command is borked.
> 
> >>2013-04-17T11:36:51.668896-04:00 utils-linux systemd-logind[1731]:
> >>New session c4 of user lcrs.
> >>2013-04-17T11:36:51.705945-04:00 utils-linux systemd-logind[1731]:
> >>Removed session c4.
> >
> >if you invoke "logger test" via su here, do you see it logging
> >something?
> >
> >Maybe your implementation of "su" is borked? Some older implementations
> >misused PAM and immediately closed the PAM session after creating
> >it... Which implementation do you use?
> >
> 
> # rpm -qf /usr/bin/su
> coreutils-8.17-6.2.1.i586

That looks OK. Can you try the logger thing I suggested? That should
tell us if the transition works at all...

Lennart

-- 
Lennart Poettering - Red Hat, Inc.