stephan, thanks for tracking this down. I almost figured it out, and then I found that you already reported this bug. Your other bug report was also super helpful for me to get Solr working after my upgrade to Buster.
On Sun, Aug 04, 2019 at 03:31:52PM +0200, beirer wrote: > The fix is also similar: > > Copy /lib/systemd/system/jetty9.service to /etc/systemd/system and modify > it by adding > > ReadWritePaths=/var/lib/solr/data > > to the # Security paragraph. I found that adding a file /etc/systemd/system/jetty9.service.d/override.conf (and making its parent directory, both via `systemctl edit jetty9`) with these contents allowed me to append to the ReadWritePaths list, overriding just the right part to get Solr to work under Jetty: ----- [Service] ReadWritePaths=/var/lib/solr/data/ ----- Debian Java Maintainers, is there a sensible way to ship a systemd override file like this with solr-jetty? (The right path for such a packaged override file might be under /lib/systemd/ somewhere, because I think /etc/systemd/ is reserved for user-made customizations.) -- J.P. Larocque <[email protected]> __ This is the maintainer address of Debian's Java team <https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-java-maintainers>. Please use [email protected] for discussions and questions.
