[
https://issues.apache.org/jira/browse/TS-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
George Paul updated TS-20:
--------------------------
Attachment: TS-20_patch1.diff
This patch 'TS-20_patch1.diff' allows Traffic Server processes (TC,TM&TS) to be
started & stopped. Example Usage is:
Start:
sudo /usr/local/bin/trafficserver start
Stop:
sudo /usr/local/bin/trafficserver stop
patch -p0 -i TS-20_patch1.diff
Has been tested on Ubuntu8.04 and Fedora11.
Please review and let me know if there are any issues.
cheers,
-George
> server.lock location disagreement
> ---------------------------------
>
> Key: TS-20
> URL: https://issues.apache.org/jira/browse/TS-20
> Project: Traffic Server
> Issue Type: Bug
> Components: Build
> Affects Versions: 2.0.0a
> Environment: linux
> Reporter: John Plevyak
> Assignee: George Paul
> Attachments: TS-20_patch1.diff
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> The /usr/local/bin/trafficserver script starts up traffic_server and then
> checks /usr/local/var/trafficserver/internal/server.lock
> for the PID of the process. This is indeed where traffic_cop puts the PID,
> but unfortunately not where traffic_server puts
> the PID which is /usr/local/var/trafficserver/server.lock. This causes the
> trafficserver script to fail.
> Either traffic_cop (and I think traffic_manager if that is used) should put
> the lock in /usr/local/var/trafficserver/server.lock
> and the script should check there or traffic_server should put it in
> /usr/local/var/trafficserver/server.lock in standalone
> mode or the standalone mode location should be
> /usr/local/var/trafficserver/internal/server.lock or perhaps the script
> should start traffic_cop.
> The 'internal' directory also doesn't exist after install which may or may
> not be a problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
