A mysterious file keeps appearing on my startup disk. It's most likely a typo in a script or something, but even though it's being created with my user account as the owner, that hasn't helped me narrow it down.

Would it be safe for me to lock my system's startup disk to prevent writing to the root folder? As far as I know nothing needs to be written there, as all the various directories used by the system are already present such as /Library, /tmp, /Applications, /System and so on. But even so, I'm wondering if this is safe to do, or will it ruin my system?

I'm hoping that by locking the volume I can force whatever is creating the file to report an error in a log file, and also to prevent similar clutter in future (some badly written programs have a nasty tendency to put log files there), but obviously it's no good if it'll break something!

  • 2
    How do you intend to lock the volume? – nohillside Mar 31 '14 at 9:41
  • What is the name of "the file" that you keep seeing? is it always the same name, or does it change? How big is it? Can you open it with anything? – Chris Paveglio Mar 31 '14 at 19:15
  • Simply your Mac Wont BOOT , so Dont go there... – WM. Apr 1 '14 at 8:52

You could use dtrace to determine what is creating the file, say using iosnoop.d which runs under dtrace will reveal which applications are using the disk and what files they are reading or writing. This would imply catching its creation or write access, "live".

If that doesn't reveal who's created the file it could be because the process is communicating more tightly with the filessytem and hfsslower.d may be required to locating the IO to this file.

You could also see if the file is open currently, and if so by whom, using lsof.

The above suggestions should reveal what's writing this file, which I believe is the root of your question.

But to specifically answer your question, no you should not "lock" the root directory of your startup disk as this is not an advisable safe practice and may prevent the OS from booting or functioning as expected. I presume here that by locking you mean the Finder concept of locking a file, or the POSIX concepts of restricting permissions and using the uchg/schg file flags via chflags. While Mac OS X doesn't normally create new files in this location arbitrarily, changes in permissions and ownership could effect filesystem traversal by users and processes and in general *nix systems expect the root volume directory to be mutable. Many processes and commands in *nix use this as a fallback default, and it's often seen used in certain cases where a login occurs and there's no HOME, for instance. While it may ave no immediate short term negative effects, it's not a wise practice nor is it the best method to determine what's causing your mysterious file creation.

Knowing more about the file might also help answer your underlying question.

| improve this answer | |
  • The file is empty and simply named "1" (minus quotes). My suspicion is it's a script with a typo somewhere, but none of the ones I've checked have any noticeable errors, the file is also created right on shut-down, but not consistently, which makes it very hard to trace. I guess my alternative is to re-create the file myself, then use chflags to lock and hide only that file, then see if anything reports any errors when trying to manipulate it in future. Anyway, I just got curious as to whether locking the root volume works, so you've answered that, thanks! – Haravikk Apr 1 '14 at 10:38

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .