SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
O.K., what is it with Slack and wrong time. ???.
Seen plenty of threads asking similar. After booting Slack, my clock is 30 minutes slow - and the hardware clock gets reset to this incorrect value.
Yes I have the correct locale set, yes I have re-run timeconfig several times. I'm at UTC+10, and the clock is out by 30 minutes. *NO* ntpdate is not the solution.
ntpdate is for correcting clock drift, not fixing bad configuration data. Seems like there is an issue here somewhere. This is the only distro I've seen this with - and I've installed plenty in the last couple of months.
As a workaround, I've put ntpdate in rc.local. Hiding the problem, not fixing it
Using the kernel as supplied on the install disks - 2.4.29 (??? - guessing, it's at work). That would be base.i I guess.
Will check tomorrow. Same goes for power management - don't know.
Will get a 2.6 kernel built when I can free up some space, then I'll be able to give you definitive answers.
O.K. folks, sorry to waste you time.
Apologies to the good ship Slack and all who sail in her.
Laptop was powered down all night.
Doesn't show the symptoms today. Have tried various time zones, and they all work as expected (ntpdate commented out in rc.local).
We actually have a time zone that is half an hour behind the zone I'm in. Looked like that was being used incorrectly.
NO - I didn't use this other zone at any time yesterday. Deliberately didn't, as things looked so suspicious.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.