[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14791754#comment-14791754
 ] 

ASF subversion and git services commented on CLOUDSTACK-8840:
-------------------------------------------------------------

Commit a5ca762acb4e0a8b27f11aa3515558b87e8fdb18 in cloudstack's branch 
refs/heads/master from [~widodh]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a5ca762 ]

Merge pull request #820 from wido/CLOUDSTACK-8840

CLOUDSTACK-8840: Systemd service for the Usage ServerThere already was a 
uncompleted systemd service file for the Usage
Server.

This new one replaces sysvinit and the old systemd service file.

* pr/820:
  CLOUDSTACK-8840: Do not include old systemd wrapper
  CLOUDSTACK-8840: Fix the source path of the service file
  CLOUDSTACK-8840: Systemd service for the Usage Server

Signed-off-by: Wido den Hollander <[email protected]>


> 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)

Reply via email to