[jira] Commented: (TS-20) server.lock location disagreement

["George Paul (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TS-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803099#action_12803099 ] 

George Paul commented on TS-20:
-------------------------------

This patch 'TS-20_patch1.diff' has been committed to traffic server 'dev' branch.
-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.