executing ntpdate on boot - seems it doesn't work

2007-02-17 Thread Rolf Bode-Meyer

Hi!

I currently try to figure out if ntpdate is called on boottime in my
system or not.

It *should* be called when the network interfaces come up (ifup),
therefore the /etc/network/if-up.d/ntpdate is present. And it's indeed
called when I manually call ifup -a after booting--an entry in the
syslog then shows something like "adjust time server ... offset ...".
But I don't see such a syslog entry for boottime, so I fear there's
something wrong. Any ideas what that could be or how to be sure
everything is ok?


And another oddity: ifup is called by the network script which is
rcS.d/S40networking. So if everything works well, ntpdate sets the
system clock at S40. But *after* that S50hwclock.sh calls hwclock
--hctosys which sets the system clock to the hardware clock.
So doesn't hwclock needs to be called before ntpdate?

Bye,
Robert


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: executing ntpdate on boot - seems it doesn't work

2007-02-19 Thread Rolf Bode-Meyer

Thanks to you all for replying.

Firstly I have to admit that this particular system is actually not a real 
Debian system but Ubuntu. I wrote here because I wrongly assumed both 
distributions are more similar then they are. And because Debian users 
knowledge about the system is better than Ubuntu users'.
I'm sorry for this abuse.


If it manually works, maybe you can add more lines to your
/etc/network/if-up/ntpdate file in order to track down where the
probleme comes from.


Inserting echos and log_daemon_msg into the ntpdate script wasn't that useful and the results confusing. 
But I was at least successfull in finding out that ntpdate-debian is indeed called and also contacts the servers: on the workstation I configured my server as ntp host and ran tcpdump there.

I didn't think of checking my server (running Debian Etch) before - my fault. 
The bootup script works there and ntpdate also shows up in the syslog. So the 
difference in Ubuntu must lay in upstart or so.


It would be odd to do it in a different way. I have checked my rcS.d directory,
and I have : S11hwclock and S40networking.


True, that's what my Etch server looks like too.
While I also don't get what that S18hwclockfirst.sh and S50hwclock of Sarge are 
about.

Greets,
Rolf


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Is kernel update not up to date?

2006-09-30 Thread Rolf Bode-Meyer

Hi!

On 2006-09-27 I did apt-get update && upgrade once again and got a new
kernel image (2.6.8-3-powerpc 2.6.8-12sarge5). In the advisory
DSA-1184-2 one can read "Date Reported: 25 Sep 2006".

But looking at /boot I see "2006-09-07 06:54 vmlinux-2.6.8-3-powerpc"
- so that image is nearly three weeks old.

What's up there?

RoBoMe


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]