Any program that puts files in /tmp should rightfully expect that they can be deleted. Further, if it did happen to still have them open, the data blocks would not be deallocated until it closed the file, so deletion wouldn't affect it at all unless it was very stupidly written. To find out what, if anything, is using the file, try fuser /tmp/387b487c.805 or lsof /tmp/387b487c.805 If that spits anything, then it's in use. You can sometimes make use of ls -lut 387b487c.805 to see when the file was last used. It might give you a clue as to who or what created it. The other things to do are: file 387b487c.805 which might provide instant insight, and (if "file" above says it's text or commands) more 387b487c.805 (if it's not text) hd 387b487c.805 | more or even just strings 387b487c.805 to see the contents. As a general trick to see if a file is needed by anything else, try changing its name: mv 387b487c.805 THISWAS387b487c.805 If nothing barfs after a few days, you should be safe to remove it- but again, anything in /tmp should be fair game period. -- Tony Lawrence (email@example.com) SCO articles, help, book reviews, tests, job listings and more : https://www.ApLawrence.com
Got something to add? Send me email.
More Articles by Tony Lawrence © 2011-04-25 Tony Lawrence