You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by bhaisaab <gi...@git.apache.org> on 2015/10/28 06:51:18 UTC

[GitHub] cloudstack pull request: [4.5] CLOUDSTACK-9000: logrotate cloudsta...

GitHub user bhaisaab opened a pull request:

    https://github.com/apache/cloudstack/pull/993

    [4.5] CLOUDSTACK-9000: logrotate cloudstack-agent out and err logs

    Adds logrotate rules for cloudstack-agent.{err,out} log files
    
    cc @remibergsma @wido @wilderrodrigues and others

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/shapeblue/cloudstack 4.5-logrotate-kvm-agent-erroutlogs

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/993.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #993
    
----
commit bacf971220ea97e80ac2fcf28de3ed9a51749522
Author: Rohit Yadav <ro...@shapeblue.com>
Date:   2015-10-28T05:44:49Z

    CLOUDSTACK-9000: logrotate cloudstack-agent out and err logs
    
    Adds logrotate rules for cloudstack-agent.{err,out} log files
    
    Signed-off-by: Rohit Yadav <ro...@shapeblue.com>

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: [4.5] CLOUDSTACK-9000: logrotate cloudsta...

Posted by wido <gi...@git.apache.org>.
Github user wido commented on the pull request:

    https://github.com/apache/cloudstack/pull/993#issuecomment-151778493
  
    Why only RPM and not for DEB?
    
    Keep in mind though that with systemd this is no longer valid


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: [4.5] CLOUDSTACK-9000: logrotate cloudsta...

Posted by wido <gi...@git.apache.org>.
Github user wido commented on the pull request:

    https://github.com/apache/cloudstack/pull/993#issuecomment-151791418
  
    @bhaisaab With systemd we no longer write a out and err file. We did this with JSVC, but now it's send to stdout and stderr which is then picked up by journald.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: [4.5] CLOUDSTACK-9000: logrotate cloudsta...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

    https://github.com/apache/cloudstack/pull/993


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request: [4.5] CLOUDSTACK-9000: logrotate cloudsta...

Posted by bhaisaab <gi...@git.apache.org>.
Github user bhaisaab commented on the pull request:

    https://github.com/apache/cloudstack/pull/993#issuecomment-151790777
  
    @wido fixed now. Do you mean with systemd, there is no point in using logrotate?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---