On 04/17/2013 04:16 PM, Lennart Poettering wrote:
On Wed, 17.04.13 16:08, Mark Hounschell (ma...@compro.net) wrote:
That looks OK. Can you try the logger thing I suggested? That should
tell us if the transition works at all...
Sorry, I had a dentist Apt.
Uh, I put this as the first command in the /lcrs/sh.lcrs script:
/bin/su -m -c "logger test" lcrs
This comes out in the log:
2013-04-17T15:41:29.754272-04:00 utils-linux systemd-logind[1722]:
New session c1 of user lcrs.
2013-04-17T15:41:29.829129-04:00 utils-linux logger: test
2013-04-17T15:41:29.831565-04:00 utils-linux systemd-logind[1722]:
Removed session c1.
A couple of strange things now. The rest of the script works fine
now??? I removed the logger test and rebooted. The script is still
working???? Is there something being cached somewhere? I swear
anything I used su for was borked until I added that extra line???
Hmm, no clue. If the logger thing worked, then maybe the next thing
would be to patch the script you start via su and add a logger line to
the beginning and to the end of it it, and check if that still is
generated.
I added these to the script started at beginning and end and the
messages are still generated. I hate problems that just go away with no
explanation. In any case, thanks for fixing it for me. You must have
magical powers??
Regards
Mark
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
