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 DEBIAN

scriptmgr2

SCRIPTMGR(1)															      SCRIPTMGR(1)

NAME

       scriptmgr - utility for controlling other skytools scripts.

SYNOPSIS

       scriptmgr.py [switches] config.ini <command> [-a | job_name ... ]

DESCRIPTION

       scriptmgr is used to manage several scripts together. It discovers potential jobs based on config file glob expression. From config file it
       gets both job_name and service type (that is the main section name eg [cube_dispatcher]). For each service type there is subsection in the
       config how to handle it. Unknown services are ignored.

COMMANDS

   status
	   scriptmgr config.ini status

       Show status for all known jobs.

   start
	   scriptmgr config.ini start -a
	   scriptmgr config.ini start job_name1 job_name2 ...

       launch script(s) that are not running.

   stop
	   scriptmgr config.ini stop -a
	   scriptmgr config.ini stop job_name1 job_name2 ...

       stop script(s) that are running.

   restart
	   scriptmgr config.ini restart -a
	   scriptmgr config.ini restart job_name1 job_name2 ...

       restart scripts.

   reload
	   scriptmgr config.ini reload -a
	   scriptmgr config.ini reload job_name1 job_name2 ...

       Send SIGHUP to scripts that are running.

CONFIG

   Common configuration parameters
       job_name
	   Name for particulat job the script does. Script will log under this name to logdb/logserver. The name is also used as default for PgQ
	   consumer name. It should be unique.

       pidfile
	   Location for pid file. If not given, script is disallowed to daemonize.

       logfile
	   Location for log file.

       loop_delay
	   If continuisly running process, how long to sleep after each work loop, in seconds. Default: 1.

       connection_lifetime
	   Close and reconnect older database connections.

       log_count
	   Number of log files to keep. Default: 3

       log_size
	   Max size for one log file. File is rotated if max size is reached. Default: 10485760 (10M)

       use_skylog
	   If set, search for [./skylog.ini, ~/.skylog.ini, /etc/skylog.ini]. If found then the file is used as config file for Pythons logging
	   module. It allows setting up fully customizable logging setup.

   scriptmgr parameters
       config_list
	   List of glob patters for finding config files. Example:

	       config_list = ~/dbscripts/conf/*.ini, ~/random/conf/*.ini

   Service section parameters
       cwd
	   Working directory for script.

       args
	   Arguments to give to script, in addition to -d.

       script
	   Path to script. Unless script is in PATH, full path should be given.

       disabled
	   If this service should be ignored.

   Example config file
	   [scriptmgr]
	   job_name	   = scriptmgr_livesrv
	   logfile	   = ~/log/%(job_name)s.log
	   pidfile	   = ~/pid/%(job_name)s.pid

	   config_list	   = ~/scripts/conf/*.ini

	   # defaults for all service sections
	   [DEFAULT]
	   cwd = ~/scripts

	   [table_dispatcher]
	   script = table_dispatcher.py
	   args = -v

	   [cube_dispatcher]
	   script = python2.4 cube_dispatcher.py
	   disabled = 1

	   [pgqadm]
	   script = ~/scripts/pgqadm.py
	   args = ticker

COMMAND LINE SWITCHES

       Following switches are common to all skytools.DBScript-based Python programs.

       -h, --help
	   show help message and exit

       -q, --quiet
	   make program silent

       -v, --verbose
	   make program more verbose

       -d, --daemon
	   make program go background

       Following switches are used to control already running process. The pidfile is read from config then signal is sent to process id specified
       there.

       -r, --reload
	   reload config (send SIGHUP)

       -s, --stop
	   stop program safely (send SIGINT)

       -k, --kill
	   kill program immidiately (send SIGTERM)

       Options specific to scriptmgr:

       -a, --all
	   Operate on all non-disabled scripts.

								    03/13/2012							      SCRIPTMGR(1)
All times are GMT -4. The time now is 07:47 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy