Sponsored Content
Full Discussion: Login Process takes longer
Top Forums UNIX for Advanced & Expert Users Login Process takes longer Post 302141618 by mah on Saturday 20th of October 2007 05:01:49 PM
Old 10-20-2007
Maybe try pinging the IP and check its connectiviti.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Killing a process that takes too long

Hello, I have a C program that takes anywhere from 5 to 100 arguments and I'd like to run it from a script that makes sure it doesnt take too long to execute. If the C program takes more than 5 seconds to execute, i would like the shell script to kill it and return a short message to the user. ... (3 Replies)
Discussion started by: WeezelDs
3 Replies

2. Forum Support Area for Unregistered Users & Account Problems

Can no longer login.

I registered last week, received the emails and activated my account. It worked splendidly. Today, I logged in, performed a search, then was prompted to login each time I moved to the next page in the search results. I requested and received a new password but UNIX.com thanks me for logging... (0 Replies)
Discussion started by: thebigm
0 Replies

3. Linux

it takes long time to login on server

Hi, I am trying to login using ssh on Red Hat Linux 5 server, The password appears immediately but after I enter the password it takes about 90 seconds to login completely. Please suggest what changes require? Regards, Manoj (4 Replies)
Discussion started by: manoj.solaris
4 Replies

4. UNIX and Linux Applications

Syb15 Query takes longer, help me out

When i run the below query in syb15 (with syb 12.5.X backward compatibilty) environment it runs 45min where as the same in syb12.5.1 it takes only 7-10min. But the main thing is stld_date(in the below query) does not covered in the index of that table. Also main_table is a huge table. So is it... (1 Reply)
Discussion started by: prsam
1 Replies

5. Programming

select() system call takes longer than the timeout specified

Below is my code. Every once in a while the select call takes as long as 150 seconds (discovered by printing time before and after this statement) while the timeout specified into it is only 1 second. Any clue why? I can't believe that select call which has been around for centuries can have a bug,... (15 Replies)
Discussion started by: old_as_a_fossil
15 Replies

6. Shell Programming and Scripting

script to monitor the process system when a process from user takes longer than 15 min run.

get email notification from from system when a process from XXXX user takes longer than 15 min run.Let me know the time estimation for the same. hi ,any one please tell me , how to write a script to get email notification from system when a process from as mentioned above a xxxx user takes... (1 Reply)
Discussion started by: kirankrishna3
1 Replies

7. UNIX for Dummies Questions & Answers

Changing Password process takes a long time

We are running unix. After a reboot of the server we have found that changing password takes a long time. if type in passwd "username" you can type in the 1st instance of the password , press enter , then it will wait for about 3 minutes before bringing up the confirm password line typing it in... (4 Replies)
Discussion started by: AIXlewis
4 Replies

8. Solaris

Login takes 44secs to 50secs

Hi, Anyone can help me, I have 10 servers all was Solaris 10 installed. The 9 servers was so fast ounce you login. But only 1 server will take 44secs to 55secs to login. I check all the hardware side it was ok. I'm using ssh, putty, ftp and telnet to login. Can you please me for any work... (11 Replies)
Discussion started by: fspalero
11 Replies

9. Red Hat

Login to server takes time

When I am trying to login to a server using Putty ssh from my windows xp machine it is taking too much time for login. My server name is http2 and when I enter this address into putty I immediately get login as: screen, but after I put my username root and enter the cursor moves downwards... (14 Replies)
Discussion started by: abhilashkrishn
14 Replies

10. UNIX and Linux Applications

database takes long time to process

Hi, we currently having a issue where when we send jobs to the server for the application lawson, it is taking a very long time to complete. here are the last few lines of the database log. 2012-09-18-10.35.55.707279-240 E244403536A576 LEVEL: Warning PID : 950492 ... (1 Reply)
Discussion started by: techy1
1 Replies
fping(8)						      System Manager's Manual							  fping(8)

