Sponsored Content
Full Discussion: Login Slowness
Operating Systems Solaris Login Slowness Post 302331355 by Hari_Ganesh on Monday 6th of July 2009 02:06:32 AM
Old 07-06-2009
Login Slowness

Hi Folks

My Sun Solaris servers are waiting for a long time after keying in the User-ID. There is a big delay in getting to the password prompt. But once the password is keyed in,it goes through in a second.

The servers in which i am facing this issue is an NIS client. But i am facing this issue for Local users also.

Any idea what the issue is and how it can be resolved?

The /etc/nsswitch.conf file has the passwd variable like below:

passwd: files nis



Thanks
HG
 

10 More Discussions You Might Find Interesting

1. Linux

slowness of Linux 8.0 server

Hi, I have a Linux 8.0 Redhat installed as a server. The samba configuration was done to allowed logging in to the server from windows workstations. I have a LAN, WAN connection. However, any time the workstation is trying to make a WAN connection it slow down all the systems on the network. Can... (0 Replies)
Discussion started by: kayode
0 Replies

2. SCO

Terminal Slowness

I have attempted to2find answers to this question: When logging into tty01 the system will take 5 to 10 seconds to display each character typed. Each other terminal will login correctly and display correctly2but not the first terminal. Rebooting was suggested on several sites and this has been... (2 Replies)
Discussion started by: ypanic
2 Replies

3. HP-UX

HP-UX Intermec Label Slowness

We recently moved from a Open VMS OS to HP-UX. When printing labels on Intermec 3400 printers we are seeing a delay of up to 3 minutes before labels print. We have printers going through a DEC Term servers and Jet Direct boxes. Any suggestions what might be causing this delay? (4 Replies)
Discussion started by: BIGJIM
4 Replies

4. Solaris

error message rmclomv ... SC Login Failure for user Please login:

Hello World ~ HW : SUN Fire V240 OS : Solaris 8 Error message prompts 'rmclomv ... SC login failure ...' on terminal. and Error Message prompts continually 'SC Login Failure for user Please login:' on Single Mode(init S) The System is in normal operation, though In case of rain, Can... (1 Reply)
Discussion started by: lifegeek
1 Replies

5. Solaris

Solaris 10 Slowness

Hi, We have got 2 solaris boxes, since our inhouse application has certified on solaris environment and now we need to certify the performance of that application on Solaris environment. 1 box we have installed websphere and the other box we have installed Oracle 10.2.0.3. both are 64bit. ... (5 Replies)
Discussion started by: mp_rocket
5 Replies

6. Solaris

NIS performance slowness

Hi I have a Solaris 10 NIS server and more than 250 NIS clients out of these there are 5 main application servers, and whenever there is any compilation happens on any of the application servers (which are acting as NIS clients) entire NIS performance will come down.Can some one help me to fix... (5 Replies)
Discussion started by: nithnara
5 Replies

7. Solaris

ssh slowness

Hi admins, After changing the ip address(temperorily) ssh to that server is very slow(exactly 25 sec).But from this new ip i can ssh to other servers without any delay problem. debug1: match: Sun_SSH_1.1.1 pat Sun_SSH_1.1.1* debug1: Enabling compatibility mode for protocol 2.0 debug1:... (2 Replies)
Discussion started by: newsol
2 Replies

8. Solaris

Java Application slowness with Xmanager

Hi! I have a m3000 server with solaris 10. Clients connecting to server using Xmanager. But when they open a Java based application its very slow and some times hanging. But when I tried with VNC it works fine. Is this a BUG in Xmanager? Or Is there any method to solve this? Thanks, Charith (3 Replies)
Discussion started by: charith.upendra
3 Replies

9. Solaris

Login slowness from LDOM to ZONE

Need assitance in troubleshooting steps . Below is the issue I have LDOM which has 4 zones on it . One zone logging into the server takes 13sec where as other zones are quick . Troubleshooting steps which I did - Checked /var/tmp . Not many files - We have LDAP but thought that wouldnt be... (7 Replies)
Discussion started by: ajayram_arya
7 Replies

10. AIX

