<br><div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">No it's not a real problem, it's just that Twisted in general is very<br>clean, so....
</blockquote><div><br><br>I've kept things as clean as I can by adding the twistd option --logfile=same_as_LOG_DIR_LOG_FILE <br>
using your LOG_FILE example above. Additionally, adding the code to drop the initial log observer and a log service.<br>
<br>The twistd log then logs the three or four lines and then get's dropped after the tac code starts and hits the logobserver line. Then, the log defined in your tac starts up and takes over from there. It keeps the
twistd.log out of the picture. <br><br>
-rob<br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> Yes, but is that a problem ? In my case, the only visible things is a
<br>> twistd.log<br>> file next to other log files. Not really harmful.<br><br></blockquote></div><br>