The way that plugins handle session/socket files

As a systems administrator, I would like the way plugins handle session and socket files to be looked at so that when a user reaches their inode limit, they can still use an inode counting plugin to identify where the inode count issue is.

-------------------------

When user reaches its inode limit third party plugins stops working because it is not possible to create session/socket files.

I would suggest changing the way that plugins handle session/socket files. So custom built Inode counting plugins could show userwhere the issue is and etc.