Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
lsof is your friend
By default it will show all open files, but you can get open files for a user:
lsof -u alowe (showing all open files for alowe)
or a process
lsof -p 123,456 (showing all open files for process numbers 123 and 456)
or a particular file
lsof /home/alowe/myfile (shows processes with /home/alowe/myfile open)
I do not think this always works for data files, as some applications only open the file when they want to read from or write to the file, closing the file while the user edits it... so on open, they open the file, then read, then close the file, after that when the user chooses to save the file, the process opens the file, writes out the data, and closes it.
If a file should be only opened and edited by one user the process should probably lock the file while the process runs.
I know my text editor (Kate) will open the file, and I can open it in another editor, and kate will warn me that another process has changed the file (and give me alist of options (replace, save as, drop changes), but it uses timestamps, etc to determine this, and nothing stops the second process from editing the file.
I mention these last notes because you mention text files, and they are probably not under the /proc file system because they are not technically open, just being edited by a process, but not in use.
I don't think you can actually tell if a process is editing a memory buffered copy of a file, as it has not marked the file as locked and has not left the file open, it is technically not open or in use, just the memory copy of the data is being used.
Sorry, and I could (Hopefully) be wrong, but I doubt it...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.