10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
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... (5 Replies)
Discussion started by: phpchick
5 Replies
2. UNIX and Linux Applications
One of my job is taking long running time.
I need to identify from the unix log file can you please help how to troubleshoot. (1 Reply)
Discussion started by: Nsharma3006
1 Replies
3. 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
4. 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
5. 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
6. 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
7. Shell Programming and Scripting
Hi,
I have here a script which is used to purge older files/directories based on defined purge period. The script consists of 45 find commands, where each command will need to traverse through more than a million directories. Therefore a single find command executes around 22-25 mins... (7 Replies)
Discussion started by: sravicha
7 Replies
8. 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
9. 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
10. UNIX for Dummies Questions & Answers
Hi peeps,
We are having around 60 users.
The time set to retrieve the mail is 300 sec.
But it's taking around 1 hour to deliver mails.
I am using debian sarge 3.1.
any clues?
And how it will affect if I decrease the time?
My machine has got 1 p4 3.0 GHZ processor and 1 GB ram.
The home... (2 Replies)
Discussion started by: squid04
2 Replies
condor_userlog(1) General Commands Manual condor_userlog(1)
Name
condor_userlog Display - and summarize job statistics from job log files.
Synopsis
condor_userlog [-help] [-total | -raw] [-debug] [-evict] [-j cluster | cluster.proc] [-all] [-hostname] logfile ...
Description
condor_userlog parses the information in job log files and displays summaries for each workstation allocation and for each job. See the
manual page for condor_submiton page for instructions for specifying that Condor write a log file for your jobs.
If -totalis not specified, condor_userlogwill first display a record for each workstation allocation, which includes the following informa-
tion:
Job
The cluster/process id of the Condor job.
Host
The host where the job ran. By default, the host's IP address is displayed. If -hostnameis specified, the host name will be displayed
instead.
Start Time
The time (month/day hour:minute) when the job began running on the host.
Evict Time
The time (month/day hour:minute) when the job was evicted from the host.
Wall Time
The time (days+hours:minutes) for which this workstation was allocated to the job.
Good Time
The allocated time (days+hours:min) which contributed to the completion of this job. If the job exited during the allocation, then this
value will equal ``Wall Time.'' If the job performed a checkpoint, then the value equals the work saved in the checkpoint during this
allocation. If the job did not exit or perform a checkpoint during this allocation, the value will be 0+00:00. This value can be greater
than 0 and less than ``Wall Time'' if the application completed a periodic checkpoint during the allocation but failed to checkpoint
when evicted.
CPU Usage
The CPU time (days+hours:min) which contributed to the completion of this job.
condor_userlogwill then display summary statistics per host:
Host/Job
The IP address or host name for the host.
Wall Time
The workstation time (days+hours:minutes) allocated by this host to the jobs specified in the query. By default, all jobs in the log are
included in the query.
Good Time
The time (days+hours:minutes) allocated on this host which contributed to the completion of the jobs specified in the query.
CPU Usage
The CPU time (days+hours:minutes) obtained from this host which contributed to the completion of the jobs specified in the query.
Avg Alloc
The average length of an allocation on this host (days+hours:minutes).
Avg Lost
The average amount of work lost (days+hours:minutes) when a job was evicted from this host without successfully performing a checkpoint.
Goodput
This percentage is computed as Good Time divided by Wall Time.
Util.
This percentage is computed as CPU Usage divided by Good Time.
condor_userlogwill then display summary statistics per job:
Host/Job
The cluster/process id of the Condor job.
Wall Time
The total workstation time (days+hours:minutes) allocated to this job.
Good Time
The total time (days+hours:minutes) allocated to this job which contributed to the job's completion.
CPU Usage
The total CPU time (days+hours:minutes) which contributed to this job's completion.
Avg Alloc
The average length of a workstation allocation obtained by this job in minutes (days+hours:minutes).
Avg Lost
The average amount of work lost (days+hours:minutes) when this job was evicted from a host without successfully performing a checkpoint.
Goodput
This percentage is computed as Good Time divided by Wall Time.
Util.
This percentage is computed as CPU Usage divided by Good Time.
Finally, condor_userlogwill display a summary for all hosts and jobs.
Options
-help
Get a brief description of the supported options
-total
Only display job totals
-raw
Display raw data only
-debug
Debug mode
-j
Select a specific cluster or cluster.proc
-evict
Select only allocations which ended due to eviction
-all
Select all clusters and all allocations
-hostname
Display host name instead of IP address
General Remarks
Since the Condor job log file format does not contain a year field in the timestamp, all entries are assumed to occur in the current year.
Allocations which begin in one year and end in the next will be silently ignored.
Exit Status
condor_userlogwill exit with a status value of 0 (zero) upon success, and it will exit with the value 1 (one) upon failure.
Author
Condor Team, University of Wisconsin-Madison
Copyright
Copyright (C) 1990-2012 Condor Team, Computer Sciences Department, University of Wisconsin-Madison, Madison, WI. All Rights Reserved.
Licensed under the Apache License, Version 2.0.
See the Condor Version 7.8.2 Manualor http://www.condorproject.org/licensefor additional notices. condor-admin@cs.wisc.edu
September 2012 condor_userlog(1)