AW: gziped stderrout.log not started anew

2021-10-19 Thread Neubert, Joachim
t; Von: Andy Seaborne [mailto:a...@apache.org] > Gesendet: Dienstag, 19. Oktober 2021 17:39 > An: users@jena.apache.org > Betreff: Re: gziped stderrout.log not started anew > > Hi Joachim, > > When you say "stopped" do you the server is not running or only pause

Re: gziped stderrout.log not started anew

2021-10-19 Thread Andy Seaborne
Hi Joachim, When you say "stopped" do you the server is not running or only paused? The usual script sends output to a file that is created by the shell. If the server is paused, and continued, the file is still open but no longer accessible from the filesystem. If it exited and restarted,

gziped stderrout.log not started anew

2021-10-19 Thread Neubert, Joachim
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