Yes - it's on "Local", but screws up the clock on every reboot.

I have a suspicion the "system" stores something in a read-only file somewhere, which forces it to treat the systemn clock as being in EST on bootup, regardless of other settings.