NAME
fping - send ICMP ECHO_REQUEST packets to network hosts SYNOPSIS
fping [ options ] [ systems... ] DESCRIPTION
fping is a program like ping(8) which uses the Internet Control Message Protocol (ICMP) echo request to determine if a target host is responding. fping differs from ping in that you can specify any number of targets on the command line, or specify a file containing the lists of targets to ping. Instead of sending to one target until it times out or replies, fping will send out a ping packet and move on to the next target in a round-robin fashion. In the default mode, if a target replies, it is noted and removed from the list of targets to check; if a target does not respond within a certain time limit and/or retry limit it is designated as unreachable. fping also supports sending a specified number of pings to a tar- get, or looping indefinitely (as in ping ). Unlike ping, fping is meant to be used in scripts, so its output is designed to be easy to parse. OPTIONS
-a Show systems that are alive. -A Display targets by address rather than DNS name. -bn Number of bytes of ping data to send. The minimum size (normally 12) allows room for the data that fping needs to do its work (sequence number, timestamp). The reported received data size includes the IP header (normally 20 bytes) and ICMP header (8 bytes), so the minimum total size is 40 bytes. Default is 56, as in ping. Maximum is the theoretical maximum IP datagram size(64K), though most systems limit this to a smaller, system-dependent number. -Bn In the default mode, fping sends several requests to a target before giving up, waiting longer for a reply on each successive request. This parameter is the value by which the wait time is multiplied on each successive request; it must be entered as a floating-point number (x.y). The default is 1.5. -c Number of request packets to send to each target. In this mode, a line is displayed for each received response (this can suppressed with -q or -Q). Also, statistics about responses for each target are displayed when all requests have been sent (or when inter- rupted). -C Similar to -c, but the per-target statistics are displayed in a format designed for automated response-time statistics gathering. For example: % fping -C 5 -q somehost somehost : 91.7 37.0 29.2 - 36.8 shows the response time in milliseconds for each of the five requests, with the "-" indicating that no response was received to the fourth request. -d Use DNS to lookup address of return ping packet. This allows you to give fping a list of IP addresses as input and print hostnames in the output. -e Show elapsed (round-trip) time of packets. -f Read list of targets from a file. This option can only be used by the root user. Regular users should pipe in the file via stdin: % fping < targets_file -g Generate a target list from a supplied IP netmask, or a starting and ending IP. Specify the netmask or start/end in the targets por- tion of the command line. If a network with netmask is given, the network and broadcast addresses will be excluded. ex. To ping the network 192.168.1.0/24, the specified command line could look like either: fping -g 192.168.1.0/24 or fping -g 192.168.1.1 192.168.1.254 -h Print usage message. -in The minimum amount of time (in milliseconds) between sending a ping packet to any target (default is 25). -l Loop sending packets to each target indefinitely. Can be interrupted with Ctrl-C; statistics about responses for each target are then displayed. -m Send pings to each of a target host's multiple interfaces. -n Same as -d. -p In looping or counting modes (-l, -c, or -C), this parameter sets the time in milliseconds that fping waits between successive packets to an individual target. Default is 1000. -q Quiet. Don't show per-target results, just set final exit status. -Qn Like -q, but show summary results every n seconds. -rn Retry limit (default 3). This is the number of times an attempt at pinging a target will be made, not including the first try. -s Print cumulative statistics upon exit. -Saddr Set source address. -Iif Set the interface (requires SO_BINDTODEVICE support) -tn Initial target timeout in milliseconds (default 500). In the default mode, this is the amount of time that fping waits for a response to its first request. Successive timeouts are multiplied by the backoff factor. -Tn Ignored (for compatibility with fping 2.4). -u Show targets that are unreachable. -Tn Set the typ of service flag (TOS). n can be either decimal or hexadecimal(0xh) format. -v Print fping version information. -Hn Set the IP TTL field (time to live hops). EXAMPLES
The following perl script will check a list of hosts and send mail if any are unreachable. It uses the open2 function which allows a pro- gram to be opened for reading and writing. fping does not start pinging the list of systems until it reads EOF, which it gets after INPUT is closed. Sure the open2 usage is not needed in this example, but it's a good open2 example none the less. #!/usr/bin/perl require 'open2.pl'; $MAILTO = "root"; $pid = &open2("OUTPUT","INPUT","/usr/local/bin/fping -u"); @check=("slapshot","foo","foobar"); foreach(@check) { print INPUT "$_ "; } close(INPUT); @output=<OUTPUT>; if ($#output != -1) { chop($date=`date`); open(MAIL,"|mail -s 'unreachable systems' $MAILTO"); print MAIL " The following systems are unreachable as of: $date "; print MAIL @output; close MAIL; } Another good example is when you want to perform an action only on hosts that are currently reachable. #!/usr/bin/perl $hosts_to_backup = `cat /etc/hosts.backup | fping -a`; foreach $host (split(/ /,$hosts_to_backup)) { # do it } AUTHORS
Roland J. Schemers III, Stanford University, concept and versions 1.x RL "Bob" Morgan, Stanford University, versions 2.x David Papp, versions 2.3x and up, David Schweikert, versions 3.0 and up fping website: http://www.fping.org DIAGNOSTICS
Exit status is 0 if all the hosts are reachable, 1 if some hosts were unreachable, 2 if any IP addresses were not found, 3 for invalid com- mand line arguments, and 4 for a system call failure. BUGS
Ha! If we knew of any we would have fixed them! RESTRICTIONS
If certain options are used (i.e, a low value for -i and -t, and a high value for -r) it is possible to flood the network. This program must be installed as setuid root in order to open up a raw socket, or must be run by root. In order to stop mere mortals from hosing the network (when fping is installed setuid root) , normal users can't specify the following: -i n where n < 10 msec -r n where n > 20 -t n where n < 250 msec SEE ALSO
netstat(1), ping(8), ifconfig(8c) fping(8)
All times are GMT -4. The time now is 08:50 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy