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

lircmd

LIRCMD(8)						  System Administration Utilities						 LIRCMD(8)

NAME

       lircmd - LIRC mouse daemon translates infrared signals into mouse events

SYNOPSIS

       lircmd [options] [config-file]

DESCRIPTION

       This  daemon  can  simulate a MouseSystems, IntelliMouse or IMPS/2 type mouse. It gets the received buttons from lircd and converts them to
       mouse events. To make this possible, lircmd needs a config file located in /etc/lircmd.conf. In this file you have to determine which  but-
       ton  from  which  remote causes a mouse move or a mouse button click.  You can also specify a special button which activates or deactivates
       the mouse mode.

       -h --help
	      display this message

       -v --version
	      display version

       -n --nodaemon
	      don't fork to background

       -u --uinput
	      generate Linux input events

OPTIONS

       If you provide the --nodaemon option lircmd won't fork to background.

       On Linux systems the --uinput option will enable automatic generation of Linux input events. lircmd will open /dev/input/uinput and  inject
       the simulated mouse events into the Linux kernel rather than creating the /dev/lircm device.

FILES

       lircmd will use syslogd to output error messages. It depends on your system configuration where they will show up.

DAEMONS

       lircd  and  lircmd are daemons. You should start them in some init script depending on your system. There are some example scripts for dif-
       ferent distributions in the contrib directory. lircmd has to be started after lircd as it connects to the socket lircd provides.

       If you start lircd or lircmd from your shell prompt you will usually get back immediately to the prompt. Often people think that  the  pro-
       gram has died. But this is not an error. lircd and lircmd are daemons. Daemons always run in background.

SEE ALSO

       The documentation for lirc is maintained as html pages. They are located under html/ in the documentation directory.

lircmd 0.9.0-pre1						   October 2010 							 LIRCMD(8)