Author: fw Date: 2012-03-25 18:58:29 +0000 (Sun, 25 Mar 2012) New Revision: 18762 Modified: doc/soler.txt Log: Clarifications for (re)starting the tracker service Modified: doc/soler.txt ==================================================================--- doc/soler.txt 2012-03-25 18:30:28 UTC (rev 18761) +++ doc/soler.txt 2012-03-25 18:58:29 UTC (rev 18762) @@ -41,12 +41,17 @@ mod_proxy is used to forward requests to the actual server which listens on 127.0.0.1:25648 and is started by the -/org/security-tracker.debian.org/website/bin/start-daemon script. +/org/security-tracker.debian.org/website/bin/start-daemon script +(using a @reboot action in sectracker''s crontab). +To restart the security tracker service, kill the tracker_service.py +Python process and invoke the start-daemon process as the sectracker +user. + Logging ------- -Apche logs are stored in: +Apache logs are stored in: /var/log/apache2/security-tracker.debian.org.access.log /var/log/apache2/security-tracker.debian.org.error.log @@ -75,4 +80,5 @@ Updates to the Subversion checkout only affect the directory /org/security-tracker.debian.org/website/secure-testing/data. -Code changes need to be applied manually, using "svn update". +Code changes need to be applied manually, using "svn update", +and a service restart (see above).