In my experience, files that have the file descriptor of txt in lsof output are the executable file itself and shared objects. The lsof man page says that it means "program text (code and data)".
While debugging a problem, I found a large number of data files (specifically, ElasticSearch database index files) that lsof reported as txt. These are definitely not executable files. The process was ElasticSearch itself, which is a java process, if that helps point someone in the right direction.
I want to understand how this process is opening and using these files that gets it to be reported in this way. I'm trying to understand some memory utilization, and I suspect that these open files are related to some metrics I'm seeing in some way.
The system is Solaris 10 x86.
Best Answer
On Solaris, everything that is mapped into the memory space of the process will be listed by
lsofastxt, regardless of being the started executable, or an executable shared object mapped by ld.so, or any data file mapped directly by the application.On Linux, only the started executable will be listed as
txt, everything else mapped into the memory space will be shown asmem(both executable shared objects and data files).