The argument should keep its original value of NULL, and should still apply for what it was originally for, which is non-Sun non-PAM OSes. Okay. Perhaps instead of trying to also repurpose it for PAM, something else should be done for HAS_PAM_LIBRARY, something with _DtAccounting that is analogous to the PamAccounting call in the original Sun PAM code path...
The argument should keep its original value of NULL, and should still apply for what it was originally for, which is non-Sun non-PAM OSes. Okay. Perhaps instead of trying to also repurpose it for PAM, something else should be done for HAS_PAM_LIBRARY, something with _DtAccounting that is analogous to the PAMAccounting call in the original Sun PAM code path...
Note that the d->gettyLine value isn't necessarily a 'correct' TTY device for Linux, it's just whatever you put after the @ in the /etc/dt/config/Xservers line for a local session, or dtremote for an XDMCP session, but that you can at least use to distinguish multiple X sessions and certainly better than NULL.
Note that the d->gettyLine value isn't necessarily a 'correct' TTY device for Linux, it's just whatever you put after the @ in the /etc/dt/config/Xservers line for a local session, or dtremote for an XDMCP session, but that's fine to use and certainly better than NULL.
To test in Debian 10 I have a systemd service config for dtlogin in /etc/systemd/system/dtlogin.service: [Unit] Description=CDE login service After=systemd-user-sessions.service [Service] ExecStart=/usr/dt/bin/dtlogin -debug 1 [Install] WantedBy=graphical.target and in the CDE-installed /etc/pam.d/dtlogin I add the line: @include common-session The common-session PAM config is from Debian and includes pam_systemd.so
HAS_PAM_LIBRARY dtlogin sets PAM session PAM_TTY to bogus value "/dev/NULL"
added linux pam support
bump down the restart delay on linux