| Title: | DCE Product Information |
| Notice: | Kit Info - See 2.*-4.* |
| Moderator: | TUXEDO::MAZZAFERRO |
| Created: | Fri Jun 26 1992 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2269 |
| Total number of notes: | 10003 |
Why does the login process takes around 30 seconds? dce_login is
nearly instantaneous. Logging in via telnet or login authenticates the
password fairly quickly (we get the "Last login:" immediately) but then
nothing for almost exactly 30 seconds
My customers are running Digital UNIX v4.0a and DCE v2.0a. SIA is
enabled. One customer has C2 enabled, one does not.
The customer running with regular security also has a source code
license to Digital UNIX, so we took a look at login.c and it appears
that the hang up happens when calling sia_ses_launch(). In
sia_ses_launch() we think that the call to sia_matrix() may be the
culprit.
The interesting thing is if we remove (BSD,libc.so) from
siad_ses_launch in matrix.conf and leave (DCE,/usr/shlib/libdcesiad.so)
the delay goes away but we end up logged in as root!
Another thing that we noticed was that if the username/password was the
same on the local machine as it was in the DCE registry, the user was
logged in unauthenticated.
If these are bugs, please let me know and I will QAR them. If it is a
configuration issue around matrix.conf or something else, please let
me know and I will inform my customers.
Thanks in advance.
Scott Fafrak
[email protected]
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2251.1 | network layout | VIRGIN::BILL | BILL is my lastname !!! | Fri May 16 1997 12:02 | 16 |
Scott, This behaviour looks like timeouts. What is the network layout ? Is any of the CDS/SEC server on a system with multiple network interface ? A client will try to reach the security server on one of the advertised interfaces (rpccp show entry /.:/subsys/dce/sec/master or replicas) If the client is not able to connect to a network interface he will timeout and retry the next interface. To analyse this problem you can set the BIND_PE_SITE variable to 1 on a client. This forces the client to use the /opt/dcelocal/etc/security/pe_site for the lookup and not the CDS. You can edit the pe_site file to see if the behaviour changes... /marco | |||||
| 2251.2 | it's the same machine | DAGWST::FAFRAK | RISCy business... | Fri May 16 1997 16:25 | 12 |
Ironically, the problem we're having is on the same machine. In fact,
at this one customer in particular, he is running DCE on only one
system. So when he is connecting to the machine via telnet, this
machine IS the CDS and Security server.
So for this situation, how does he set the environment variable when he
does not have an environment? Or is this variable set in the
dcestartup for DCE to deal with?
Thanks
Scott
| |||||