[
https://issues.apache.org/jira/browse/ZOOKEEPER-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14588526#comment-14588526
]
Guillaume ALAUX commented on ZOOKEEPER-2095:
--------------------------------------------
This last service file uses shell scripts which must run zookeeper "as daemon"
(ie running it in a forked process) thus the "Type=forking". The one I
submitted does not fork. It allows for better log capturing as far as I
remember.
As Raul Gutierrez Segales suggested, I would go with a systemd service file
that directly calls `java` in order to keep all configuration in the systemd
service file.
> Add Systemd startup/conf files
> ------------------------------
>
> Key: ZOOKEEPER-2095
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2095
> Project: ZooKeeper
> Issue Type: Improvement
> Components: contrib
> Reporter: Guillaume ALAUX
> Priority: Minor
> Attachments: ZOOKEEPER-2095.patch
>
>
> As adoption of systemd by distributions grows, it would be nice to have
> systemd configuration and startup files for Zookeeper in the upstream tree. I
> would thus like to contribute the following patch which brings the followings
> systemd files:
> - {{sysusers.d_zookeeper.conf}}: creates {{zookeeper}} Linux system user to
> run Zookeeper
> - {{tmpfiles.d_zookeeper.conf}}: creates temporary {{/var/log/zookeeper}} and
> {{/var/lib/zookeeper} directories
> - {{zookeeper.service}}: regular systemd startup _script_
> - {{zookeeper@.service}}: systemd startup _script_ for specific use (for
> instance when Zookeeper is invoked to support some other piece of software –
> [example for
> Kafka|http://pkgbuild.com/git/aur-mirror.git/tree/kafka/systemd_kafka.service#n3],
> [example for
> Storm|http://pkgbuild.com/git/aur-mirror.git/tree/storm/systemd_storm-nimbus.service#n3])
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
