Login or Register to Ask a Question and Join Our Community


Shell Programming and Scripting

Handling Stdout&StdErr for background jobs.

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Top Forums Shell Programming and Scripting Handling Stdout&StdErr for background jobs.
# 1  
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.
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

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

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

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

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

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

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

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

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

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

10. 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
Login or Register to Ask a Question

LEARN ABOUT DEBIAN

startfluxbox

STARTFLUXBOX(1) 						  Fluxbox Manual						   STARTFLUXBOX(1)

NAME

       startfluxbox - start a fluxbox session

SYNOPSIS

       startfluxbox

DESCRIPTION

       startfluxbox is a script which runs the file ~/.fluxbox/startup If it doesn't exist it will be generated.

       startfluxbox should be started from your ~/.xinitrc if you use startx, or ~/.xsession if you run a display manager, like xdm.

FILES

       ~/.fluxbox/startup
	   This file contains all commands that should be executed before fluxbox is started. The initial file contains helpful comments for
	   beginners. It also starts fluxbox.

EXAMPLES

       The default ~/.fluxbox/startup is as follows:

	   #!/bin/sh
	   #
	   # fluxbox startup-script:
	   #
	   # Lines starting with a '#' are ignored.

	   # Change your keymap:
	   xmodmap "$HOME/.Xmodmap"

	   # Applications you want to run with fluxbox.
	   # MAKE SURE THAT APPS THAT KEEP RUNNING HAVE AN ''&'' AT THE END.
	   #
	   # unclutter -idle 2 &
	   # wmnd &
	   # wmsmixer -w &
	   # idesk &

	   # And last but not least we start fluxbox.
	   # Because it is the last app you have to run it with ''exec'' before it.

	   exec fluxbox
	   # or if you want to keep a log:
	   # exec fluxbox -log "$fluxdir/log"

       If you need to start applications after fluxbox, you can change the exec fluxbox line above to something like this:

	   exec fluxbox &
	   fbpid=$!

	   sleep 1
	   {
		   xsetroot -cursor_name left_ptr -fg white -bg black &
		   ipager &
		   gkrellm2 &
	   } &

	   wait $fbpid

       So xsetroot, ipager, and gkrellm2 will all be started after fluxbox, after giving fluxbox 1 second to startup.

       For more details on what else you can do in this script, see sh(1), or the documentation for your shell.

AUTHORS

       The author of startfluxbox(1) is Han Boetes <han at fluxbox.org>

       This manpage was converted to asciidoc format by Jim Ramsay <i.am at jimramsay.com> for fluxbox-1.1.2

SEE ALSO

       fluxbox(1)

AUTHOR

       Jim Ramsay <i.am@jimramsay.com>
	   Author.

startfluxbox.txt						  28 October 2011						   STARTFLUXBOX(1)