Sponsored Content
Top Forums Shell Programming and Scripting Wget takes a long time to complete Post 302889915 by ahamed101 on Monday 24th of February 2014 12:16:53 PM
Old 02-24-2014
You see the connection timeout, thats a problem. It is not able to connect in the first place. Try increasing the timeout.
Normally how long does it take to start transferring the file once you issue the command?

--ahamed
 

10 More Discussions You Might Find Interesting

1. Programming

fwrite takes extremely long time

After my previous thread, I think I found out what causes the long delays. I run this program on several Linux computers, and the sometimes (after the file with the arrays becomes big) the fwrite takes between 100 ms to 900 ms. This is very bad for me, as I want a timer to halt each 30 ms.... ... (5 Replies)
Discussion started by: inna
5 Replies

2. Shell Programming and Scripting

shell script takes long time to complete

Hi all, I wrote this shell script to validate filed numbers for input file. But it take forever to complete validation on a file. The average speed is like 9mins/MB. Can anyone tell me how to improve the performance of a shell script? Thanks (12 Replies)
Discussion started by: ozzman
12 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 for Dummies Questions & Answers

time how long it takes to load a module

Hello, like the title says, how can i measure the time it takes to load a module in Linux, and how how can i measure the time it takes to load a statically compiled module. /Best Regards Olle ---------- Post updated at 01:13 PM ---------- Previous update was at 11:54 AM ---------- For... (0 Replies)
Discussion started by: ollebanan
0 Replies

5. 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

6. Shell Programming and Scripting

sort takes a long time

Dear experts I have a 200MG text file in this format: text \tab number I try to sort using options -fd and it takes very long! is that normal or I can speed it up in some ways? I dont want to split the file since this one is already splitted. I use this command: sort -fd file >... (12 Replies)
Discussion started by: voolek
12 Replies

7. 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

8. UNIX for Advanced & Expert Users

Find command takes too long to complete

Hi, Below is my find command find /opt/app/websphere -name myfolder -perm -600 | wc -l At time it even takes 20 mins to complete. my OS is : SunOS mypc 5.10 Generic_150400-09 sun4v sparc SUNW,T5440 (10 Replies)
Discussion started by: mohtashims
10 Replies

9. Shell Programming and Scripting

Script takes too long to complete

Hi, I have a lengthy script which i have trimmed down for a test case as below. more run.sh #!/bin/bash paths="allpath.txt" while IFS= read -r loc do echo "Working on $loc" startdir=$loc find "$startdir" -type f \( ! -name "*.log*" ! -name "*.class*" \) -print | while read file do... (8 Replies)
Discussion started by: mohtashims
8 Replies

10. Shell Programming and Scripting

Checking for substring in a loop takes too long to complete.

I need to check if the files returned by ls command in the below script is a sub-string of the argument passed to the script i.e $1 The below script works fine but is too slow. If the ls command take 12 secs to complete printing all files with while loop then; using posix substring check... (6 Replies)
Discussion started by: mohtashims
6 Replies
cimserver(8)						      System Manager's Manual						      cimserver(8)

NAME
cimserver - start or stop the CIM Server; display the version number or running status of the CIM Server SYNOPSIS
cimserver [configProperty=value] ... cimserver -s [ shutdownTimeout = value ] cimserver -v cimserver -h cimserver --help cimserver --version cimserver --status Remarks This command can only be executed by a privileged user. DESCRIPTION
The cimserver command provides a command line interface to stop and start the CIM Server, as well as to display the version number or run- ning status of the CIM Server. After installation, the CIM Server must be started using the cimserver command. If the system is rebooted, the CIM Server will automati- cally restart, with the exception of the case where the CIM Server was shutdown prior to the reboot. Generally, once the CIM Server is started, it is expected to be always running and ready to serve CIM requests. However, if the CIM Server must be stopped and restarted, the cimserver command can be used to shutdown the CIM Server gracefully and restart it at a later time. Starting the CIM Server Issuing the cimserver command without any options starts the CIM Server process. When starting the CIM Server using the cimserver command, the <configProperty=value> syntax can be used to set the configuration properties to be used by the CIM Server. It is important to know that the values specified in the cimserver command apply only to the current CIM Server process that gets started. The default values for the configuration properties do not change. For a list of the CIM Server config- uration properties, see the man page for the cimconfig command. Shutting down the CIM Server Issuing the cimserver command with the -s option stops the CIM Server. Optionally, a timeout value can be specified by setting the shut- downTimeout configuration property. Under normal operation, CIM Server should be able to be shutdown fairly quickly without problem. There are, however, situations that may prevent CIM Server from shutting down within a reasonable amount of time. For example, a provider that is not responding to requests, or a provider that is servicing a long-running CIM request. To handle such situations and to ensure that the CIM Server can be shutdown without having the user wait a long period of time (or indefinitely), a shutdown timeout value is used. The shutdown timeout value is the maximum amount of time (in seconds) the user is willing to wait for the CIM Server to complete all the outstanding CIM operation requests before shutting down the CIM Server. If the specified shutdown timeout period expires, the CIM Server will be shutdown even if there are CIM operations in progress. The shutdown timeout value is a CIM Server configuration property (shut- downTimeout ) that can be changed using the command. The default shutdown timeout value is 10 seconds. A timeout value (in seconds) can be specified in the cimserver command to shutdown the CIM Server using the =value> syntax. This overrides the default shutdown timeout value. The minimum timeout value is 2 seconds. While CIM Server is shutting down, a client connection request will result in a connection error (the same as if the CIM Server were not running). For clients who have already established a connection to the CIM Server, new CIM requests will be rejected with a CIM error indicating that the CIM Server is shutting down. When a client receives a response containing a CIM error indicating that the CIM Server is shutting down, it should close the connection and reconnect to CIM Server at a later time. Options The cimserver command recognizes the following options: -v, --version Display the version number or running status of the CIM Server. -h, --help Display the command usage. --status Display the running status of the CIM Server. -s Stop the CIM Server. Specify the timeout value for shutting down the CIM Server. This can only be used in conjunction with the -s option. The minimum timeout value is 2 seconds. If this is not specified, the default configurable timeout value will be used. configProperty=value Set the value for the specified configuration property to be used in starting the CIM Server. EXIT STATUS
The cimserver command returns one of the following values: 0 Success 1 Error The cimserver --status command returns one of the following values: 0 The CIM Server is running 1 Error 2 The CIM Server is not running When an error occurs, an error message is written to stderr and an error value of 1 is returned. DIAGNOSTICS
unable to connect to CIM Server. CIM Server may not be running. The cimserver command was issued to stop the CIM Server when CIM Server was not running. An exit status value of 1 is returned. Error: Bind failed: Failed to bind socket. The cimserver command was issued to start the CIM Server and the CIM Server was already running. An exit status value of 1 is returned. EXAMPLES
Stop the CIM Server with the default timeout value of 10 seconds. cimserver -s Stop the CIM Server with a timeout value of 5 seconds. cimserver -s shutdownTimeout=5 Start the CIM Server. cimserver Start the CIM Server with the configuration property enableNamespaceAuthorization set to true. cimserver enableNamespaceAuthorization=true Display the version number of the CIM Server. This version number is used to identify the release version of the CIM Server in the OpenPe- gasus release. cimserver -v Display the command usage. cimserver -h SEE ALSO
cimconfig(8). cimserver(8)
All times are GMT -4. The time now is 04:18 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy