December 2003 - openSUSE Users - openSUSE Mailing Lists

Re: [SLE] Time synch problem
by Carlos E. R. 23 Feb '05

23 Feb '05

El 2003-07-09 a las 13:37, C Hamel escribió: (You forgot to post to the list) > I am afraid I don't even know how to ask a question, at this point, but I'll > make an attempt: Exactly where should this ntp thing be called to set the > clock ...or(/and) by what process? It is a very proper question :-) Well, it depends. There are two ways. If your computer is up all the time, and has a permanent network connection, you can use the ntpd daemon, which polls a set of servers about once a minute, and _very_ slowly adjusts the system clock; it can even note the systematic error or drift, and take that in to account to discipline the system clock. There are many options available for the daemon: see full doc in: http://localhost/usr/share/doc/packages/xntp-doc/html/index.htm Or, you may have a temporary network connection, like I do; I will explain this in some detail. We can adjust the clock to "internet" time, once, sometime after we connect to internet. This, apparently, can be done with the daemon, using some option I don't fully understand. Or we can use ntpdate - a program which is to disappear some time in the future, but that I use, and SuSE uses as well in its own script. For this, we can simply call "/etc/init.d/xntpd ntptimeset" - and assume that when "ntpdate" finally disappears SuSE will adjust the script appropriately ;-) Of course, /etc/ntp.conf has to be configured; at least, it must have a list of servers: server IP_address server name_address This is sufficient for "xntpd ntptimeset" to work; just leave the rest of the config at the default values. If you want to use the daemon, then I'm not the person to ask :-) Ok, so when is the appropriate time to make this time adjust? Well, ideally, during system boot-up, after network connection is established. This is done properly by the service xntpd, if enabled. The SuSE script "/etc/init.d/xntpd start" does first a clock set using ntpdate, if the variable XNTPD_INITIAL_NTPDATE is set to "AUTO". Then, it starts the daemon to keep time synchronized. And, if our network connection is not permanent? Then, the script "/etc/ppp/poll.tcpip", which is called from "/etc/ppp/ip-up", will adjust the clock first thing: assuming we have some servers configured, it will be done every time we connect to internet with the modem. I do it differently, only once every five times, and I also update the hwclock. The danger of this method is that the clock might suddenly go forward or backward a bit (seconds or hours, it depends): not very nice on a *nix system, but we can not avoid it. More details to be aware of: what happens to the hardware or CMOS clock? Well, the script "/etc/init.d/boot.clock" (read it, it is documented) does this sequence of things (using the command "hwclock") before starting system services: - Create if it doesn't exist, the file "/etc/adjtime" - Adjust hardware clock (CMOS) for known drift during the time the computer has been off; this depends on the previous file to work. - Copy CMOS clock (hardware) to system time (CPU and OS maintained). After this, the system goes fully up, and maybe, the clock is adjusted from the internet or by hand (danger!). But (and this is very different than windows) the CPU maintained clock has to be copied back to the CMOS, because the kernel doesn't do it. SuSE does it in the script "/etc/init.d/halt" that copies system time to hardware time just before power off. Me, I prefer to do it just after I adjust to network time, inside "ip-up.local", like this: /usr/sbin/rcxntpd ntptimeset /sbin/hwclock --systohc More things to be aware of: a common mistake is manually adjusting the system clock from kde control center (for example), and not updating the hwclock at the same time: the drift adjust algorithm of hwclock thinks that the CMOS clock is fast or slow by the same amount you adjusted the clock, and the next boot it will adjust the time by several hours... The solution is to delete "/etc/adjtime" and call "/sbin/hwclock --systohc" just then (documented on the SuSE sdb). Well, this has been enough chatter on my part; let's hope I didn't make many mistakes :-) -- Saludos Carlos Robinson

3 7

How to add secondary IP address to a SuSE box?
by joe_pr＠myrealbox.com 16 Sep '04

16 Sep '04

Hello, I am converting one of our Domino servers fro NT4 to SuSE 8.2. Is there any way to add a secondary IP to the network card? I used to have such a setup for the current NT box and eve tried this config with Mandrake but thi sdoes not seem to be possible with YAST2. Any idea anybody? Thanks Josef Prusa

6 5

[SLE] LILO - files
by sander.van.vugt＠azlan.nl 06 Sep '04

06 Sep '04

Hi, I'dd like to know what the following files in the directory /boot are about. Can anyone give me a clue or point me to some documentation? - boot.b - chain.b - map - System.map-2.2.14 - chos.* Thanks in advance, Sander ********************************************************************** Disclaimer This email is confidential and intended solely for the use of the individual to whom it is adressed. Any views or opinions presented are solely those of the author and do do not necessarily represent those of the Azlan Holdings bv and/or subsidairy. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing or copying of this email is strictly prohibited If you have received this email in error please notify Azlan Holdings MIS Helpdesk by telephone on +31 (0) 79 3443200. ********************************************************************* -- To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the FAQ at http://www.suse.com/support/faq

4 3

9.1 unuseably slow
by David Bottrill 02 Sep '04

02 Sep '04

We received a copy of 9.1 today at work and I have installed this on three machines with dissapointing results. The first machine was an IBM Thinkpad R40 with a Centino 1600 CPU. This machine worked fine and the performance was great. The second and third machines were unusable, KDE takes serveral minutes to start, attempting to start YAST for instance will take about a minute for the SU box to appear and then another minute for YAST to load. I get similar results for all applications I have tried, in all instances the system performs like a P100 with very little RAM. The machines that run slowly are both Athlon XP based machines, one being an Athlon XP 2400 with 1GB of DDR RAM on an ECS Elite motherboard. The second machine is an XP2000 with 512MB of PC3200 RAM on a PCChips motherboard. I have applied all the updates with no effect. Any ideas would be appreciated, I've had to switch back to 9.0 as the whole 9.1 experience is unuseable has anybody got any ideas? David -- David Bottrill Registered Linux user number 330730 www.bottrill.org Internet SIP Phone: 1-747-244-2699

6 8

DVD playback...
by Matthew 14 May '04

14 May '04

Good day, Yes there are legal reasons why SuSE cannot have DVD playback of those pesky movies, but what be done? Would it be too expensive for Novell/SuSE to license a codec? Seems like there is a new copyright law in Germany that has made PackMan be more cautious. No one has made a player for Linux that is 100% legal, is it due to expense? Matt

2 1

OT: What Perl Modules are installed?
by Ahbaid Gaffoor 01 Mar '04

01 Mar '04

Hello all, how do you test to see what perl modules are installed? Is there a quick command that does this for Perl? Something like how we can do "rpm -qa" to see all rpm's installed... many thanks, Ahbaid

9 12

Unofficial SuSEFAQ project needs your help
by Togan Muftuoglu 01 Mar '04

01 Mar '04

Hi everyone, As the subject header says the project needs your help in adding new content. While I am still unpacking the big part is finished and I can play with my projects again. However, while I was away SuSE 9.0 came lots of new comers joined etc. etc . As a result I was not able to follow the current threads since October and that is in a few days two months time. So I need FAQ entries the question and the answer just in simple text format (yes putting url links so that I can follow the thread will help) Any mini howto's are also welcomed send it to my direct attention note: my mail server does not like spam at all so make sure you have your reverse address delegated. If that becomes a problem please post it to the http://sf.net/projects/susefaq Thanks in advance. -- Togan Muftuoglu Unofficial SuSE FAQ Maintainer http://susefaq.sf.net

3 7

No CD sound with SUSE 9.0
by Karel De Vriendt 22 Feb '04

22 Feb '04

I did a standard install with SUSE 9.0 on my computer. I have a Creative SB Live!Value sound card. YAST detects my sound card as "CT4832 SBLive! Value" and when, in the sound configuration dialog, I test the volume, I can hear the music. But I do not hear the sound associated with events in GNOME (of course after having started the sound server) and when I play a CD with xmms, again no sound. In the startup sequence of the computer, I see - start sound driver: emu10K1 - restoring previous sound settings Can somebody suggest how to proceed? Thanks in advance, Karel De Vriendt

5 7

Can anyone recommend a backup program/script for home user?
by Tom Nielsen 19 Feb '04

19 Feb '04

I was just about to setup a raid 1 when I realized I didn't want to really accomplish that. What I want is something to backup my system incase I fubar something. So, rather than dd my drive every night, I'm wondering how I can backup my system where only the changed files get backed up rather than the whole drive. I looked at rsync but I'm not sure if that's what I want. Any advice? Tom

15 17

9.0 and NTFS
by Ulrich Leopold 29 Jan '04

29 Jan '04

Dear all, How well is NTFS supported in SuSE 9.0? 1. Can it read and write properly NTFS? 2. Does it support all possible NTFS cluster sizes such as 512 bytes up to 64kB? Cheers, Ulrich

5 4