j
I choose "local" rather than gmt during the setup, which *should* in theory give me 12 hr clock, no? Well it doesn't I've even reinstalled it, I don't get error messages or anything like that I just get a 24 hr clock that starts w/ time in the afternoon, say, set at 4 pm, and it acts as if it's 04:00, apparently.
Several issues here: * The choice of 12 or 24-hour display will depend on the time-display application, not the system time setting. Consult the man page for the clock program you're using for display. * If your system time is really off by 12 hours, you could have the wrong timezone set up, so make sure yours is correct. For example, I'm near Seattle Washington, USA, so my timezone is USA/Los Angeles, or somesuch. Yast should give you an easy way to set this. * Make sure your hardware (the cmos clock) clock is set correctly. When the machine boots, it reads the cmos clock, applying any corrections it's learned from periodic adjustments you may have made. Thereafter, the system time is kept by the cpu, and unless you take measures, say, in a local cron script, to periodically write the system time to the hardware clock, the hwclock will drift off by a lot---it's not meant to be particularly accurate. Keep in mind that the first time you change the system time, you may be making a huge adjustment; you won't want that huge adjustment factor applied each time, so you can simply remove the adjustment file (/etc/adjustime, or somesuch). See man hwclock. Hope that helps, Jim