2
There's a folder on my Linux desktop which shouldn't exist. The first time I saw it, I thought I'd accidentally copied it from somewhere else, so I deleted it. Now it's back again. So it must have been automatically created by some process, but what can I do to figure out which program is creating it? I think it's likely that if I delete the folder it'll eventually be created again, so I should be able to catch this program in the act if anyone can suggest a technique for doing so.
By the way, there are no files in this mystery folder, and its name is the same as another folder I created months ago to hold my personal documents, not something that a program would create to hold its own configuration files or the like.
EDIT: Since I asked this question the folder hasn't shown up again, so I guess I could consider the problem solved... but I'd still be interested to know if anyone has an idea of some tool I could use if this happens again.
EDIT 2: IT'S BAAAACK.... yes, the mysteriously reappearing folder has reappeared. The modification time is July 2, ~10:30 PM EDT, just over a week after I last edited this question, so I guess that's when it was recreated, but that doesn't tell me what might have put it there. So I am still interested in any other answers.
Where is this folder located? What's its name? Maybe it's the standard folder defined by some desktop environment for storing documents (eg. "Documents") and the desktop environment is recreating it when it's missing. – goedson – 2010-06-22T13:02:16.303
Who is the owner of the folder? Does that lead you to its creator? – JRobert – 2010-06-22T14:04:38.650
@goedson: The folder is named
PHYS542
. Like I said, I highly doubt that's any sort of standard folder. @JRobert: the folder is owned by me (it's a single-user system), so unfortunately that doesn't tell me anything useful. Well, I guess I know it's not being created byroot
but that doesn't narrow it down enough. – David Z – 2010-06-22T15:04:43.243Have you tried greping for PHYS542 on your system? Maybe it could help you find which executable is creating this. – goedson – 2011-04-27T11:54:11.307
@goedson: good idea, although the problem hasn't reoccurred since last summer so I suspect I wouldn't find anything now. I'll try it anyway and see if anything pops up. – David Z – 2011-04-27T17:32:44.723