[Twisted-Python] odd problem with daemonization?
tv at twistedmatrix.com
Thu Mar 20 02:03:07 EST 2003
On Wed, Mar 19, 2003 at 12:02:46AM -0600, Glyph Lefkowitz wrote:
> The reason that you're having this problem is that on the C++ side of
> things, FD 0,1,2 are just normal FDs. This is due to the fact that we
> trap the sys.stdout _object_ in python, but we don't keep the
> file-descriptors around. The Transport of your Protocol is getting
> created after those FDs have been closed, and is therefore haplessly
> allocating the FD of stdout by chance.
Give up hope of being able to process the data written to fd 1
or 2 directly by the C part, and dup2 /dev/null to 0, 1 and 2?
More information about the Twisted-Python