Slowness issue

Oracle database is facing slowness issues frequently on AIX server. So can anybody suggest how to fix these issues from OS end? Do we need to tune any parameter in AIX to resolve this issue? Please post in an adequate forum! (1 Reply)
Discussion started by: vithal
1 Replies
nisclient(1M)						  System Administration Commands					     nisclient(1M)

NAME
nisclient - initialize NIS+ credentials for NIS+ principals SYNOPSIS
/usr/lib/nis/nisclient -c [-x] [-o] [-v] [-l <network_password>] [-d <NIS+_domain>] client_name... /usr/lib/nis/nisclient -i [-x] [-v] -h <NIS+_server_host> [-a <NIS+_server_addr>] [-k <key_domain>] [-d <NIS+_domain>] [-S 0 | 2] /usr/lib/nis/nisclient -u [-x] [-v] /usr/lib/nis/nisclient -r [-x] DESCRIPTION
The nisclient shell script can be used to: o create NIS+ credentials for hosts and users o initialize NIS+ hosts and users o restore the network service environment NIS+ credentials are used to provide authentication information of NIS+ clients to NIS+ service. Use the first synopsis (-c option) to create individual NIS+ credentials for hosts or users. You must be logged in as a NIS+ principal in the domain for which you are creating the new credentials. You must also have write permission to the local "cred" table. The client_name argument accepts any valid host or user name in the NIS+ domain (for example, the client_name must exist in the hosts or passwd table). nisclient verifies each client_name against both the host and passwd tables, then adds the proper NIS+ credentials for hosts or users. Note that if you are creating NIS+ credentials outside of your local domain, the host or user must exist in the host or passwd tables in both the local and remote domains. By default, nisclient will not overwrite existing entries in the credential table for the hosts and users specified. To overwrite, use the -o option. After the credentials have been created, nisclient will print the command that must be executed on the client machine to ini- tialize the host or the user. The -c option requires a network password for the client which is used to encrypt the secret key for the client. You can either specify it on the command line with the -l option or the script will prompt you for it. You can change this network password later with passwd(1) or chkey(1). nisclient -c is not intended to be used to create NIS+ credentials for all users and hosts which are defined in the passwd and hosts tables. To define credentials for all users and hosts, use nispopulate(1M). Use the second synopsis (-i option) to initialize a NIS+ client machine. The -i option can be used to convert machines to use NIS+ or to change the machine's domainname. You must be logged in as super-user on the machine that is to become a NIS+ client. Your administrator must have already created the NIS+ credential for this host by using nisclient -c or nispopulate -C. You will need the network password your administrator created. nisclient will prompt you for the network password to decrypt your secret key and then for this machine's root login password to generate a new set of secret/public keys. If the NIS+ credential was created by your administrator using nisclient -c, then you can simply use the initialization command that was printed by the nisclient script to initialize this host instead of typing it manually. To initialize an unauthenticated NIS+ client machine, use the -i option with -S 0. With these options, the nisclient -i option will not ask for any passwords. During the client initialization process, files that are being modified are backed up as files.no_nisplus. The files that are usually modi- fied during a client initialization are: /etc/defaultdomain, /etc/nsswitch.conf, /etc/inet/hosts, and, if it exists, /var/nis/NIS_COLD_START. Notice that a file will not be saved if a backup file already exists. The -i option does not set up a NIS+ client to resolve hostnames using DNS. Please refer to the DNS documentation for information on set- ting up DNS. (See resolv.conf(4)). It is not necessary to initialize either NIS+ root master servers or machines that were installed as NIS+ clients using suninstall(1M). Use the third synopsis (-u option) to initialize a NIS+ user. You must be logged in as the user on a NIS+ client machine in the domain where your NIS+ credentials have been created. Your administrator should have already created the NIS+ credential for your username using nisclient -c or nispopulate(1M). You will need the network password your administrator used to create the NIS+ credential for your user- name. nisclient will prompt you for this network password to decrypt your secret key and then for your login password to generate a new set of secret/public keys. Use the fourth synopsis (-r option) to restore the network service environment to whatever you were using before nisclient -i was executed. You must be logged in as super-user on the machine that is to be restored. The restore will only work if the machine was initialized with nisclient -i because it uses the backup files created by the -i option. Reboot the machine after initializing a machine or restoring the network service. OPTIONS
The following options are supported: -a <NIS+_server_addr> Specifies the IP address for the NIS+ server. This option is used only with the -i option. -c Adds DES credentials for NIS+ principals. -d <NIS+_domain> Specifies the NIS+ domain where the credential should be created when used in conjunction with the -c option. It specifies the name for the new NIS+ domain when used in conjunction with the -i option. The default is your current domainname. -h <NIS+_server_host> Specifies the NIS+ server's hostname. This option is used only with the -i option. -i Initializes a NIS+ client machine. -l <network_password> Specifies the network password for the clients. This option is used only with the -c option. If this option is not specified, the script will prompt you for the network password. -k <key_domain> This option specifies the domain where root's credentials are stored. If a domain is not specified, then the system default domain is assumed. -o Overwrites existing credential entries. The default is not to overwrite. This is used only with the -c option. -r Restores the network service environment. -S 0|2 Specifies the authentication level for the NIS+ client. Level 0 is for unauthenticated clients and level 2 is for authenticated (DES) clients. The default is to set up with level 2 authentication. This is used only with the -i option. nisclient always uses level 2 authentication (DES) for both -c and -u options. There is no need to run nisclient with -u and -c for level 0 authentication. To configure authentication mechanisms other than DES at secu- rity level 2, use nisauthconf(1M) before running nisclient. -u Initializes a NIS+ user. -v Runs the script in verbose mode. -x Turns the "echo" mode on. The script just prints the commands that it would have executed. Notice that the commands are not actually executed. The default is off. EXAMPLES
Example 1: Adding the DES Credential in the Local Domain To add the DES credential for host sunws and user fred in the local domain: example% /usr/lib/nis/nisclient -c sunws fred Example 2: Adding the DES Credential in a Specified Domain To add the DES credential for host sunws and user fred in domain xyz.example.com.: example% /usr/lib/nis/nisclient -c -d xyz.example.com. sunws fred Example 3: Initializing the Host in a Specific Domain To initialize host sunws as a NIS+ client in domain xyz.example.com. where nisplus_server is a server for the domain xyz.example.com.: example# /usr/lib/nis/nisclient -i -h nisplus_server -d xyz.example.com The script will prompt you for the IP address of nisplus_server if the server is not found in the /etc/hosts file. The -d option is needed only if your current domain name is different from the new domain name. Example 4: Initializing the Host as an Unauthenticated Client in a Specific Domain To initialize host sunws as an unauthenticated NIS+ client in domain xyz.example.com. where nisplus_server is a server for the domain xyz.example.com: example# /usr/lib/nis/nisclient -i -S 0 -h nisplus_server -d xyz.example.com. -a 172.16.44.1 Example 5: Initializing the User as a NIS+ principal To initialize user fred as a NIS+ principal, log in as user fred on a NIS+ client machine. example% /usr/lib/nis/nisclient -u FILES
/var/nis/NIS_COLD_START This file contains a list of servers, their transport addresses, and their Secure RPC public keys that serve the machines default domain. /etc/defaultdomain The system default domainname. /etc/nsswitch.conf Configuration file for the name-service switch. /etc/inet/hosts Local host name database. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWnisu | +-----------------------------+-----------------------------+ SEE ALSO
chkey(1), keylogin(1), nis+(1), passwd(1), keyserv(1M), nisaddcred(1M), nisauthconf(1M), nisinit(1M), nispopulate(1M), suninstall(1M), nss- witch.conf(4), resolv.conf(4), attributes(5) NOTES
NIS+ might not be supported in future releases of the SolarisTM Operating Environment. Tools to aid the migration from NIS+ to LDAP are available in the Solaris 9 operating environment. For more information, visit http://www.sun.com/directory/nisplus/transition.html. SunOS 5.10 12 Dec 2001 nisclient(1M)
All times are GMT -4. The time now is 07:31 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy