When, with a stopped Fuseki, I gzip and rename the stderrout.log file, it is 
not created anew with the next fuseki start.

When I create an empty stderrout.log manually, and make it belong to 
fuseki:fuseki, the file remains empty, while apparently the log entries are 
written to the system log (journalctl - CentOs 7.9, SElinux disabled).

Does anybody know how to get Fuseki/Jetty to accept the newly created log file? 
(and perhaps, how this can happen in the first place?)

Help is much appreciated!

Cheers, Joachim
--
Joachim Neubert

ZBW - Leibniz Information Centre for Economics
Neuer Jungfernstieg 21
20354 Hamburg
Phone +49-40-42834-462

Reply via email to