id	summary	reporter	owner	description	type	status	priority	milestone	version	resolution	keywords	cc
647	buildbot.tac specifies a relative path for twistd.log	dwlocks		"Buildbot's log file will be created in the current working directory of the parent process.  This is probably the behavior people expect.  It is what I expected.  It is a problem for init scripts, which have wacky hard to configure environments.

Twisted bug 2572 http://twistedmatrix.com/trac/ticket/2572 means that the current working directory for any code in buildbot.tac is not configurable with ""--rundir= "".  The executing environment must have the correct working directory.  Various flavors of Linux have different init tools with inconsistent options.  Maybe it's easy to specify the working directory for a daemon (Debian).  Maybe it's close to impossible (gentoo).

Is it reasonable to specify ""%(basedir)/twistd.log"" in buildbot.tac?

Or only specify %(basedir) if os.getcwd()=""/""

tickets #603 and #253 might be related"	defect	closed	major	0.8.0	0.7.11	fixed