Those snippets from your scripts look correct, is your sessreg set to
executable?
Does anyone else have access to your system?
Might it have been hacked to prevent programs like "w," "who," or
"lastlog" from showing that someone's ghosted in for nefarious purposes?
On 10/18/2020 05:11 PM, IL Ka wrote:
>
> On Sun, Oct 18, 2020 at 5:35 PM Chris Sorenson <cso...@isd.net> wrote:
>
Hello.
>
> xdm runs Xstartup on behalf of the user.
>
Hmm.. man page says: "After the user logs in, xdm runs the Xstartup
script
as root.".
There is a $USER argument passed to this script, but the script itself
runs
as root.
>
> What does your Xstartup say?
>
exec /usr/bin/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x
/usr/lib64/X11/xdm/Xservers -l $DISPLAY -h "" $USER
I am pretty sure the problem is the following line in xdm-config:
DisplayManager*startup: /usr/lib64/X11/xdm/Xstartup
! The following three resources set up display :0 as the console.
DisplayManager._0.startup: /usr/lib64/X11/xdm/GiveConsole
GiveConsole is:
chown $USER /dev/console
So, sessreg is simply not called when xdm serves screen :0
I was able to fix it by copying sessreg line to the GiveConsole, but it
looks like a strange hack..
Ilya
_______________________________________________
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s
