On 06:14 pm, d...@krondo.com wrote:
>On Tue, Aug 17, 2010 at 10:40 AM, wrote:
>>On 11:35 am, zoran.bosn...@sloveniacontrol.si wrote:
>>>I am running twisted application from /etc/init/myapp.conf by exec
>>>statement like this:
>>>exec /usr/bin/twistd --uid= --gid=
>>>--logfile=/var/log/dir/file
Yes Server.site does indeed take a logPath arg.
Now how can I amend my code so that I can see both sys.stdout and my log
file both being written at the same time?
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/c
On Tue, Aug 17, 2010 at 10:40 AM, wrote:
> On 11:35 am, zoran.bosn...@sloveniacontrol.si wrote:
>>I am running twisted application from /etc/init/myapp.conf by exec
>>statement like this:
>>exec /usr/bin/twistd --uid= --gid= --logfile=/var/log/dir/file
>>
>>The problem is when log file is first c
On 11:35 am, zoran.bosn...@sloveniacontrol.si wrote:
>I am running twisted application from /etc/init/myapp.conf by exec
>statement like this:
>exec /usr/bin/twistd --uid= --gid= --logfile=/var/log/dir/file
>
>The problem is when log file is first created under /var/log/dir (dir
>is
>owned by user
I am running twisted application from /etc/init/myapp.conf by exec
statement like this:
exec /usr/bin/twistd --uid= --gid= --logfile=/var/log/dir/file
The problem is when log file is first created under /var/log/dir (dir is
owned by user id), the owner of the file is 'root', not requested user.
As
You are currently considering your task from the viewpoint “let's make a
callback chain for the perfect workflow and alter this chain in case of
anything going wrong.” I think the flaw with this approach is that you are
trying to make your “ideal” flow work at all in situations where it would
On 8/17/10 6:24 AM, disappearedng wrote:
> Dear Everyone,
>
> I am running WSGI inside my twisted server. I am currently using
> startLogging, but I am interested in separating the two sources of
> logs into different destinations, i.e. different log files. Take a
> look at my log:
To the best o
On Aug 17, 2010, at 8:49 AM, Sergey Magafurov wrote:
> ... lots of text skipped ...
You are currently considering your task from the viewpoint “let's make a
callback chain for the perfect workflow and alter this chain in case of
anything going wrong.” I think the flaw with this approach is tha
