Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Handling Stdout&StdErr for background jobs.
Operating Systems Solaris Handling Stdout&StdErr for background jobs. Post 302200928 by alvinbush on Friday 30th of May 2008 10:32:10 AM
Old 05-30-2008
Handling Stdout&StdErr for background jobs.
Hello Friends,

sorry, i am not very familiar with Unix programming. Could you please help me on this?

We have to start different components from a startup script.

each components are started as below in the background in a startprocess function

$nohup $file $args >>$logFile 2>&1 &

after this the script calls some waiting method and waits in the logfile for some particular string as below

if grep -c "$pattern" $logFile>1; then ....

and go ahead with the next component.


We have now the problem that the background jobs continue writing into the log file even after startup and covering the disk space.
I am looking for a way to redirect the stdout of the background jobs to dev/null immediately after finding the successful start entry in the log.



Thanks in advance,

Alvin
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

stderr & stdout to a file and the right exit code

Hi all, I need to redirect stdout and stderr to a file in a ksh shell. That's not a problem. But I need also the correct exit code for the executed command. In the example below I redirect correctly the stdout & stderr to a file, but I have the exit code of tee command and not for the mv... (2 Replies)
Discussion started by: up69
2 Replies

2. Shell Programming and Scripting

redirecting STDOUT & STDERR

In bash, I need to send the STDOUT and STDERR from a command to one file, and then just STDERR to another file. Doing one or the other using redirects is easy, but trying to do both at once is a bit tricky. Anyone have any ideas? (9 Replies)
Discussion started by: jshinaman
9 Replies

3. Shell Programming and Scripting

getting stderr & stdout output lively modified

This is about getting all output to stderr and stdout localized. Nothing to do with redirecting output to a file (there already are some interesting threads about that issue on this forum). What I intend to do is capturing all lines of text sent to the screen, compare them with an array of... (2 Replies)
Discussion started by: teo ramirez
2 Replies

4. UNIX for Advanced & Expert Users

combined stdout & stderr

Hello Everyone! I'm trying to combine output for standard output and for possible standard error to the log file. I was trying to use tee command, but it turned out if error occurred error output will be send to the screen only and will not be redirected with tee command to the log file. Anyone... (11 Replies)
Discussion started by: slavam
11 Replies

5. Shell Programming and Scripting

Redirecting STDERR message to STDOUT & file at same time

Friends I have to redirect STDERR messages both to screen and also capture the same in a file. 2 > &1 | tee file works but it also displays the non error messages to file, while i only need error messages. Can anyone help?? (10 Replies)
Discussion started by: vikashtulsiyan
10 Replies

6. Shell Programming and Scripting

Handling Stdout&StdErr for background jobs.

Hello Friends, sorry, i am not very familiar with Unix programming. Could you please help me on this? We have to start different components from a startup script. each components are started as below in the background in a startprocess function $nohup $file $args >>$logFile 2>&1 & ... (0 Replies)
Discussion started by: alvinbush
0 Replies

7. Linux

Can background process access to stdout,stderr

Hi folks :) Can deamonized process access to stderr, stdout? I 'm trying to display error_num/return value of a function run() in stderr using fprintf(stderr, "function run() returns = %d", ret_val); run() is called after deamonizing the process. (1 Reply)
Discussion started by: katty
1 Replies

8. Shell Programming and Scripting

Prepend TimeStamp to STDERR & STDOUT to a file

Currently I am redirecting STDERR and STDOUT to a log file by doing the following { My KSH script contents } 2>&1 | $DEBUGLOG Problem is the STDERR & STDOUT do not have any date/time associated. I want this to be something that i can embed into a script opposed to an argument I use... (4 Replies)
Discussion started by: nitrobass24
4 Replies

9. Shell Programming and Scripting

Redirect STDOUT & STDERR to file and then on screen

Dear all, redirecting STDOUT & STDERR to file is quite simple, I'm currently using: exec 1>>/tmp/tmp.log; exec 2>>/tmp/tmp.logBut during script execution I would like the output come back again to screen, how to do that? Thanks Lucas (4 Replies)
Discussion started by: Lord Spectre
4 Replies

10. Shell Programming and Scripting

Redirect STDOUT & STDERR to file and then on screen

Dear all, redirecting STDOUT & STDERR to file is quite simple, I'm currently using: Code: exec 1>>/tmp/tmp.log; exec 2>>/tmp/tmp.log But during script execution I would like the output come back again to screen, how to do that? Thanks Luc edit by bakunin: please use CODE-tags like the... (6 Replies)
Discussion started by: tmonk1
6 Replies

LEARN ABOUT DEBIAN

condor_wait

condor_wait(1)						      General Commands Manual						    condor_wait(1)

Name
       condor_wait Wait - for jobs to finish

Synopsis
       condor_wait [-help -version]

       condor_wait[-debug] [-wait seconds] [-num number-of-jobs] log-file[job ID]

Description
       condor_waitwatches  a  user  log file (created with the logcommand within a submit description file) and returns when one or more jobs from
       the log have completed or aborted.

       Because condor_waitexpects to find at least one job submitted event in the log file, at least one job must have been successfully submitted
       with condor_submitbefore condor_waitis executed.

       condor_waitwill wait forever for jobs to finish, unless a shorter wait time is specified.

Options
       -help

	  Display usage information

       -version

	  Display version information

       -debug

	  Show extra debugging information.

       -wait seconds

	  Wait no more than the integer number of seconds. The default is unlimited time.

       -num number-of-jobs

	  Wait for the integer number-of-jobsjobs to end. The default is all jobs in the log file.

       log file

	  The name of the log file to watch for information about the job.

       job ID

	  A  specific job or set of jobs to watch. If the job IDis only the job ClassAd attribute  ClusterId , then condor_wait waits for all jobs
	  with the given  ClusterId . If the job IDis a pair of the job ClassAd attributes, given by  ClusterId . ProcId , then condor_wait  waits
	  for  the specific job with this job ID. If this option is not specified, all jobs that exist in the log file when condor_wait is invoked
	  will be watched.

General Remarks
       condor_waitis an inexpensive way to test or wait for the completion of a job or a whole cluster, if you are trying to get a process outside
       of Condor to synchronize with a job or set of jobs.

       It can also be used to wait for the completion of a limited subset of jobs, via the -numoption.

Examples
       condor_wait  logfile

       This command waits for all jobs that exist in  logfile to complete.

       condor_wait  logfile 40

       This command waits for all jobs that exist in  logfile with a job ClassAd attribute  ClusterId of 40 to complete.

       condor_wait  -num 2 logfile

       This command waits for any two jobs that exist in  logfile to complete.

       condor_wait  logfile 40.1

       This command waits for job 40.1 that exists in  logfile to complete.

       condor_wait  -wait 3600 logfile 40.1

       This waits for job 40.1 to complete by watching	logfile , but it will not wait more than one hour (3600 seconds).

Exit Status
       condor_waitexits  with  0  if and only if the specified job or jobs have completed or aborted. condor_waitreturns 1 if unrecoverable errors
       occur, such as a missing log file, if the job does not exist in the log file, or the user-specified waiting time has expired.

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_wait(1)
All times are GMT -4. The time now is 05:07 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy