[
https://issues.apache.org/jira/browse/JENA-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16416959#comment-16416959
]
ASF subversion and git services commented on JENA-1510:
-------------------------------------------------------
Commit 635466a1ecef8130ea3f0abc3056bcbf7c86b6da in jena's branch
refs/heads/master from [~osma]
[ https://git-wip-us.apache.org/repos/asf?p=jena.git;h=635466a ]
JENA-1510: Add section on how to configure syslog logging for fuseki systemd
service.
> Add logging to systemd unit file for Fuseki
> -------------------------------------------
>
> Key: JENA-1510
> URL: https://issues.apache.org/jira/browse/JENA-1510
> Project: Apache Jena
> Issue Type: Brainstorming
> Components: Fuseki
> Reporter: Joachim Neubert
> Priority: Minor
>
> Currently, the fuseki.service logs to journalctl, which is the systemd
> default mechanism, and not to any fuseki-specific log file. Since I want to
> have (and probably keep) such files, I've followed a [solution on
> stackoverflow|https://stackoverflow.com/questions/37585758/how-to-redirect-output-of-systemd-service-to-a-file]
> and added
> {code}
> StandardOutput=syslog
> StandardError=syslog
> SyslogIdentifier=fuseki
> {code}
> which logs to rsyslog. A /etc/rsyslog.d/fuseki.conf file then defines the
> actual log location:
> {code}
> if $programname == 'fuseki' then /var/log/fuseki/stderrout.log
> if $programname == 'fuseki' then stop
> {code}
> which worked nicely. I suppose it could be useful for others, too. What do
> you think?
> Ping [~osma] who created the systemd unit file (JENA-1501).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
