A Bug about the JVM Attach mechanism

[Peter Levart]

Here's  a thread that describes why systemd-tmpfiles doesn't implement 
the --fuser option that tmpwatch does:

https://lists.freedesktop.org/archives/systemd-devel/2015-April/031339.html

The authors say the following:


/In almost all cases the atime checks we do should be fully sufficient//
//though. Do you have a case where they aren't?//
//
//(Note that we do compare all unix sockets we find with /proc/net/unix//
//though, which is relatively efficient still. Also, as unix sockets//
//which are actively used do not get their atime bumped this is kinda a//
//necessity to cover them nicely.)/


...meaning that /tmp/.java_pid<pid> which are UNIX sockets shouldn't be 
deleted by systemd-tmpfiles while still in use. Users of tmpwatch OTOH 
should enable the --fuser option.

Is this enough for you,  Nijiaben?


Regards, Peter

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.java.net/pipermail/serviceability-dev/attachments/20190622/0d6fb3b6/attachment.html>