Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #34624 > unrolled thread
| Started by | peter <pjmakey2@gmail.com> |
|---|---|
| First post | 2012-12-11 11:45 -0300 |
| Last post | 2012-12-11 11:45 -0300 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: forking and avoiding zombies! peter <pjmakey2@gmail.com> - 2012-12-11 11:45 -0300
| From | peter <pjmakey2@gmail.com> |
|---|---|
| Date | 2012-12-11 11:45 -0300 |
| Subject | Re: forking and avoiding zombies! |
| Message-ID | <mailman.731.1355237647.29569.python-list@python.org> |
On 12/11/2012 10:57 AM, andrea crotti wrote:
> where in [] I have the PID of the process.
> In this suggested way I should use some other files as standard output
> and error, but for that I already have the logging module that logs
> in the right place..
It's not realy neccesary do use the stderr and stdout parameters, in
fact the default value for those parameters are null ('/dev/null').
The functionality is like this.
All you print to stdout going to be in the stdout parameter of the
daemon function, and the same thing for stderr.
Now my suggestion for you, is you already have initialize a "logging
file", just use the logging module to redirect informacion what's is
doing your forked function, and use the stderr paramater of the daemon
function to DEBUG errors in the forked function.
Back to top | Article view | comp.lang.python
csiph-web