[
https://issues.apache.org/jira/browse/CLOUDSTACK-8840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14747165#comment-14747165
]
ASF GitHub Bot commented on CLOUDSTACK-8840:
--------------------------------------------
Github user wido commented on the pull request:
https://github.com/apache/cloudstack/pull/820#issuecomment-140676140
@bhaisaab Tnx! I tested it on a CentOS 7 system:
```
[root@vm-d818122e-51ca-479f-9618-051b4eed7c10 system]# systemctl status
cloudstack-usage
cloudstack-usage.service - CloudStack Usage Server
Loaded: loaded (/etc/systemd/system/cloudstack-usage.service; disabled)
Active: active (running) since wo 2015-09-16 10:38:48 CEST; 3s ago
Docs: http://www.cloudstack.org/
Main PID: 2492 (sh)
CGroup: /system.slice/cloudstack-usage.service
```
@remibergsma Can you verify if the packages now build properly? I would
love to get this into 4.6 so that we are systemdified :)
> Update systemd profile for usage server
> ---------------------------------------
>
> Key: CLOUDSTACK-8840
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8840
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Usage
> Reporter: Wido den Hollander
> Assignee: Wido den Hollander
> Labels: systemd
> Fix For: 4.6.0
>
>
> Currently there is a systemd profile for the usage server, but it is not
> packaged properly and can be improved much.
> We should align this with the Agent systemd profile.
> In /usr/libexec/cloudstack there should be a wrapper which does the actual
> Java invoke and the wrapper is invoked by systemd.
> Output of the usage server should go to stdout as well so it is catched by
> journalctl.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
