Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Handling Stdout&StdErr for background jobs.
Top Forums Shell Programming and Scripting Handling Stdout&StdErr for background jobs. Post 302200929 by alvinbush on Friday 30th of May 2008 10:36:00 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

Continue here:

Handling Stdout&StdErr for background jobs.
 

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. Solaris

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 & ... (1 Reply)
Discussion started by: alvinbush
1 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 REDHAT

ncftpbatch

ncftpbatch(1)						      General Commands Manual						     ncftpbatch(1)

NAME

       ncftpbatch - Individual batch FTP job processor

SYNOPSIS

       ncftpbatch -d

       ncftpbatch -l

       ncftpbatch -D

OPTIONS

   Command line flags:
       -d      Begin  background  processing  of FTP jobs in the current user's $HOME/.ncftp/spool directory.  This returns immediately, because a
	       daemon process is spawned and ran in the background.

       -l      Lists the contents of the user's job queue.

       -D      This is like -d, except that the process does not become a daemon.

DESCRIPTION

       This program is responsible for processing background FTP requests.  It is normally only run by ncftp and not manually by  a  human  being,
       however you can run it to manually process the FTP job queue.

       The  jobs are spool files written to a user's $HOME/.ncftp/spool directory and have a special format and file-naming convention (which con-
       tains when the job is to be run).  ncftp runs this program when it needs to, but if the ncftpbatch daemon dies unexpectedly the	jobs  that
       are left in the queue will not be processed until another instance of ncftpbatch is run.

       ncftpget  and  ncftpput can also be used to submit jobs for batch processing, using those utilities' -b command-line flag.  If desired, you
       can also manually create the spool files although this procedure is not documented here (see the manual	page  for  ncftpspooler  for  more
       information on how to do that).

DIAGNOSTICS

       ncftpbatch  writes  to its own log file, the $HOME/.ncftp/spool/log file.  This file should be examined to determine if any ncftpbatch pro-
       cesses are actively working on jobs.

AUTHOR

       Mike Gleason, NcFTP Software (mgleason@ncftp.com).

SEE ALSO

       ncftp(1), ncftpput(1), ncftpget(1).

Software							       NcFTP							     ncftpbatch(1)
All times are GMT -4. The time now is 09:42 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy