On Aug 29, 2011, at 8:20 AM, Stephan wrote:

I still have the issue, but I've found out that it has something to do
with the fact that the twisted daemon isn't starting as the user I've
asked it to start as.

The --chuid flag to start-stop-daemon is not seen by twistd; twistd is started by start-stop-daemon allegedly already running as that user. If this is a bug, it's a bug in your platform's startup-management tools, not Twisted itself.

Note that os.environ['USER'] is informational only and does not represent the actual current user. Look at os.getuid() for the real number.