05-21-2014
Rm -rf is taking very long, will it timeout?
I have so many (hundreds of thousands) files and directories within this one specific directory that my "rm -rf" command to delete them has been taking forever.
I did this via the SSH, my question is: if my SSH connection times out before rm -rf finishes, will it continue to delete all of those directories?
If not, what is the solution around this ?
10 More Discussions You Might Find Interesting
1. Red Hat
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
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
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
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
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
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
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
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 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
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
LEARN ABOUT DEBIAN
smokeping_probes_anotherssh
Smokeping_probes_AnotherSSH(3) SmokePing Smokeping_probes_AnotherSSH(3)
NAME
Smokeping::probes::AnotherSSH - Another SSH probe
SYNOPSIS
*** Probes ***
+AnotherSSH
forks = 5
offset = 50%
step = 300
# The following variables can be overridden in each target section
greeting = SSH-Latency-Measurement-Sorry-for-this-logmessage
interval = established
mininterval = 0.5
pings = 5
port = 22
timeout = 5
# [...]
*** Targets ***
probe = AnotherSSH # if this should be the default probe
# [...]
+ mytarget
# probe = AnotherSSH # if the default probe is something else
host = my.host
greeting = SSH-Latency-Measurement-Sorry-for-this-logmessage
interval = established
mininterval = 0.5
pings = 5
port = 22
timeout = 5
DESCRIPTION
Latency measurement using SSH. This generates Logfile messages on the other Host, so get permission from the owner first!
VARIABLES
Supported probe-specific variables:
forks
Run this many concurrent processes at maximum
Example value: 5
Default value: 5
offset
If you run many probes concurrently you may want to prevent them from hitting your network all at the same time. Using the probe-
specific offset parameter you can change the point in time when each probe will be run. Offset is specified in % of total interval, or
alternatively as 'random', and the offset from the 'General' section is used if nothing is specified here. Note that this does NOT
influence the rrds itself, it is just a matter of when data acqusition is initiated. (This variable is only applicable if the variable
'concurrentprobes' is set in the 'General' section.)
Example value: 50%
step
Duration of the base interval that this probe should use, if different from the one specified in the 'Database' section. Note that the
step in the RRD files is fixed when they are originally generated, and if you change the step parameter afterwards, you'll have to
delete the old RRD files or somehow convert them. (This variable is only applicable if the variable 'concurrentprobes' is set in the
'General' section.)
Example value: 300
Supported target-specific variables:
greeting
Greeting string to send to the SSH Server. This will appear in the Logfile. Use this to make clear, who you are and what you are doing
to avoid confusion.
Also, don't use something that is a valid version string. This probe assumes that the connection gets terminated because of protocol
mismatch.
Default value: SSH-Latency-Measurement-Sorry-for-this-logmessage
interval
The interval to be measured. One of:
connect
Interval between connect() and the greeting string from the host.
established
Interval between our greeting message and the end of the connection because of Protocol mismatch. This is the default.
complete
From connect() to the end of the connection.
Default value: established
mininterval
Minimum interval between the start of two connection attempts in (possibly fractional) seconds.
Default value: 0.5
pings
How many pings should be sent to each target, if different from the global value specified in the Database section. Note that the
number of pings in the RRD files is fixed when they are originally generated, and if you change this parameter afterwards, you'll have
to delete the old RRD files or somehow convert them.
Example value: 5
port
Connect to this port.
Default value: 22
timeout
Timeout for the connection.
Default value: 5
AUTHORS
Christoph Heine <Christoph.Heine@HaDiKo.DE>
2.6.8 2013-03-17 Smokeping_probes_AnotherSSH(3)