10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi Experts,
I am facing one problem here which is one process always stuck in running state which causes the other similar process to sleep state . This causes my system in hanged state.
On doing cat /proc/<pid>wchan showing the "__init_begin" in the output.
Can you please help me here... (6 Replies)
Discussion started by: naveeng
6 Replies
2. UNIX for Advanced & Expert Users
Hi Experts,
I am facing one problem here which is one process always stuck in running state which causes the other similar process to sleep state . This causes my system in hanged state.
On doing cat /proc/<pid>wchan showing the "__init_begin" in the output.
Can you please help me here... (1 Reply)
Discussion started by: naveeng
1 Replies
3. BSD
Hi Experts,
I am facing one problem here which is one process always stuck in running state which causes the other similar process to sleep state . This causes my system in hanged state.
On doing cat /proc/<pid>wchan showing the "__init_begin" in the output.
Can you please help me here... (0 Replies)
Discussion started by: naveeng
0 Replies
4. Shell Programming and Scripting
Hi, I have a parallelized Mathematica program that spans across 8 MathKernels processes running at 100% and one MathKernel (highlighted in blue) running at < 10% that controls the other 8. They look like this on the cluster:
https://www.unix.com/attachment.php?attachmentid=5111&stc=1&d=1381245618... (2 Replies)
Discussion started by: giovform
2 Replies
5. Shell Programming and Scripting
Hi,
How can i capture the running process for 2 hours.
Thanks in advance.:b: (1 Reply)
Discussion started by: sarathkumar
1 Replies
6. Shell Programming and Scripting
I had a script executing every hour to kill a process. I used loop rather than cron to execute it periodically. But now when I am trying to kill that sleep process of 1 hour its not getting killed. it is taking a new PID everytime I kill. To disable the script commenting is the only option... (1 Reply)
Discussion started by: nixhead
1 Replies
7. UNIX for Dummies Questions & Answers
Hello All,
I have a script which has a functionality to sleep for 300 seconds after it does some processing, so in the logs if i check after the 3 iteration of sleep it didn't write saying "sleeping for 300 seconds". I suspect putty would automatically terminate session as i cannot access it any... (1 Reply)
Discussion started by: Ariean
1 Replies
8. Shell Programming and Scripting
Hi
i want to print the time of a process in hours only..(or) in minutes only.Is there anyway to print the process such like that
when i give the commnand like following
#ps -eo pid,time
PID TIME
412 01:49:32
481 00:03
it shows in HH:MM:SS format:
Could anyone... (1 Reply)
Discussion started by: srikanthg
1 Replies
9. Shell Programming and Scripting
Hi All,
Here is my script:
sleep_time=`echo "9.6 * $num_servers"|bc| cut -d. -f1`
if ; then sleep_time=3600;fi
### Allow the compare script to kick in after 1 hour at the least
logger "Sleeping for $sleep_time seconds ...Will call compare.sh thereon" $act_log
sleep $sleep_time
#sleep... (3 Replies)
Discussion started by: ntgobinath
3 Replies
10. Shell Programming and Scripting
how to start a process and make it sleep for 5 mins and then kill that process (6 Replies)
Discussion started by: shrao
6 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)