Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 16 Aug 2014 16:54:46 +0200
From:      Polytropon <freebsd@edvax.de>
To:        Peter Ulrich Kruppa <ulrich@pukruppa.de>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: sh stdout/stderr redirection problem
Message-ID:  <20140816165446.db6aefc6.freebsd@edvax.de>
In-Reply-To: <53EF6979.2080708@pukruppa.de>
References:  <53EF6979.2080708@pukruppa.de>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 16 Aug 2014 16:23:53 +0200, Peter Ulrich Kruppa wrote:
> Hi,
> 
> I have got a python3.4 script which I can start from an rc.d script as a
> daemon this way:
> 	
>   daemon -p /var/run/my.pid /path/to/python3.4 /path/to/myscript.py
> 
> 
> /path/to/python3.4 /path/to/myscript.py produces interesting messages on
> stdout and stderr, so I would like to collect them in /var/log/my.log .
> I have tried all kinds of combinations of >>'s and 2>&1's but either I
> catch daemon's output which is nothing or the script won't start anymore.
> 
> Any ideas? - Thanks for your help

Idea:

	# ( daemon -p /var/run/my.pid /path/to/python3.4 /path/to/myscript.py ) > /tmp/myscript.log 2>&1

You can use ( ... ) to "summarize" subshell outputs, but in
your case using _script_ is probably the easiest method. It
will capture all output written to the terminal (stdout and
stderr). See "man script" for details.



-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140816165446.db6aefc6.freebsd>