Try adding a "debug" keyword to pam_sunray_amgh in /etc/pam.conf, and
adding a "*.debug /var/opt/SUNWut/log/messages" line to /etc/syslog.conf
(and then HUP the syslog daemon).
That will give significantly more data regarding what's going on.
-Bob
Scott L Riggen wrote:
Bob,
We don't turn syslog off......We just log it to a central server. with the
volume of data in there right now it's hard to find my particular stuff.
I'm going to chat with the syslog guru to see what options we have on this to
make it easier. I set it up the sunray way so it would be easier to grub
through the local logs.
That's what everyone things, until they have a problem. :) Often it's
too late to tell what happened if syslog was disabled.
The logs rotate and take care of themselves, so it seems harmless and
prudent to leave the logging on. Just my 2c...
Yes, it matches what is in my back_end_db. So I guess I am back at square one
trying to figure out why switching is not working. I might just trash the
entire system and reload everything to make sure all the various utconfig and
utadm stuff didn't leave behind something hanging me up. Unless you have any
other ideas :) I'm stumped, frustrated, and about out of patience. I'm
thinking about putting our crappy old Xsetup script back in place and letting
the users bounce around until utswitch does the right thing somehow.....
What does "utuser -p user.1265220350-7053" report? Does it match the
"Payflex.*" name reported in your back_end_db file?
_______________________________________________
SunRay-Users mailing list
SunRay-Users@filibeto.org
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
SunRay-Users@filibeto.org
http://www.filibeto.org/mailman/listinfo/sunray-users
