[Buildbot-commits] buildbot/docs buildbot.texinfo,1.40,1.41

[Brian Warner]

Update of /cvsroot/buildbot/buildbot/docs
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv21234/docs

Modified Files:
	buildbot.texinfo 
Log Message:
* buildbot/scripts/sample.cfg: add python-mode declaration for
vim. Thanks to John Pye for the patch.

* docs/buildbot.texinfo (Launching the daemons): fix @reboot job
command line, mention the importance of running 'crontab' as the
buildmaster/buildslave user. Thanks to John Pye for the catch.


Index: buildbot.texinfo
===================================================================
RCS file: /cvsroot/buildbot/buildbot/docs/buildbot.texinfo,v
retrieving revision 1.40
retrieving revision 1.41
diff -u -d -r1.40 -r1.41
--- buildbot.texinfo	13 Mar 2006 09:29:57 -0000	1.40
+++ buildbot.texinfo	17 Mar 2006 01:07:08 -0000	1.41
@@ -803,12 +803,21 @@
 
 Once you get everything running, you will want to arrange for the
 buildbot daemons to be started at boot time. One way is to use
- at code{cron}, by putting them in a @@reboot crontab entry:
+ at code{cron}, by putting them in a @@reboot crontab entry at footnote{this
+@@reboot syntax is understood by Vixie cron, which is the flavor
+usually provided with linux systems. Other unices may have a cron that
+doesn't understand @@reboot}:
 
 @example
-@@reboot buildbot @var{BASEDIR}
+@@reboot buildbot start @var{BASEDIR}
 @end example
 
+When you run @command{crontab} to set this up, remember to do it as
+the buildmaster or buildslave account! If you add this to your crontab
+when running as your regular account (or worse yet, root), then the
+daemon will run as the wrong user, quite possibly as one with more
+authority than you intended to provide.
+
 It is important to remember that the environment provided to cron jobs
 and init scripts can be quite different that your normal runtime.
 There may be fewer environment variables specified, and the PATH may