Changes to pmset being ignored

This is a question for advanced users.

I'm on a mid-2012 "MacBookPro9,2"

Before I upgraded to Mavericks, I was using the most up-to-date version of Mountain Lion.

In Mountain Lion, I had my pmset standbydelay set to 24 hours instead of the default (I think) 4 hours, so that waking from a laptop left closed overnight would take a few seconds rather than a minute or so (avoiding SafeSleep).

Right after I updated to Mavericks, I stupidly edited my sudoers file with vim rather than with visudo. That broke "sudo," but I seem to have fixed it (followed the directions here: http://astrails.com/blog/2009/9/29/how-to-fix-a-hosed-etc-sudoers-file-on-mac-os x [gave admin write privileges using Finder, commented out the line I added with vim, un-commented the line with visudo, removed admin write privileges using Finder]) — after doing that, "sudo" started working just fine again. Haven't had any problems using "sudo" since.

(I don't know if anything in the previous paragraph is relevant, but it seems like it might be.)

After I got that sudoers business sorted out, the next morning I opened my laptop to find that it had been in SafeSleep. I realized that the Mavericks upgrade must have removed my pmset standbydelay customization, so I once again changed it to 24 hours ("sudo pmset -a standbydelay 86400"), and "pmset -g" confirmed that the change was accepted. The PowerManagement plist reflected my change, too, so I thought everything was good.

But then the same thing happened the next morning—SafeSleep was not avoided. I shut down the laptop and started it up again, only to find that the standbydelay setting had reverted to the 4-hour default in the PowerManagement plist. I think maybe this had something to do with the whole sudoers debacle (not sure), because after I re-implemented the 24-hour standbydelay and shut down and restarted a second time, my settings stuck (and that has been my experience since then—the standbydelay remains set to 24 hours).

But the weird thing is that the laptop still goes into SafeSleep as if I had never changed the standbydelay setting. Every morning when I open the laptop it has to come out of hibernation, even though the PowerManagement plist still says standbydelay is 86400 seconds.

I've tried:

--changing hibernation mode to 0 ("sudo pmset -a hibernationmode 0")

--deleting PowerManagement plist, rebooting, re-implementing the 86400 standbydelay and/or the 0 hibernationmode

--repairing permissions in Disk Utility

--reinstalling Mavericks (I was surprised that my customized sudoers file and PowerManagement plist were unchanged by this)

Ultimately the problem is a minor nuisance, but I can't for the life of me get my pmset changes to work, even though "pmset -g" and the plist reflect my changes. I wonder if it might have something to do with my sudoers idiocy (did I somehow permanently mess something up?), but sudo works just fine, so I'm not sure. Searching forums, I haven't found anyone else encountering problems with pmset in Mavericks.

Does anyone have any idea what might be happening here? It's so bizarre to me that changes to hibernation mode and/or standbydelay SEEM to be accepted, judging by the "pmset -g" command and by seeing my changes appear in the PowerManagement plist, but it's like my computer is simply ignoring those settings.

"pmset -g" yields this:

But it still enters SafeSleep after 4 hours.