You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Ramya Sunil (JIRA)" <ji...@apache.org> on 2012/05/18 23:45:06 UTC

[jira] [Created] (AMBARI-318) Do not install the packages that install init.d scripts

Ramya Sunil created AMBARI-318:
----------------------------------

             Summary: Do not install the packages that install init.d scripts
                 Key: AMBARI-318
                 URL: https://issues.apache.org/jira/browse/AMBARI-318
             Project: Ambari
          Issue Type: Bug
            Reporter: Ramya Sunil
            Assignee: Ramya Sunil


Since init.d scripts have hard coded paths for logs, users cant use the init.d scripts as it might mess with the locations for the logs on the mounted directories.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (AMBARI-318) Do not install the packages that install init.d scripts

Posted by "Matt Foley (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AMBARI-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13279266#comment-13279266 ] 

Matt Foley commented on AMBARI-318:
-----------------------------------

This is not the right answer.  SE's expect the init.d scripts to be available; Apple for instance.  The correct answer is get the change into BigTop so the log location respects the configuration.
                
> Do not install the packages that install init.d scripts
> -------------------------------------------------------
>
>                 Key: AMBARI-318
>                 URL: https://issues.apache.org/jira/browse/AMBARI-318
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Ramya Sunil
>            Assignee: Ramya Sunil
>         Attachments: AMBARI-318.patch
>
>
> Since init.d scripts have hard coded paths for logs, users cant use the init.d scripts as it might mess with the locations for the logs on the mounted directories.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (AMBARI-318) Do not install the packages that install init.d scripts

Posted by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMBARI-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinod Kumar Vavilapalli updated AMBARI-318:
-------------------------------------------

    Fix Version/s: 0.9.0
    
> Do not install the packages that install init.d scripts
> -------------------------------------------------------
>
>                 Key: AMBARI-318
>                 URL: https://issues.apache.org/jira/browse/AMBARI-318
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Ramya Sunil
>            Assignee: Ramya Sunil
>             Fix For: 0.9.0
>
>         Attachments: AMBARI-318.patch
>
>
> Since init.d scripts have hard coded paths for logs, users cant use the init.d scripts as it might mess with the locations for the logs on the mounted directories.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (AMBARI-318) Do not install the packages that install init.d scripts

Posted by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMBARI-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinod Kumar Vavilapalli updated AMBARI-318:
-------------------------------------------

    Affects Version/s: 0.9.0
    
> Do not install the packages that install init.d scripts
> -------------------------------------------------------
>
>                 Key: AMBARI-318
>                 URL: https://issues.apache.org/jira/browse/AMBARI-318
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 0.9.0
>            Reporter: Ramya Sunil
>            Assignee: Ramya Sunil
>             Fix For: 0.9.0
>
>         Attachments: AMBARI-318.patch
>
>
> Since init.d scripts have hard coded paths for logs, users cant use the init.d scripts as it might mess with the locations for the logs on the mounted directories.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (AMBARI-318) Do not install the packages that install init.d scripts

Posted by "Ramya Sunil (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMBARI-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ramya Sunil updated AMBARI-318:
-------------------------------

    Attachment: AMBARI-318.patch
    
> Do not install the packages that install init.d scripts
> -------------------------------------------------------
>
>                 Key: AMBARI-318
>                 URL: https://issues.apache.org/jira/browse/AMBARI-318
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Ramya Sunil
>            Assignee: Ramya Sunil
>         Attachments: AMBARI-318.patch
>
>
> Since init.d scripts have hard coded paths for logs, users cant use the init.d scripts as it might mess with the locations for the logs on the mounted directories.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira