[@

@] At least for ntpclient version 2007_365-1

Chong Lee adds: Or you could use the -q flag: /opt/sbin/adjtimex -q -t 10000

RF: (30Oct2008) The documentation for ntpclient says:

RF: (30Oct2008) The documentation for ntpclient says:

On to ntpclient -l. This is actually easy, if you performed and understood

RF: (30Oct2008) The documentation for ntpclient says: \\\

     ntpclient -l -h $NTPHOST

   On to ntpclient -l.  This is actually easy, if you performed and understood

RF: (30Oct2008) The documentation for ntpclient says:\\

On to ntpclient -l. This is actually easy, if you performed and understood

   the previous steps.  Run
     ntpclient -l -h $NTPHOST
   in the background.

(:linebreaks:)

(:nolinebreaks:)

On to ntpclient -l. This is actually easy, if you performed and understood

in the background.

which to me implies that you must deliberately run ntpclient in the background when using -l.

'''@@On to ntpclient -l. This is actually easy, if you performed and understood

in the background. @@'''

which to me implies that you must deliberately run ntpclient in the background when using -l.

RF: (30Oct2008) The documentation for ntpclient says:

@@On to ntpclient -l. This is actually easy, if you performed and understood the previous steps. Run

  ntpclient -l -h $NTPHOST

in the background. @@

which to me implies that you must deliberately run ntpclient in the background when using -l.

/opt/sbin/adjtimex -t 10000 >/dev/null

In Debian, tzconfig

 ****

Gordon Baskin adds:

The file /opt/etc/init.d/S10ntpclient could be changed to eliminate the output of adjtimex:

#!/bin/sh    
if [ -n "`pidof ntpclient`" ]; then    
    /bin/killall ntpclient 2>/dev/null    
fi    
/opt/sbin/adjtimex -t 10000 ''>/dev/null''    
/opt/bin/ntpclient -s -h pool.ntp.org > /var/log/ntp.log
/usr/sbin/hwclock --systohc --utc

In /etc/crontab , delete the line containing hwclock and replace it with the following:

1 * * * * root /opt/bin/ntpclient -s -h pool.ntp.org > /var/log/ntp.log && /usr/sbin/hwclock --systohc --utc

 ****

The -l parameter in the ntpclient command does not work in scripts on my NSLU2 (with Unslung 6.10beta) at all. In my case it stopped the NSLU2 boot procedure while executing the /opt/etc/init.d/S10ntpclient script which I found out only because the Ready/Status LED was still blinking after the boot procedure should have finished.

 chmod +rx /opt/etc/init.d/S10ntpclient

The -s means to set the clock, -h selects the NTP host to get the time from, -l says to lock the local clock to the server (MicRo: -l does not work in scripts because the ntpclient -l command never completes which makes a script using the -l parameter hang!).\\

Make /opt/etc/init.d/S10ntpclient script executable:

pool.ntp.org is an organization that tries to make it easy for people to find a low-level NTP server that isn't too busy, the idea being to keep from overloading the higher-level servers as some clueless consumer electronics manufacturers have done in the past.

/unslung/rc.crond

#! /bin/sh
# Diversion script: customize before starting crond
#
# Reason: change the periodic update of the hwclock to use --adjust
#
if [ ! -e /etc/crontab.orig ]; then cp -p /etc/crontab /etc/crontab.orig; fi
sed -i -e 's/1 \* \* \* \* root \/usr\/sbin\/hwclock -s \&>\/dev\/null/1 \* \* \* \* root \/usr\/sbin\/hwclock --adjust --utc \&>\/dev\/null/' /etc/crontab
#
# Continue to start crond
#
return 1
# EOF - include this line

SHELL=/bin/sh
PATH=/sbin:/bin:/usr/sbin:/usr/bin
MAILTO=""
HOME=/
# ---------- ---------- Default is Empty ---------- ---------- #
0 0-23/8 * * * root /usr/sbin/CheckDiskFull &>/dev/null
0 0 * * * root /usr/sbin/WatchDog &>/dev/null
1 * * * * root /usr/sbin/hwclock --adjust --utc &>/dev/null

**** Don't copy crontab to your system; let the script do the edits ****

/opt/etc/init.d/S10ntpclient

#!/bin/sh
#
if [ -n "`pidof ntpclient`" ]; then
    /bin/killall ntpclient 2>/dev/null
fi
#
# Initialize kernel variables?
#
#/opt/sbin/adjtimex -t 10000
#
# Simple set first.  This will abruptly ensure that we are in sync with the server
# if the server responds, we'll set the hwclock to match the response
#
/opt/bin/ntpclient -s -l -h 0.pool.ntp.org > /var/log/ntp.log && hwclock --systohc --utc
#
# Now start daemon to keep us in sync
#
/opt/bin/ntpclient -i 600 -l -h 0.pool.ntp.org >> /var/log/ntp.log & 
# EOF - include this line

Edit July08 by MicRo\\

/usr/sbin/hwclock --systohc --utc

1 * * * * root /opt/bin/ntpclient -s -h pool.ntp.org > /var/log/ntp.log && /usr/sbin/hwclock --systohc --utc

Edit July08 MicRo
I took the freedom to edit this page and tried to make it better readable.
The -l parameter in the ntpclient command did not work on my NSLU2 (with Unslung 6.10beta) at all. In my case it stopped the NSLU2 boot procedure while executing the /opt/etc/init.d/S10ntpclient script which I found out only as the Ready/Status LED was still blinking after the boot procedure should have finished.

Create the file /opt/etc/init.d/S10ntpclient containing the following:

1 * * * * root /opt/bin/ntpclient -s -h pool.ntp.org > /var/log/ntp.log && hwclock --systohc --utc

Create the file /unslung/rc.rstimezone:

#! /bin/sh
# Diversion script to get control of time
#
# Extract the GUI timezone from the .conf file
# Copy the corresponding /usr/zoneinfo file over /usr/local/localtime
/usr/sbin/Set_TimeZone >/dev/null
#
# Adjust the hardware clock for accumulated drift
#
/usr/sbin/hwclock --adjust
#
# Initialize the kernel with the corrected time
#
/usr/sbin/hwclock --hctosys >/dev/null
#
# ntpclient will (shortly) start correcting the system clock
#
# The hwclock drift will be computed & recorded once an hour (crontab)
#
# Do not execute the linksys script
#
return 0
# EOF - include this line

Make /opt/etc/init.d/S10ntpclient and /unslung/rc.rstimezone script executable:

 chmod +rx /opt/etc/init.d/S10ntpclient /unslung/rc.rstimezone

Run the S10ntpclient script once by hand, and then it will run automatically every time you reboot.

The -s means to set the clock, -l says to lock the local clock to the server (MicRo: -l does not work on every NSLU2), and -h selects the ntp host.\\

[@

1. ! /bin/sh

Install ntpclient:

@]

[@

Make /opt/etc/init.d/S10ntp script executable:

Run the S10ntp script once by hand, and then it will run automatically every time you reboot.

/unslung/rc.rstimezone

[@

1. ! /bin/ash
2. Diversion script to get control of time
4. Extract the GUI timezone from the .conf file
5. Copy the corresponding /usr/zoneinfo file over /usr/local/localtime

/usr/sbin/Set_TimeZone >/dev/null

2. Adjust the hardware clock for accumulated drift

/usr/sbin/hwclock --adjust

2. Initialize the kernel with the corrected time

/usr/sbin/hwclock --hctosys >/dev/null

2. ntpclient will (shortly) start correcting the system clock
4. The hwclock drift will be computed & recorded once an hour (crontab)
6. Do not execute the linksys script

return 0

1. EOF - include this line

/unslung/rc.crond

 #! /bin/sh
 # Diversion script: customize before starting crond

 # Reason: change the periodic update of the hwclock to use --adjust

 if [ ! -e /etc/crontab.orig ]; then cp -p /etc/crontab /etc/crontab.orig; fi
 sed -i -e 's/1 \* \* \* \* root \/usr\/sbin\/hwclock -s \&>\/dev\/null/1 \* \* \* \* root \/usr\/sbin\/hwclock --adjust --utc \&>\/dev\/null/' /etc/crontab

 # Continue to start crond

 return 1

Edit July08 MicRo?
I took the freedom to edit this page and tried to made it better readable.
The -l parameter in the ntpclient command did not work on my NSLU2 (with Unslung 6.10beta) at all. In my case it stopped the NSLU2 boot procedure while executing the /opt/etc/init.d/S10ntp script which I found out only as the Ready/Status LED was still blinking after the boot procedure should have finished. Consequently I removed the -l parameter out of the scripts below.

The Slug (NSLU2) has buggy timekeeping facilities, which Cisco apparently tried to fix, but didn't do a very good job of fixing. As of January 2008, on an Unslung system, bcrowell observed that the clock was set to 1999 by default, and setting it correctly didn't "stick" across reboots. This causes all kinds of problems with file synchronization, unpacking tarballs, etc. The following is a fix for the problem for Unslung 6.8:

Edit July08 \MicRo?

The -l parameter in the ntpclient command did not work on my NSLU2 (with Unslung 6.10beta) at all. In my case it stopped the NSLU2 bootprocedure which I found out as the Ready/Status LED was still blinking after the boot up should have finished.

Explanation:

The adjtimex line changes the rate at which the system clock runs by 1% relative to the factory default. See the technical explanation at http://www.culcon.com/~henry/nslu2.html.\\

The -s means to set the clock, -l says to lock the local clock to the server (\MicRo?: -l does not work on every NSLU2), and -h selects the ntp host.\\

Edit July08 MicRo? I took the freedom to edit this page and tried to made it better readable.

I found the -l parameter in the ntpclient command to be problematic. In my case it stopped the NSLU2 bootprocedure which I found out as the Ready/Status LED was still blinking. Consequently I removed the -l parameter out of the procedures below.

Edit Jan08 JW - Below was found to be problematic. Solution was to

Explanation:

The adjtimex line changes the rate at which the system clock runs by 1% relative to the factory default. See the technical explanation at http://www.culcon.com/~henry/nslu2.html.\\ There's a man page for adjtimex at http://linuxcommand.org/man_pages/adjtimex8.html .

Documentation for the ntpclient command is available at http://doolittle.icarus.com/ntpclient/ .
The -s means to set the clock, -l says to lock the local clock to the server (MicRo?: does not work on every NSLU2), and -h selects the ntp host.\\ Pool.ntp.org is an organization that tries to make it easy for people to find a low-level NTP server that isn't too busy, the idea being to keep from overloading the higher-level servers as some clueless consumer electronics manufacturers have done in the past.

The crontab sets the clock once per hour, and copies the resulting time to the hardware clock.

1. I think ntpclient is normally meant to run continuously in the background. However, this setup seems to run it and then terminate it, starting it again later based on a cron job. This would have the advantage of not taking up memory by having ntpclient always running. Is this correct?
2. The scripts use > rather than >> to write to ntp.log. I assume this is because old ntp log entries are not of interest, and there's no point in gradually using up more and more disk space. Is this correct?

Edit Jan08 JW - below was found to be problematic

• make sure you have both crond (linksys) and cron running
• ipkg install ntp
• ntpdate pool.ntp.org

In /etc/crontab , delete the line containing hwclock and replace it with the following:

Make /opt/etc/init.d/S10ntp executable

 chmod +rx /opt/etc/init.d/S10ntp

The adjtimex line changes the rate at which the system clock runs by 1% relative to the factory default. See the technical explanation at http://www.culcon.com/~henry/nslu2.html. There's a man page for adjtimex at http://linuxcommand.org/man_pages/adjtimex8.html .

[@

@] Create the file /opt/etc/init.d/S10ntp containing the following:

1 * * * * root /opt/bin/ntpclient -s -h pool.ntp.org >> /var/log/ntp.log && hwclock --systohc --utc

[@

/opt/bin/ntpclient -s -h pool.ntp.org > /var/log/ntp.log

    1 * * * * root /opt/bin/ntpclient -s -l -h pool.ntp.org >> /var/log/ntp.log && hwclock --systohc --utc

#!/bin/sh    
if [ -n "`pidof ntpclient`" ]; then    
    /bin/killall ntpclient 2>/dev/null    
fi    
/opt/sbin/adjtimex -t 10000    
/opt/bin/ntpclient -s -l -h pool.ntp.org > /var/log/ntp.log
hwclock --systohc --utc

_______________

edit Jan08 JW - below was found to be problematic solution was to make sure you have both crond (linksys) and cron running ipkg install ntp ntpdate pool.ntp.org and that is all if you set cron (/opt/etc/crontab) to ntpdate regularly _______________

ipkg install ntpclient

Install the ntpclient package

install the ntpclient package

    ipkg install ntpclient

The above is an attempt by me (bcrowell) to summarize and organize some previous material. Here are some questions I have. If my understanding of these points is correct, please change them to affirmative statements.

The above is an attempt by bcrowell to summarize and organize some previous material. Here are some questions I have at this point. If my understanding of these points is correct, please change them to affirmative statements.

1. I think ntpclient is normally meant to run continuously in the background. However, this setup seems to run it and then terminate it, starting it again later based on a cron job. This would have the advantage of not taking up memory by having ntpclient always running. Is this correct?

2. The scripts use > rather than >> to write to ntp.log. I assume this is because old ntp log entries are not of interest, and there's no point in gradually using up more and more disk space. Is this correct?

In /etc/crontab , DELETE THE HWCLOCK LINE, and replace it with the following:

The crontab sets the clock once per hour, and copies the resulting time to the hardware clock.

    /opt/bin/ntpclient -s -l -h pool.ntp.org > /var/log/ntp.log
    hwclock --systohc --utc

In /etc/crontab , replace the hwclock line with the following:

    1 * * * * root /opt/bin/ntpclient -s -l -h pool.ntp.org > /var/log/ntp.log && hwclock --systohc --utc

The -s means to set the clock, -l says to lock the local clock to the server, and -h selects the ntp host. Pool.ntp.org is an organization that tries to make it easy for people to find a low-level ntp server that isn't too busy, the idea being to keep from overloading the higher-level servers as some clueless consumer electronics manufacturers have done in the past.

Explanation: (In the following, the xhttp stuff is because a security misfeature in the wiki wouldn't let me add links with http.)

The slug has buggy timekeeping facilities, which Cisco apparently tried to fix, but didn't do a very good job of fixing. As of January 2008, on an Unslung system, bcrowell observed that the clock was set to 1999 by default, and setting it correctly didn't "stick" across reboots. This causes all kinds of problems with file synchronization, unpacking tarballs, etc. The following is a fix for the problem for Unslung 6.8:

Remove the hwclock line from /etc/crontab.

In the second ntpclient line, the -l says to lock the local clock to the server, and by default this is done every 10 minutes.

The adjtimex line changes the rate at which the system clock runs by 1% relative to the factory default. See the technical explanation at xhttp://www.culcon.com/~henry/nslu2.html . There's a man page for adjtimex at xhttp://linuxcommand.org/man_pages/adjtimex8.html .

Documentation for the ntpclient command is available at xhttp://doolittle.icarus.com/ntpclient/ . In the first ntpclient line, -s means to set the clock, and -h selects the ntp host. Pool.ntp.org is an organization that tries to make it easy for people to find a low-level ntp server that isn't too busy, the idea being to keep from overloading the higher-level servers as some clueless consumer electronics manufacturers have done in the past.

The adjtimex line changes the rate at which the system clock runs by 1% relative to the factory default. See the technical explanation at xhttp://www.culcon.com/~henry/nslu2.html .

The adjtimex line changes the rate at which the system clock runs by 1% relative to the factory default. See the technical explanation at .

The adjtimex line changes the rate at which the system clock runs by 1% relative to the factory default.

See http://en.wikipedia.org/wiki/Network_Time_Protocol for an explanation of what NTP is.

Run the script once by hand, and then it will run automatically every time you reboot.

Explanation:

Create the file /opt/etc/init.d/S10ntp containing the following:

    #!/bin/sh    
    if [ -n "`pidof ntpclient`" ]; then    
        /bin/killall ntpclient 2>/dev/null    
    fi    
    /opt/sbin/adjtimex -t 10000    
    /opt/bin/ntpclient -s -h pool.ntp.org > /var/log/ntp.log
    /opt/bin/ntpclient -l -h pool.ntp.org > /var/log/ntp.log &  

chmod +rx /opt/etc/init.d/S10ntp

The slug has buggy timekeeping facilities, which Cisco says they're going to fix in the future. As of January 2008, on an Unslung system, bcrowell observed that the clock was set to 1999 by default, and setting it correctly didn't "stick" across reboots. This causes all kinds of problems with file synchronization, unpacking tarballs, etc. The following is a fix for the problem for Unslung 6.8:

The slug has buggy timekeeping facilities, which Cisco says they're going to fix in the future. As of January 2008, on an Unslung system, bcrowell observed that the clock was set to 1999 by default, and setting it correctly didn't "stick" across reboots. This causes all kinds of problems with file synchronization, unpacking tarballs, etc. The following is a fix for the

The slug has buggy timekeeping facilities, which Cisco says they're going to fix in the future. As of January 2008, on an Unslung system, bcrowell observed that the clock was set to 1999 by default, and setting it correctly didn't "stick" across reboots. This causes all kinds of problems with file synchronization, unpacking tarballs, etc. The following is a fix for the problem:

The slug has buggy timekeeping facilities, which Cisco says they're going to fix in the future. As of January 2008, on an Unslung system, bcrowell observed that the clock was set to 1999 by default, and setting it correctly didn't "stick" across reboots. This causes all kinds of problems with file synchronization, unpacking tarballs, etc. The following is a fix for the problem:

1. ipkg install ntpclient

See http://en.wikipedia.org/wiki/Network_Time_Protocol for an explanation of what NTP is.

NB: This timer problem has now been fixed in the Openslug & UcSlugC source HEAD.

NB: This timer problem has now been fixed in the Openslug & UcSlugC source HEAD. test

In Debian, tzconfig

In Debian, tzconfig

TEST

Now our clock gets set every hour (roughly: if there are no errors)

Check /var/log/messages to see if your crond is running okay!

Don't forget to set your timezone

In Debian, tzconfig

Be sure to name and place them exactly as specified. Be sure to delete the leading space from each line. And be sure that you get the very long lines -- without wrapping. [but note: you've spelled rstimezone two different ways! :^)]

NB: This timer problem has now been fixed in the Openslug & UcSlugC source HEAD.

Why waste your precious memory?

Note: If you extract these scripts, delete the first space on each line -- the wiki gets upset without them, and shell will get upset with them. :-)

Why waist your precious memory? I added this line to the crontab:
"1 * * * * root /opt/bin/ntpclient -s -l -h 0.pool.ntp.org > /var/log/ntp.log && hwclock --systohc --utc"
and removed the line "1 * * * * root /usr/sbin/hwclock -s &>/dev/null"
Now our clock gets set every hour (rouhly: if there are no errors)

Check /var/log/messages to see if your crond is running okay!

The requisite scripts are provided below. The diversion script edits, rather than replaces, crontab. This will minimize interactions with other users of crontab.

It would be nice if the ntpclient kit were updated with these, but I don't have time at the moment..

Also, remember to:

    chmod +x /unslung/rc.rstimezone /unslung/rc.crond /opt/etc/init.d/S10ntpclient

Be sure to name and place them exactly as specified. Be sure to delete the leading space from each line. And be sure that you get the very long lines -- without wrapping.

 # Adjust the hardware clock for accumulated drift

 # EOF - include this line

 # EOF - include this line

/etc/crontab After editing, it will look like this. The original is saved as crontab.orig.

 **** Don't copy crontab to your system; let the script do the edits ****

 # EOF - include this line

I've done a bit of work on this. Here's a scheme that keeps the hardware clock in-line, gets an accurate time at boot, and runs the client.

• When crond initializes, we edit /etc/crontab to get the hourly updates

The requisite scripts are provided below. It would be nice if the ntpclient kit were updated with these, but I don't have time at the moment..

Update: I changed the diversion script to edit, rather than replace, crontab. This will minimize interactions with other users of crontab.

 # Diversion script: customize before starting crond

 if [ ! -e /etc/crontab.orig ]; then cp -p /etc/crontab /etc/crontab.orig; fi
 sed -i -e 's/1 \* \* \* \* root \/usr\/sbin\/hwclock -s \&>\/dev\/null/1 \* \* \* \* root \/usr\/sbin\/hwclock --adjust --utc \&>\/dev\/null/' /etc/crontab

/opt/etc/crontab After editing, it will look like this. The original is saved as crontab.orig.

NOTE: http://www.pool.ntp.org/

I've done a bit of work on this. Here's a scheme that keeps the hadware clock in-line, gets an accurate time at boot, and runs the client.

• Early in boot, rc.rsttimezone initializes the timezone, calibrates the hardware clock, and sets the initial time.
• When crond initializes, we replace crontab with the copy in /opt/etc to get the hourly updates
• When the network comes up, S10ntpclient gets the network time, sets the system time, and starts the daemon.
• From then on, the client keeps the system time accurate, and the crond job keeps the hardware clock accurate.

The requisite scripts are provided below. it would be nice if the ntpclient kit were updated with these, but I don't have time at the moment..

Enjoy,

    --tlhackque

/unslung/rc.rstimezone

 #! /bin/ash
 # Diversion script to get control of time
 #
 # Extract the GUI timezone from the .conf file
 # Copy the corresponding /usr/zoneinfo file over /usr/local/localtime
 /usr/sbin/Set_TimeZone >/dev/null
 #
 # Adjust the harware clock for accumulated drift
 #
 /usr/sbin/hwclock --adjust
 #
 # Initialize the kernel with the corrected time
 #
 /usr/sbin/hwclock --hctosys >/dev/null
 #
 # ntpclient will (shortly) start correcting the system clock
 #
 # The hwclock drift will be computed & recorded once an hour (crontab)
 #
 # Do not execute the linksys script
 #
 return 0

/unslung/rc.crond

 #! /bin/sh
 # Diversion script: replace crontab with customized one before starting crond
 #
 # Reason: change the periodic update of the hwclock to use --adjust
 #
 if [ -e /opt/etc/crontab ]; then cp -fp /opt/etc/crontab /etc/crontab; fi
 #
 # Continue to start crond
 #
 return 1

Note: You can't use a symbolic link; crond gets very upset!

/opt/etc/crontab

 SHELL=/bin/sh
 PATH=/sbin:/bin:/usr/sbin:/usr/bin
 MAILTO=""
 HOME=/
 # ---------- ---------- Default is Empty ---------- ---------- #
 0 0-23/8 * * * root /usr/sbin/CheckDiskFull &>/dev/null
 0 0 * * * root /usr/sbin/WatchDog? &>/dev/null
 1 * * * * root /usr/sbin/hwclock --adjust --utc &>/dev/null

/opt/etc/init.d/S10ntpclient

 #!/bin/sh
 #
 if [ -n "`pidof ntpclient`" ]; then
     /bin/killall ntpclient 2>/dev/null
 fi
 #
 # Initialize kernel variables?
 #
 #/opt/sbin/adjtimex -t 10000
 #
 # Simple set first.  This will abruptly ensure that we are in sync with the server
 # if the server responds, we'll set the hwclock to match the response
 #
 /opt/bin/ntpclient -s -l -h 0.pool.ntp.org > /var/log/ntp.log && hwclock --systohc --utc
 #
 # Now start daemon to keep us in sync
 #
 /opt/bin/ntpclient -i 600 -l -h 0.pool.ntp.org >> /var/log/ntp.log & 

Note: If you extract these scripts, delete the first space on each line -- the wiki gets upset without them, and shell will get upset with them. :-)

    /opt/sbin/adjtimex -t 10000

Update The above still does a much better job than the "fix" by Linksys, but if you choose to follow the above instructions, you'll need to edit /etc/crontab to remove the cron task that Linksys added to sync with the hardware clock.

Update 2 ntpclient is available as ipkg package: On the NSLU2 run:

    ipkg install ntpclient

This just installs ntpclient. I have also added a startscript: /opt/etc/init.d/S10ntpclient:

    #!/bin/sh

    if [ -n "`pidof ntpclient`" ]; then
        /bin/killall ntpclient 2>/dev/null
    fi

    /opt/bin/adjtimex -t 10000
    /opt/bin/ntpclient -i 600 -l -h 0.pool.ntp.org > /var/log/ntp.log &

NOTE: Remember to remove the hwclock line from /etc/crontab

NOTE: http://www.pool.ntp.org/

This page pre-dates the R25 firmware, and so may conflict with the fix that Linksys made. If you have more information on this, please write it here.

Update The above still does a much better job than the "fix" by Linksys, but if you choose to follow the above instructions, you'll need to edit /etc/crontab to remove the cron task that Linksys added to sync with the hardware clock.

http://www.culcon.com/~henry/nslu2.html

This page pre-dates the R25 firmware, and so may conflict with the fix that Linksys made. If you have more information on this, please write it here.