I'm having trouble deleting a plist file - I realize it's cached, I've tried logging out, restarting, killing cfprefsd, but no luck - the cached version returns - how do I do this now?
Thanks!
Thanks!
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
How to delete plist files?
- Thread starter disasterdrone
- Start date
- Sort by reaction score
Boot the recovery partition if you have one. Then use Disk Utility to mount your install drive/partition open Terminal from the same Utilities menu you used to start DU and rm /path/to/install/System/Library/Extentions/Some.kext/Contents/ToBeDeleted.plist. Once done reboot and you should have it done as the operating system would not have been running preventing the deletion because of the caching.
Only way I can see to do so with the operating system not running messing you about with the cache. Going to have to adjust the path for sure to the launch daemons one as I see now it is a daemon your talking about not a .kext, had that stuck in my brain somehow when writing that.
Am I halucinating though? In olden times you used to be able to just delete them?
No clue I usually only do an edit on them don't think I have ever had to delete one.
Which plist specifically are you trying to delete?
Like you mentioned, Mavericks caches plist files. The routine should be delete plist reboot then start the app to recreate the default plist.
What exact sequence are you following?
Hi thanks for the help.
I'm trying to delete the time machine plist, I'm having extensive time machine problems and am following Pondini's advice for a full reset.
I'm not having trouble deleting the file, it's not a force delete problem. My problem is that the plist restores itself from the cache.
1. Delete plist.
2. Empty trash.
3. Reboot.
4. plist is back.
Try this order.
1. Turn off Time Machine
2. Delete plist.
3. Reboot.
4. Turn on Time Machine
That should create a new default plist.
When you say the plist is back, are you sure the one that came back is cached or do the date/time created show it may be the newly created default like you want?
Last edited:
What is the name of, and the location of, the cache file (or files) in which the plists are cached?
If that file (or files) can be identified and located, why not move it (them) to the desktop and then reboot?
I am assuming that during a reboot, the OS will "look for" the cache(s) in a predetermined place. And that if it can't find and read them, it will then just read the actual (i.e. non-cached) plist files and in the process of doing so create a NEW cache file(s).
It may be necessary to use a utility (such as PathFinder) that can easily see and move files that are normally invisible to the user...
If that file (or files) can be identified and located, why not move it (them) to the desktop and then reboot?
I am assuming that during a reboot, the OS will "look for" the cache(s) in a predetermined place. And that if it can't find and read them, it will then just read the actual (i.e. non-cached) plist files and in the process of doing so create a NEW cache file(s).
It may be necessary to use a utility (such as PathFinder) that can easily see and move files that are normally invisible to the user...
When you delete a .plist file, a new one is automatically created by the app.
Thanks guys.
I have tm turned off when I do this. The plist is recreated with the same settings as before, not new default settings. I'm going to try the recovery partition route later.
Thanks,
I have tm turned off when I do this. The plist is recreated with the same settings as before, not new default settings. I'm going to try the recovery partition route later.
Thanks,
I am not sure exactly what settings you are trying to remove, but I know that some apps, for example iDefrag, will store a "Settings" file in odd places. In the case of iDefrag, its licensing information to help deter replication of that file. I have seen files with names that resemble "sfsfsdgw3232f" that seem to be intentionally named that way to help prevent user identification.
