Brian,
many thanks for your detailed response. Should we continue this discussion
in gdm-list or in sunray-users list?
Brian Cameron brian.came...@oracle.com wrote:
We observed that the 57 gconfd daemons somehow blocked each other(?)
(status D in the process list) and the load factor of
I was working on overhauling our PAM configuration today and wondered, as
before, what the dtsession-SunRay entries are for. As far as I can tell,
dtsession is only for unlocking a locked CDE session, and this IBM link
(http://publib.boulder.ibm.com/infocenter/aix/v6r1/index.jsp?topic=/com.ibm.
On Wed, 05 Jan 2011 09:43:21 -0600
Brian Cameron brian.came...@oracle.com wrote:
Meik:
This bugpatch is about the $HOME/.gconf directory. After updating
my gconfd from 2.28 to 2.32 this works for me and I have now a
per-session .gconf directory
This should make GConf behave better
Yes, dtlogin is just for CDE.
However, it's incorrect to say that only the auth stack is used (thanks IBM).
The other stacks are all important:
account is for accounting, if you want to user logins/logouts to be logged
(which is sort of the main point IMO).
password is to implement password
Slight mis-statement:
On 01/05/11 17:16, Bob Doolittle wrote:
utnsclogin doesn't need these, because it's not actually a Display Manager - it
doesn't manage displays/sessions. It only does authentication and potentially
redirection to the server hosting the token's session (if a session
Hi Bob,
Thanks for the reply. That was very informative, along with your other
clarification e-mail. I think you misread part of my initial question
though. While all of the 4 PAM sections dtlogin-SunRay are used, what about
for dtSESSION-SunRay (which was my original question)? Also, does
If I understand correctly, that means two invocations of PAM are actually
used. But does that mean there is no way to handle users' expired
passwords? Normally under dtlogin, if the account password is expired, they
are prompted to change it when the auth module succeeds but the account
module
