From owner-freebsd-questions@FreeBSD.ORG  Sun Aug 17 07:44:25 2014
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 4E49CDEF
 for <freebsd-questions@freebsd.org>; Sun, 17 Aug 2014 07:44:25 +0000 (UTC)
Received: from pukruppa.de (pd95cabe3.dip0.t-ipconnect.de [217.92.171.227])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "pukruppa.de", Issuer "pukruppa.de" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id D031D2556
 for <freebsd-questions@freebsd.org>; Sun, 17 Aug 2014 07:44:24 +0000 (UTC)
Received: from pukruppa.de (localhost [127.0.0.1])
 by pukruppa.de (8.14.9/8.14.9) with ESMTP id s7H7iJOK058203
 for <freebsd-questions@freebsd.org>; Sun, 17 Aug 2014 09:44:20 +0200 (CEST)
 (envelope-from ulrich@pukruppa.de)
Message-ID: <53F05D53.3030001@pukruppa.de>
Date: Sun, 17 Aug 2014 09:44:19 +0200
From: Peter Ulrich Kruppa <ulrich@pukruppa.de>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: freebsd-questions@freebsd.org
Subject: [SOLVED] Re: sh stdout/stderr redirection problem
References: <53EF6979.2080708@pukruppa.de>
 <20140816165446.db6aefc6.freebsd@edvax.de>
In-Reply-To: <20140816165446.db6aefc6.freebsd@edvax.de>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Aug 2014 07:44:25 -0000

On 16.08.2014 16:54, Polytropon wrote:
> 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

After some playing around:

> Idea:
> 
> 	# ( daemon -p /var/run/my.pid /path/to/python3.4 /path/to/myscript.py ) > /tmp/myscript.log 2>&1
This doesn't work: it produces an empty logfile ...

> 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.
That's not "elegant" but it works for me. I have to use a long command

daemon -f -p /var/run/my.pid script -a /var/log/my.log \
/path/to/python3.4 /path/to/myscript.py

Thanks for your input!

Greetings

Peter