SlackwareThis Forum is for the discussion of Slackware Linux.
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.
So if i set my time zone to US/Eastern my computer now thinks it's 10:12:17 in the morning -.- I am not finding a timezone man page -.- anyone care to specify a manpage for what he was refering too so i may look at it
When you execute the command
in a terminal, you should see the manpage for timezone. If this is not the case, maybe you're system is messed up.
Well for now i guess non of this matters or well maybe you can tell me what to do now. I am reinstalling slackware64 14 to undo some stuff I've done and just to start fresh. I need to know though how can I set my clock up properly you think between ntp (if needed) and choosing yes instead of no when it comes to the hardware clock where I don't think I'm gonna use windows I have a spare PC so I can try and better fix this issue. Thanks everyone
The only thing I do after a standard installation as you describe is to edit /etc/ntp.conf. Here's my netbook's as an example (I don't have security concerns).
# Configuration file for ntpd.
# Time sources
# Using pool method from /usr/share/doc/ntp-4.2.6p1/html/manyopt.html#pool
# also at http://www.eecis.udel.edu/~mills/ntp/html/manyopt.html#pool
# For India
# (Asia also required because India is inadequate)
# For UK
# Local, for use when not connected to the Internet
fudge 127.127.1.0 stratum 10
# Drift file
I know that markush and thats wheat I been running to change my timezone this whole time :P Hasn't done me anygood but lets take a break from this issue I'm having some performance issues ever since I switched to multilib this afternoon that I'm not happy about and so now I need to reverse this issue -.- gonna just clear the entire system reinstall the system and do all but one thing right this time (we hope all but that one thing right ) we see if setting up the system to look at my RTC will help anything
1. Your hardwarclock in the BIOS is set to localtime (the correct time at your home) and
2. You've chosen the correct timezone US/Eastern and
3. you've selected (in timeconfig) "hardwareclock is set to localtime"
Then it should actually work for you.
You can also use the ntpdate command (when the above settings are all correct)
as root. Afterwards the system should have the correct time.
You seem to have many problems with Slackware, maybe you try it a bit more simple and install Slackware 32bit, then you don't need multilib and can make some experience with Linux and Slackware before doing more advanced things.
I've used slackware 32bit for years I'm just I been taking some chances and exploring but I have considered it but I really need the advantage of my cpu at 64bit because of lot of my applications take advantage of 64bit. I just still getting used to the fact that no one really considers linux in the windows environment and I use both and it's hard to not use a linux version of some my apps but i have decided that some alternatives are really working out for me and that I think i know what I need to do now. Like i said this time around I'm gonna do things differently
So I can't get ntpdate to work it always tells me socket is in use exiting it and it looks like everytime i enter the command a number next to ntpdate gets larger by 1 everytime. Any ideas I can't get any timeservers setup with this thing for some reason? gonna try adding it to the file directly thought but i doubt that will change anything.
So I can't get ntpdate to work it always tells me socket is in use
That's probably because the NTP daemon, ntpd, is running. If you want to run ntpdate then stop the daemon. AFAIK there's no point because Slackware starts ntpd with the -g option. From the ntpd man page:
Allow the first adjustment to be Big.
Here's an illustrative command shell session
root@CW9:~# ntpdate asia.pool.ntp.org
12 Nov 07:38:59 ntpdate: the NTP socket is in use, exiting
root@CW9:~# /etc/rc.d/rc.ntpd stop
Stopping NTP daemon...
root@CW9:~# ntpdate asia.pool.ntp.org
12 Nov 07:39:20 ntpdate: step time server 188.8.131.52 offset -0.567154 sec
root@CW9:~# /etc/rc.d/rc.ntpd start
Starting NTP daemon: /usr/sbin/ntpd -g