November 2005 - openSUSE Users - openSUSE Mailing Lists

Possible boot ordering problem between ntp and dhcp
by Bruce A. Mallett 04 Nov '05

04 Nov '05

I think I'm seeing an ordering problem in that ntp won't set the system clock on boot because: 1) Yast stores the time server's name and not its IP address in /etc/ntp.conf 2) My system gets its IP via dhcpd 3) ntp fails to resolve the IP address via DNS for the ntp server named in /etc/ntp.conf because ... 4) dhcpd does not modify /etc/resolv.conf until *after* /etc/init.d/ntp is run FWIW: I've eth0 controlled by ifplugd. I believe that this is demonstrated by doing: egrep -i 'dhcp|ntp' /var/log/messages which yields the following: --- Nov 3 15:20:20 tornado ntpdate[5292]: can't find host louie.udel.edu Nov 3 15:20:20 tornado ntpdate[5292]: no servers can be used, exiting Nov 3 15:20:20 tornado ntpd[5365]: ntpd 4.2.0a(a)1.1191-r Fri Sep 9 17:17:17 UTC 2005 (1) Nov 3 15:20:21 tornado ntpd[5365]: precision = 3.000 usec Nov 3 15:20:21 tornado ntpd[5365]: Listening on interface wildcard, 0.0.0.0#123 Nov 3 15:20:21 tornado ntpd[5365]: Listening on interface wildcard, ::#123 Nov 3 15:20:21 tornado ntpd[5365]: Listening on interface lo, 127.0.0.1#123 Nov 3 15:20:21 tornado ntpd[5365]: kernel time sync status 0040 Nov 3 15:20:21 tornado ntpd[5365]: frequency initialized -1.291 PPM from /var/lib/ntp/drift/ntp.drift Nov 3 15:20:25 tornado modify_resolvconf: Service dhcpcd modified /etc/resolv.conf. See info block in this file --- showing /etc/resolv.conf being modified *after* ntp runs.

2 2

(OT) 64-bit Linux - THANKS
by Mike Roy 04 Nov '05

04 Nov '05

Hello everyone: Just a short note to say thank you to all of you who responded to my earlier request about 64-bit machines and Linux. I didn't realize just how many flavors of Linux are running on AMD 64 machines, it was an eye-opener. Again, many thanks. Cheers, Mike

3 3

cpu throttling on Fujitsu Lifebook S7020
by Miroslav Ruda 04 Nov '05

04 Nov '05

Hello, I'm installing Opensuse 10.0 on Siemens Fujitsu Lifebook S7020 and I'm not able to setup CPU throttling. Looks like kernel doesn't support it: # cat /proc/acpi/processor/CPU0/throttling <not supported> I have tried modules acpi-cpufreq and speedstep-centrino with the same result - CPU frequency can be changed, but throttling is not supported. Processor is Intel(R) Pentium(R) M processor 2.00GHz, motherboard with intel 915 chipset. Any idea what's missing? -- Mirek Ruda

2 2

Memory Details
by Jose A Medina 04 Nov '05

04 Nov '05

Guess this question is not specific to SuSe but that is our flavor of Linux in house, so here goes. We are currently running SLES9 and we have one remote server that we will be upgrading the RAM on. The problem is we have no way of knowing what the current type/config of the system ram is. Is there a tool we can use to determine. The number of RAMM slots filled and what types of RAM fill these slots.. I'm assume there is a simple tool for this but I have never needed to use one prior to now. Thanks JAM

2 1

Re: [SLE] Trouble with adding YAST installation sources
by Dan Abernathy 04 Nov '05

04 Nov '05

Thank you for the replies. I did have the U.S. Packman mirror entered correctly, but it seems problematic, the downloads were constantly stalling even when it did manage to refresh the package list. I changed it to a different mirror and now all is well. Mplayer is working, which was my main goal. I do wish there were a way to close YAST when it's misbehaving, it doesn't respond to clicking "Abort" and whatnot.

2 2

know-how question: cups
by Stephan Böni 04 Nov '05

04 Nov '05

I can hold a print job in his queue with the lp command, like "lp -i 3 -H hold" which holds the print job with id 3. But how can in verify, which jobs are held? Is there no command, who can display this information? Thanks for any help. Stephan

3 2

VPS & Firewall problem
by Marek Mikuliszyn 04 Nov '05

04 Nov '05

Hello everyone! I've got a burning problem with my VPS running under SuSE with Plesk. Well... I've tried to configure firewall thru YaST tool and I configured sth badly cause I lost access to my server. No problem, I though cause I still could switch to Repair Mode with Plesk... so I did. But the problem is, that when I'm changing anything while under Repair Mode, after restart all changes are changing back to old/bad ones :/ I've tried to edit /etc/sysconfig/SuSEfirewall2 or even delete firwall script from /init.d/ with no effect - files are returning after restart. My question is: Could someone please tell me how to turn off this damn SuSEfirewall and configure firewall in future only thru iptables ? -- greetings, Marek Mikuliszyn

3 2

Where is DB.php ? Suse 10.0.
by Robert Rozman 04 Nov '05

04 Nov '05

Hi, I'm trying to install PHP application and it complains : robi:/usr/src/AMP # ./install_amp Checking for PEAR DB..FAILED [FATAL] PEAR must be installed (requires DB.php). Include path: /usr/share/php I've installed php4-pear and I'm searching for file DB.php and it isn't there. Does anyone know in what package is this file included or is it missing from Suse rpm's ? Thanks in advance, regards, Rob.

2 1

trac and SuSE 10?
by Anders Norrbring 04 Nov '05

04 Nov '05

Has anyone got trac up and running on SuSE 10? If so, how? I just can't get it to work at all... -- Anders Norrbring Norrbring Consulting

1 0

no keyboard with KDE
by Vincente Aggrippino 04 Nov '05

04 Nov '05

SuSE 10.0. I recently switched from Fedora Core where I was used to Gnome. So, when I switched to SuSE, I made sure that all of the Gnome and GTK stuff was installed and Gnome was the default. I thought I'd give KDE a try, since it's SuSE's default and there are a lot of programs that I'm not using which are KDE based. After I switched, using the "Session" link at the bottom of the greeter, I can't use the keyboard. I know it works, I just can't use it from within KDE. I can't type in a Konsole terminal... I can't use CTRL-ALT-F1 to switch to the actual console. I can't open the YaST Control Center properly because I can't type the root password when I'm prompted. If I use the mouse to log out, or end my session, I can type again... I can log in. Everything works fine in Gnome. I read something from an old message that seems to describe this problem in relation to upgrading KDE, but this is the first time I've run KDE. Does anyone have any ideas? Thanks, Vince

4 7