On Fri, Feb 26, 2010 at 10:04 PM, Michael Jinks <[email protected]> wrote: > Sun Ray info: > VERSION: 4.2_17,REV=2009.06.24.11.48
That's not the 4.2 product release. It's probably the first Early Access build, which is now obsolete. Sun Support won't take a call on an EA version, and there were more than a few fixes that went into 4.2 between EA and the final release. Offhand I don't recall any fixes that would have a bearing on this PAM issue but you should plan to move to the final product release anyway. As far as diagnosing the problem goes, I'd start by looking for clues in /var/adm/messages and in /var/dt/Xerrors. If that doesn't help then you might try turning on PAM debug reporting; see http://blogs.sun.com/wittyman/entry/debugging_pam_in_solaris for instructions. If that doesn't identify the problem then you could resort to attaching a 'truss -f -upam' to the 'dtlogin' master process (the one whose parent PID is 1) before you attempt to start a new Sun Ray session and log in. (If you already have a session, choose 'Reset' from the greeter after launching the 'truss'. I think that'll be enough to get you a fresh greeter that will be tracked by the 'truss'.) This will generate tons of output, so be sure to send it to a file (by using the -o option) for later analysis. Just for fun, you might compare the output of 'nm' on your module against the output from the Sun Ray modules and see whether there's a symbol name clash between them. Your module is built as a 32-bit binary, right? OttoM. __ ottomeister Disclaimer: I am employed by Oracle. The statements and opinions expressed here are my own and do not necessarily represent those of Oracle Corporation. _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
