Sponsored Content
Full Discussion: Login Slowness
Operating Systems Solaris Login Slowness Post 302332400 by Hari_Ganesh on Thursday 9th of July 2009 04:00:40 AM
Old 07-09-2009
Hi otheus,

sorry for the delay.
Pasting the requested output:

[8]d08083: time ypcat hosts >/dev/null
real 0m0.05s
user 0m0.00s
sys 0m0.03s
mumux101 @ /users/d08083
[9]d08083: time getent hosts > /dev/null
real 0m0.01s
user 0m0.01s
sys 0m0.00s
mumux101 @ /users/d08083
[10]d08083:

May i know what you are trying to achieve/convey?

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
SG_RBUF(8)							     SG3_UTILS								SG_RBUF(8)

NAME
sg_rbuf - reads data using SCSI READ BUFFER command SYNOPSIS
sg_rbuf [--buffer=EACH] [--dio] [--help] [--mmap] [--quick] [--size=OVERALL] [--test] [--verbose] [--version] DEVICE sg_rbuf [-b=EACH_KIB] [-d] [-m] [-q] [-s=OVERALL_MIB] [-t] [-v] [-V] DEVICE DESCRIPTION
This command reads data with the SCSI READ BUFFER command and then discards it. Typically the data being read is from a disk's memory cache. It is assumed that the data is sourced quickly (although this is not guaranteed by the SCSI standards) so that it is faster than reading data from the media. This command is designed for timing transfer speeds across a SCSI transport. To fetch the data with a SCSI READ BUFFER command and optionally decode it see the sg_read_buffer utility. There is also a sg_write_buffer utility useful for downloading firmware amongst other things. This utility supports two command line syntaxes, the preferred one is shown first in the synopsis and explained in this section. A later section on the old command line syntax outlines the second group of options. OPTIONS
Arguments to long options are mandatory for short options as well. -b, --buffer=EACH where EACH is the number of bytes to be transferred by each READ BUFFER command. The default is the actual available buffer size returned by the READ BUFFER (descriptor) command. The maximum is the same as the default, hence this argument can only be used to reduce the size of each transfer to less than the device's actual available buffer size. -d, --dio use direct IO if available. This option is only available if the DEVICE is a sg driver device node (e.g. /dev/sg1). In this case the sg driver will attempt to configure the DMA from the SCSI adapter to transfer directly into user memory. This will eliminate the copy via kernel buffers. If not available then this will be reported and indirect IO will be done instead. -h, --help print usage message then exit. -m, --mmap use memory mapped IO if available. This option is only available if the DEVICE is a sg driver device node (e.g. /dev/sg1). In this case the sg driver will attempt to configure the DMA from the SCSI adapter to transfer directly into user memory. This will elimi- nate the copy via kernel buffers. -O, --old switch to older style options. -q, --quick only transfer the data into kernel buffers (typically by DMA from the SCSI adapter card) and do not move it into the user space. This option is only available if the DEVICE is a sg driver device node (e.g. /dev/sg1). -s, --size=OVERALL where OVERALL is the size of total transfer in bytes. The default is 200 MiB (200*1024*1024 bytes). The actual number of bytes transferred may be slightly less than requested since all transfers are the same size (and an integer division is involved rounding towards zero). -t, --time times the bulk data transfer component of this command. The elapsed time is printed out plus a MB/sec calculation. In this case "MB" is 1,000,000 bytes. The gettimeofday() system call is used internally for the time calculation. -v, --verbose increase level of verbosity. Can be used multiple times. -V, --version print out version string then exit. NOTES
This command is typically used on modern SCSI disks which have a RAM cache in their drive electronics. If no IO to the magnetic media, or slower devices like flash RAM, is involved then the disk may be able to source data fast enough to saturate the bandwidth of the SCSI transport. The bottleneck may then be the DMA element in the HBA, the Linux drivers or the host machine's hardware (e.g. speed of RAM). Various numeric arguments (e.g. OVERALL) may include multiplicative suffixes or be given in hexadecimal. See the "NUMERIC ARGUMENTS" sec- tion in the sg3_utils(8) man page. EXAMPLES
On the test system /dev/sg0 corresponds to a fast disk on a U2W SCSI bus (max 80 MB/sec). The disk specifications state that its cache is 4 MB. $ time ./sg_rbuf /dev/sg0 READ BUFFER reports: buffer capacity=3434944, offset boundary=6 Read 200 MiB (actual 199 MiB, 209531584 bytes), buffer size=3354 KiB real 0m5.072s, user 0m0.000s, sys 0m2.280s So that is approximately 40 MB/sec at 40 % utilization. Now with the addition of the "-q" option this throughput improves and the utiliza- tion drops to 0%. $ time ./sg_rbuf -q /dev/sg0 READ BUFFER reports: buffer capacity=3434944, offset boundary=6 Read 200 MiB (actual 199 MiB, 209531584 bytes), buffer size=3354 KiB real 0m2.784s, user 0m0.000s, sys 0m0.000s EXIT STATUS
The exit status of sg_rbuf is 0 when it is successful. Otherwise see the sg3_utils(8) man page. OLDER COMMAND LINE OPTIONS
The options in this section were the only ones available prior to sg3_utils version 1.23 . In sg3_utils version 1.23 and later these older options can be selected by either setting the SG3_UTILS_OLD_OPTS environment variable or using '--old' (or '-O) as the first option. -b=EACH_KIB where EACH_KIB is the number of Kilobytes (i.e. 1024 byte units) to be transferred by each READ BUFFER command. Similar to the --buffer=EACH option in the main description but the units are different. -d use direct IO if available. Equivalent to the --dio option in the main description. -m use memory mapped IO if available. Equivalent to the --mmap option in the main description. -N switch to the newer style options. -q only transfer the data into kernel buffers (typically by DMA from the SCSI adapter card) and do not move it into the user space. Equivalent to the --quick option in the main description. -s=OVERALL_MIB where OVERALL_MIB is the size of total transfer in Megabytes (1048576 bytes). Similar to the --size=OVERALL option in the main description but the units are different. -t times the bulk data transfer component of this command. Equivalent to the --time option in the main description. -v increase level of verbosity. Can be used multiple times. -V print out version string then exit. AUTHOR
Written by Doug Gilbert REPORTING BUGS
Report bugs to <dgilbert at interlog dot com>. COPYRIGHT
Copyright (C) 2000-2007 Douglas Gilbert This software is distributed under the GPL version 2. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PUR- POSE. SEE ALSO
sg_read_buffer, sg_write_buffer, sg_test_rwbuf(all in sg3_utils) sg3_utils-1.23 January 2007 SG_RBUF(8)
All times are GMT -4. The time now is 02:07 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy