Changes between Version 57 and Version 58 of RunningBuildbotOnWindows

Timestamp:

09/16/11 08:39:18 (20 months ago)

Author:

philippem

Comment:

--

RunningBuildbotOnWindows

@@ -13 +13 @@
 For the remainder of this document we will assume python was installed in "`C:Python26`".  Please adjust accordingly if you install to a different path.
 
-Install python, pywin32, and Twisted for all users.  You will need to do this while logged in as the actual "Administrator" account, not as a regular user with Administrator privileges, because of the way filesystem permissions are inherited during egg installation. When running python setup.py, be sure to use the full path to the version of python you expect to run buildbot (It is ok to have multiple versions of python installed).  The pywin32 and Twisted installers will look up the registry key and know where to install to such that they work with the python you've installed.
+Install python, pywin32, and Twisted for all users.  You will need to do this while logged in as the actual "Administrator" account, not as a regular user with Administrator privileges, because of the way filesystem permissions are inherited during egg installation. The buildbot service itself need not be a privileged account (see below). When running python setup.py, be sure to use the full path to the version of python you expect to run buildbot (It is ok to have multiple versions of python installed).  The pywin32 and Twisted installers will look up the registry key and know where to install to such that they work with the python you've installed.
 
 Install Buildbot itself with
@@ -20 +20 @@
 C:python26python setup.py install
 }}}
-
-It does not need administrator rights to install.
 
 
@@ -107 +105 @@
 ==== Troubleshooting ====
 
-If you have any issues with the service installation or buildbot-as-a-service startup, you can see the actual problem using Windows' "Event Viewer".  It's under "Windows Logs" and then "Applications"; look for problems of type "Error" with a source of "Buildbot".  Please report any such errors when asking for help on the mailing list.
+If you have any issues with the service installation or buildbot-as-a-service startup, you can see the actual problem using Windows' "Event Viewer".  It's under "Windows Logs" and then "Applications"; look for problems of type "Error" with a source of "Buildbot".  Please report any such errors when asking for help on the mailing list. 
+
+If the buildbot service fails to start, but the script runs for the same user when logged in, it may be due to permissions that were in effect when the buildbot package and pre-requisites were installed. See "PreRequisites" above.