Sponsored Content
Top Forums UNIX for Dummies Questions & Answers attempting to break within function Post 67329 by tumblez on Tuesday 22nd of March 2005 03:10:19 PM
Old 03-22-2005
good idea

Good idea, I'll think about doing just that!
Thanks! Smilie
 

8 More Discussions You Might Find Interesting

1. IP Networking

Error with ifconfig when attempting to switch to 10baseT

In Darwin, when typing "ifconfig en0 media 10baseT/UTP mediaopt half-duplex" I recieve the error message "ifconfig: SIOCSIFMEDIA: Operation not permitted". The same thing occurs when I sudo the command. Any suggestions? Thanks... (1 Reply)
Discussion started by: tkarrde
1 Replies

2. Red Hat

attempting to install chkconfig 1.3.5

Hi there everyone, I'm using redhat 7.3 at the moment and am currently trying to install chkconfig-1.3.5-3.i386.rpm , but when I type this command: rpm -Uvh chkconfig-1.3.5-3.i386.rpm I get the following error: error: failed dependencies: chkconfig = 1.2.24 is needed by... (3 Replies)
Discussion started by: redhat_newb101
3 Replies

3. Solaris

Forcing OpenBoot: H/W Solution to no <BREAK> function on USB Serial

Please note: This solution does require some soldering ability. If, like me today, you really really need to get into OpenBoot on a non booting Solaris machine (in my case an Ultra 5) but your USB dongle won't send <BREAK> then here is a -really- simple hardware hack that works a treat: ... (0 Replies)
Discussion started by: HideawayStudio
0 Replies

4. Debian

attempting to boot from cd rom

i just installed Debian Lenny on HP DL380. After the server rebooted, it still asks for me to insert a cd rom. where can I exactly check the settings for the boot menu? Should it use the hard disk since I didnt insert any cd? pls advise (1 Reply)
Discussion started by: lhareigh890
1 Replies

5. Shell Programming and Scripting

BASH: Break line, read, break again, read again...

...when the lines use both a colon and commas to separate the parts you want read as information. The first version of this script used cut and other non-Bash-builtins, frequently, which made it nice and zippy with little more than average processor load in GNOME Terminal but, predictably, slow... (2 Replies)
Discussion started by: SilversleevesX
2 Replies

6. SuSE

Attempting to use AutoYaST with SLES11SP2

We currently have a setup with SLES11SP1 where we have an AutoYaST ISO set up for automated network installs. I'm attempting to port this to SP2 to make new installs current, but I'm running into a few problems. The process seems the same, and after running mkisofs to build a new SP2 ISO the... (0 Replies)
Discussion started by: Magus Zeal
0 Replies

7. Homework & Coursework Questions

C++ Attempting to modify this function to read from a (;) semi-colon-separated file

After some thought. I am uncomfortable issuing my professors name where, there may be unintended side effects from any negative responses/feedback. Willing to re post if I can omit school / professor publicly, but can message moderator for validation? I am here for knowledge and understanding,... (1 Reply)
Discussion started by: briandanielz
1 Replies

8. UNIX for Beginners Questions & Answers

Error attempting to run alsamixer

I am working on an embbeded system. On the system in /usr/bin there are a host of programs one of which is called alsamixer. I want to use this utility but whenever I try to run any alsamixer commands I get and error message: Error opening terminal: vt100 Anyone ever seen this error... (10 Replies)
Discussion started by: Circuits
10 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)
All times are GMT -4. The time now is 03:46 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy