Minor tidying of alert-tracks generation
Generate alert-tracks pid & log to default location

Deployment system should handle linking the original location to
wherever necessary on the specific platform.
Use correct site name for alert tracks log and pid

ENV[‘SITE’] can be specified for the crontab (and elsewhere) so
allow the option here too.
Ensure the log and pid directories exist

If the directories do not exist the daemon cannot start.
Create tmp/pids in capistrano shared directory

pids need to persist across deploys so that we can kill/restart running
processes on deployment
Add tmp/pids to example SHARED_DIRECTORIES config
Generate purge-varnish pid & log to default location

Deployment system should handle linking the original location to
wherever necessary on the specific platform.
Use correct site name for purge-varnish log and pid

Allows the log and pid file names to be set dynamically by the
config_files:convert_init_script rake task.

ENV[‘SITE’] can be specified to name the particular install – e.g.
rather than 'alaveteli' you might name the site 'foi' – so now the log
and pid files are created with the correct name rather than simply
'purge-varnish'
Ensure the log and pid directories exist

If the directories do not exist the daemon cannot start.
Merge branch 'alert-tracks-generator' into rails-3-develop