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:
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
Of course, /etc/ntp.conf has to be configured; at least, it must have a
list of servers:
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
- 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:
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 :-)
I am looking into setting up bandwidth limiting using cbq on Suse 9.1.
I have a few questions though before I spend hours reading the man pages as
they are quite heavy going.
1). Are there any quirks or issues using the 2.6 kernels ?
2). Will this work on a firewall that is using NAT ? Because all the
traffic going out originates from the same IP.
3). Is it possible to use traffic shaping to split a connection (ADSL) four
ways, so each user is guaranteed a quarter of the bandwidth, and also, to
allow the other users to share unused bandwidth while a user is offline ??
4). Can anyone point me at some documentation on this - howto's or examples
? The examples I have seen are all fairly complex.
Thanks for any help people can offer.
I've recently upgraded from SuSE 8.1 Pro to SuSE 9.1 Pro via a fresh
install and am having big problems. I'm running a Dell PowerEdge 2550
with an integrated Adaptec Ultra3 AIC-7899, IBM Ulstrastar Ultra320 73
GB drive, and kernel is latest via YaST of 220.127.116.11-104-default. This is
the same setup I've used for a long, long time with no problems under
At what seems to be completely random times I get tons of I/O errors
and the machine completely ceases to function. I have syslog turned all
the way up but nothing gets logged to syslog. Ocassionally I get to
tty10 quickly enough to see:
aic7xxx_abort returns 0x2000
SCSI error : <0 0 0 0> return code = 0x6000000
end_request: I/O error, dev sda, sector "varies but most recently 81773499".
I've tried mutiple known good drives but the same problem occurs so
unless I've had mass hard drive failures across multiple systems all at
once, I'm fairly certain it's not a hard drive problem. I'm using the
aic7xxx module. I noticed that there's also an aic7xxx_old module
available via modprobe -l | grep -i aic7. If I used YaST to look at
possible modules, it shows aic79xx and aic7xxx as suggestions. Any
ideas? Should I try one of these other two modules? The latest
2.6.x-cvs kernel from SuSE's ftp site? Compile my own from kernel.org?
Go back to 2.4 based system?....
Also, any good way to get some logging on this? I have cron sending
the output of dmesg and a few other things to a file every ten minutes
to try and catch something but it hasn't worked so far with gibberish
being appended to and corrupting the file.
Finally I got Kylix 3 installed on SuSE 9 but found trouble
right away. Even a new blank project fails to compile. I get a
bunch of errors with a file called time.h. After a little searching
in this group and elsewhere on the net, I found several references
to http://unvclx.sourceforge.net so I got 3.5.1 and installed
but still I have the same problem. I have seem some posts here
from those who say they have been using Kylix but I would certainly
like to know how they got it to work.
Yes, I know at least one post said there wasn't much future for Kylix
and after my experience so far, I am inclined to agree. I would love
to use something like Qt but I don't know of any gui builders for the
windows side. I have heard of tools for Linux but since I am wanting
to write for both platforms, it would be nice is there was a tool for
I asked SuSE support about the lack of Gnome Conduits and this is what I got...
"Unfortunatly it is up to the developer of the software to package it up for each distribution they
wish to support, unfortunatly, if the package is not available for SuSE linux all I could suggest
would be searching for the sources and compiling it on your system, beyond that theres not much we
So... (SuSE team listening) does this mean that every single RPM installed in SuSE is provided by
the people who developed the software? The Kernel, Gnome, KDE, all of that comes to SuSE already
ready to go. SuSE doesn't do anything, really. What, then, does SuSE do? Burn them all onto a CD
for me? Seriously, this is the most ridiculous response I've ever received from a SuSE rep. I
don't, for a minute, believe that the developers of Gnome-pilot-conduits created RPMs, packages,
etc. for Mandrake, Fedora, Ark Linux, FreeBSD, Debian, etc. but not for SuSE. That's absurd.
All I wanted was a straight answer and I got the biggest line of bull ever.
Being rusty technically, haven't used a sliderule in almost a half century,
the best I can say is don't squabble. Technology is supposed to be fun!
At least I made it that way working for a living in aerospace al alia.
John J. Devine
Anybody know how to get the touchpad activated on a Laptop with 9.1?
I can't seem to find any option in Yast.
HP Pavilion 4600. It worked fine in 9.0 (in fact it was the only distro which
installed well here).
I'm running SUSE 9 pro on a Toshiba Satellite 1115-S123, my wireless
card is a Microsoft Broadband Networking MN-520 (prism chipset), and
my access point is a D-Link DI-514. In Gnome, I have the wireless
applet in the toolbar to show my current signal strength. From time to
time, the applet will show N/A and when I check /var/log/messages I
get this (ignore the old dates):
May 31 13:00:55 slacker kernel: prism2sta_mlmerequest: Failed to read
wlan0 statistics: error=-61
May 31 13:00:57 slacker kernel: prism2sta_mlmerequest: Failed to read
wlan0 statistics: error=-61
May 31 13:00:58 slacker kernel: NETDEV WATCHDOG: wlan0: transmit timed out
May 31 13:00:58 slacker kernel: hfa384x_tx_timeout: Implement me.
May 31 13:00:59 slacker kernel: prism2sta_mlmerequest: Failed to read
wlan0 statistics: error=-61
May 31 13:01:03 slacker last message repeated 2 times
May 31 13:01:03 slacker kernel: NETDEV WATCHDOG: wlan0: transmit timed out
May 31 13:01:03 slacker kernel: hfa384x_tx_timeout: Implement me.
May 31 13:01:07 slacker kernel: prism2sta_mlmerequest: Failed to read
wlan0 statistics: error=-61
When this happens I lose all connectivity to the access point. I
cannot get wlan0 back up using rc network restart - I have to go in to
YaST, change the settings then change them back to what they were, and
apply the settings. As far as I knew YaST was basically doing the rc
network restart as I was not changing any settings. If YaST cannot
bring wlan0 back up I have to restart.
On every boot I must also manually bring wlan0 up and add a route. I
made a script for this but it's a real pain in the butt. I guess my
1) Does anyone have an idea what is going on with wlan0 and why the
card cannot read the signal?
2) Is there anyway I can get my wlan0 IP and route to stay even after reboot?
Any info or help would be great, thanks in advance =]
(By the way, I did get great joy from contacting Microsoft's Broadband
Networking support and thanking them for using the Prism chipset in
there cards - helping me get wireless working in Linux)
Well, as I mentioned briefly, I did "take the plunge."
Here are my observations so far:
- Enhancements to mailing list handling -- good
- Styled text composition -- good
- Quick Search bar -- nice
There are some glitches and shortcomings: The HTML formatting toolbar
and the command to show and hide it get out of sync. In-line
spell-checking is not available when composing styled email. There is a
problem with saving a style mail draft and then reopening it to continue
- Quick Search bar -- nice
- Window-Specific Settings -- This is a vast generalization of the old
"Save Window Settings" command in the "Advanced" sub-menu of the window
manager menu. I'm still figuring this out. It's clearly powerful, but
also somewhat perplexing.
- Idiosyncracies. Most of my panel functionality was really wacky at
first. Eventually I just turned each applet (in my case, Pager, Taskbar
and Tray) off and back on again and now they seem to be OK. The desktop
grid problem has been noted already but even after the manual update to
the appropriate configuration file, there's a problem. Some (but not all)
of the icons on my desktop are migrating north. Each login moves them up
a notch. The same thing happens each time I hide and re-show the panel. I
finally just turned of automatic grid alignment--It's not worth the
Some settings reverted to their default. The "Bell" setting reverted to
"System Bell." In fact, Notification appears reverts to System Bell
whenever it's restarted. I had a similar problem in (KDE 3.2.3) with the
history setting reverting to 1000 (from my own setting of 5000). I fixed
the history problem by quitting Konsole and editing its configuration
file by hand. After that the change "took." Maybe I'll have to try that
with the Bell configuration.
I know this is a pretty minimal "review," but my use of Linux / KDE is
very stylized--Lots of Web, email (KMail), Usenet (KNode), shell
(Konsole) and the rest is non-KDE applications (including Mozilla for Web
As a fix for a connection timeout problem I was having (stupid Cisco
firewall dropping a connection after 1 hour of idle time with no
notification on either end) I reduced the tcp keepalive time from the
default 2 hours to 45 minutes. When testing this, I simply changed the
value in /proc/sys/net/ipv4/tcp_keepalive_time. In order to get this to
apply on boot, I added:
net.ipv4.tcp_keepalive_time = 2700
to the sysctl.conf file.
Last week we had to move the server to a different rack. On bootup the
setting was lost (it was back at the default 7200).
On all other Linux systems I have (2 RH and a Gentoo), sysctl settings in
this file are applied on bootup. SUSE doesn't seem to care about it
(which explains why it was empty). Do I have to explicitly make the
sysctl call in one of the bootup scripts (and if so, which one), or is
there somewhere else I should be looking?