[jira] Commented: (TS-165) Config files (records.config at least) can get wrong ownership

["Leif Hedstrom (JIRA)" <ji...@apache.org>]

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

Leif Hedstrom commented on TS-165:
----------------------------------

The issue is definitely reproducible as above (I tried on Ubuntu), and in step 3 all I have to change is the port from 8080 to 80.

> Config files (records.config at least) can get wrong ownership
> --------------------------------------------------------------
>
>                 Key: TS-165
>                 URL: https://issues.apache.org/jira/browse/TS-165
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Config
>            Reporter: Leif Hedstrom
>             Fix For: 2.0.0a
>
>
> With the following steps, I get records.config to become owned by root, when it should stay owned by nobody:
> (04:43:38 PM) zwoop: Ok, so this reproduces it every time on my fedora box, gonna try it on ubuntu next
> (04:44:41 PM) zwoop: This is what I did
> (04:44:41 PM) zwoop: 1) rm -rf local
> (04:44:41 PM) zwoop: 2) sudo gmake install
> (04:44:41 PM) zwoop: 3) emacs local/etc/trafficserver/records.config
> (04:44:41 PM) zwoop:      change port from 8080 to 80, and change eth0 to eth1 (I have to do the later, or it'll fail)
> (04:44:41 PM) zwoop: 4) local/bin/trafficserver start
> (04:44:41 PM) zwoop: 5) Wait 10-20 seconds (at least, maybe longer)
> (04:44:41 PM) zwoop: 6) ls -lrt local/etc/trafficserver

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.