Summarizing a bit what I wrote in previous messages, it seems 8.19.5 does a chdir into the path.logs directory, 8.18.0 did not do this. There are relatively few *chdir calls, mostly into /tmp/hsperfdata_elasticsearch
It also tries to create the .attach.pid$PID file there, via /proc/$PID/cwd path, which is the same directory as path.logs at this point. This succeeds in my (standard install) case. The openat options are O_RDWR|O_CREAT|O_EXCL, and perms 0666. The file in this directory is closed and unlinked on my system approx 100 ms later. In between open and close there is a readlink call which shows the entire path (and returns -1 as its a file, not a link). Aside from log files (sic), I dont see other filesystem activity in that directory
I’m certainly not saying this is a smoking gun, but given the “unusual” setup in @buitcj ‘s path.logs directory maybe it’s interesting. It also sort of “links” the log directory and the “attach to JVM” topics, slightly.
I am also not sure it’s really an appropriate use of the path.logs directory ?