Sponsored Content
Top Forums Shell Programming and Scripting Rm -rf is taking very long, will it timeout? Post 302902678 by phpchick on Wednesday 21st of May 2014 03:19:51 PM
Old 05-21-2014
Quote:
Originally Posted by Perderabo
This has happened to me on several occasions. Not a timeout per se, but the connection drops or something like that. There are ways to make the the rm process nearly immortal. But I simply reconnect and restart the command. The files that were deleted do not come back... they stay gone. So you don't lose any progress.
did this, only took a couple of tries
 

10 More Discussions You Might Find Interesting

1. Red Hat

login process taking a long time

I'm having a bit of a login performance issue.. wondering if anyone has any ideas where I might look. Here's the scenario... Linux Red Hat ES 4 update 5 regardless of where I login from (ssh or on the text console) after providing the password the system seems to pause for between 30... (4 Replies)
Discussion started by: retlaw
4 Replies

2. Shell Programming and Scripting

For Loop Taking Too Long

I'm new from UNIX scripting. Please help. I have about 10,000 files from the $ROOTDIR/scp/inbox/string1 directory to compare with the 50 files from /$ROOTDIR/output/tma/pnt/bad/string1/ directory and it takes about 2 hours plus to complete the for loop. Is there a better way to re-write the... (5 Replies)
Discussion started by: hanie123
5 Replies

3. UNIX for Advanced & Expert Users

Comparison and For Loop Taking Too Long

I'd like to 1. Check and compare the 10,000 pnt files contains single record from the /$ROOTDIR/scp/inbox/string1 directory against 39 bad pnt files from the /$ROOTDIR/output/tma/pnt/bad/string1 directory based on the fam_id column value start at position 38 to 47 from the record below. Here is... (1 Reply)
Discussion started by: hanie123
1 Replies

4. UNIX for Dummies Questions & Answers

gref -f taking long time for big file

grep -f taking long time to compare for big files, any alternate for fast check I am using grep -f file1 file2 to check - to ckeck dups/common rows prsents. But my files contains file1 contains 5gb and file 2 contains 50 mb and its taking such a long time to compare the files. Do we have any... (10 Replies)
Discussion started by: gkskumar
10 Replies

5. UNIX for Dummies Questions & Answers

Job is taking long time

Hi , We have 20 jobs are scheduled. In that one of our job is taking long time ,it's not completing. If we are not terminating it's running infinity time actually the job completion time is 5 minutes. The job is deleting some records from the table and two insert statements and one select... (7 Replies)
Discussion started by: ajaykumarkona
7 Replies

6. Solaris

Re-sync Taking Extremely Long.

It's almost 3 days now and my resync/re-attach is only at 80%. Is there something I can check in Solaris 10 that would be causing the degradation. It's only a standby machine. My live system completed in 6hrs. (9 Replies)
Discussion started by: ravzter
9 Replies

7. Solaris

How to find out bottleneck if system is taking long time in gzip

Dear All, OS = Solaris 5.10 Hardware Sun Fire T2000 with 1 Ghz quode core We have oracle application 11i with 10g database. When ever i am trying to take cold backup of database with 55GB size its taking long time to finish. As the application is down nobody is using the server at all... (8 Replies)
Discussion started by: yoojamu
8 Replies

8. UNIX for Dummies Questions & Answers

ls is taking long time to list

Hi, All the data are kept on Netapp using NFS. some directories are so fast when doing ls but few of them are slow. After doing few times, it becomes fast. Then again after few minutes, it becomes slow again. Can you advise what's going on? This one directory I am very interested is giving... (3 Replies)
Discussion started by: samnyc
3 Replies

9. Shell Programming and Scripting

While loop problem taking too long

while read myhosts do while read discovered do echo "$discovered" done < $LOGFILE | grep -Pi "|" | egrep... (7 Replies)
Discussion started by: SkySmart
7 Replies

10. Shell Programming and Scripting

Timeout to abolish ssh connection command it takes too long

Hi, I am running a ssh connection test in a script, how can I add a timeout to abolish the process if it takes too long? ssh -i ~/.ssh/ssl_key useraccount@computer1 Thank you. - j (1 Reply)
Discussion started by: hce
1 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 09:52 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy