Hi,
This is what I have used.
I could not find the url but it works on my Dachstein Floppy and CD routers
About time servers, I got mine from a search for "time server" on the net
Sergio
From:
Charles Steinkuehler <[EMAIL PROTECTED]>
Thu 7:21 PM
Subject:
Re: [LRP] portsentry/ntp/logging...
To:
William Clements <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Updated April 1, 2001 with new URL's, and new updatetime procedure for LRP
2.9.x users.
> One more... I have and internal machine acting as an ntp server and
> I 'm wondering how I can get lrp to sync from this machine. I've noticed
> a few posts floating by on this issue, but my understanding of this
> issue is minimial so I require a little more hand-holding...
Well, I don't run psentry, and haven't set up remote logging yet, but I can
help with the time thing. I posted a nice summary about LRP and timezones
and such a while ago...I thought rick would have stuck this on his site, but
apparently not, so here it is again.
For those keeping score at home, since I posted this, it has been noted that
LRP 2.9.x systems are missing the hwclock command, which can be found on my
site as part of the utilities package (put the binary in /sbin):
http://lrp.steinkuehler.net/files/packages/Utilities/hwclock
Also, LRP 2.9.x distributions don't automatically set the hardware clock to
the current time the way Materhorn/Eiger systems do (since the hwclock
command is missing). To fix this, replace the updatetime procedure in
/etc/cron.daily/multicron-d with the procedure below:
Old updatetime routine:
updatetime () {
[ "$lrp_DATE_SERVER" != "" ] && qt rdate $lrp_DATE_SERVER
}
New updatetime routine:
updatetime () {
[ -f /etc/default/rcS ] && . /etc/default/rcS
[ "$GMT" = "-u" ] && GMT="--utc"
if [ -n "`ps axc | grep xntpd`" ]; then
hwclock --systohc $GMT
else
[ "$lrp_DATE_SERVER" != "" ] \
&& rdate -s $lrp_DATE_SERVER \
&& sleep 2 && hwclock --systohc $GMT
fi
}
Finally, it seems that the LRP 2.9.4 date command does not support any of
the fancy formatting commands listed, and doesn't seem to know about
timezones...anyone with a 2.9.4 system want to fill in the missing pieces
for setting up your local time-zone?
<Here's the original post>
I finally have an understanding of how TimeZones, localtime, and the
hardware clock are configured on LRP. Thanks to Karl for posting how to get
automatic time updates working, which prompted me to (finally) get my
timezone configured properly. Here's a summary of what I've found:
All unix systems run on UTC, or 'universal' time. This allows servers from
around the world to communicate with a consistent view of 'time'. To make
life easy for the local user, the system typcially reports times and dates
adjusted to a local time zone.
To further complicate matters, on PC's (typical LRP hardware) the hardware
'CMOS' clock can be set to local time (typical for DOS/WIN machines) or UTC
(typical for unix only machines). LRP can handle either setting, although I
suggest setting your hardware clock to UTC, as your LRP machine is not
likely to 'multiboot' into DOS or Windows :)
OK, so how do you make it work already?!?
Some useful commands to see if your LRP system is setup properly...
Display local system time:
date
Display UTC time:
date -u
Display current TimeZone:
date +%Z
Display current TimeZone offset from UTC:
date +%z
Display current time from the CMOS clock (no adjustments made for local/UTC
time, so this is the actual CMOS clock setting)
hwclock --show
OK, now to make things work...
To set up the proper timezone, simply replace /etc/localtime with a timezone
file appropriate for your local. You can use the timezone files from a
Debian release (in /user/share/zoneinfo) or download the appropriate
timezone file from my website:
http://lrp.steinkuehler.net/files/kernels/zoneinfo/
Use the date commands above to verify your new zoneinfo file is
working properly (no reboot required).
To define the setting of your CMOS clock (set to UTC or local time), edit
/etc/default/rcS, and set the value of GMT appropriately:
CMOS clock set to UTC
GMT="-u"
CMOS clock set to local time
GMT=""
Finally, as stated previously, to have LRP automatically update your clock
settings to a network clock server, edit /etc/lrp.conf and set
lrp_DATE_SERVER=<timeserver>
NOTE: There are several different time protocols availble. The rdate
command, used by LRP uses the RFC868 protocol which is usually implemented
as a built-in service of inetd.
Charles Steinkuehler
http://lrp.steinkuehler.net
http://c0wz.steinkuehler.net (lrp.c0wz.com mirror)
_______________________________________________
linux-router maillist - [EMAIL PROTECTED]
http://www.linuxrouter.org/mailman/listinfo/linux-router
http://lrp.steinkuehler.net/Packages/Utilities.htm
-----Mensaje original-----
De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Enviado el: Monday, January 21, 2002 13:46
Para: [EMAIL PROTECTED]
Asunto: [Leaf-user] Keeping system date upto date
sadly, my eigerBeta2 based router must operate under some Draconian
operating perameters (due to it being in the same room as where my wife
studies for exams) .. hence it must be ultra quiet. I have implemented
this by using a friends old (5+ years old!) laptop with the Hard disk
removed. It does operate without any noise whatsoever, but lately I had
received complaints about the rather loud fan that would go on
intermittently (usually I wasn't even using the connection when this
happened) ... I found a setting in the BIOS to drop the laptop into
a low power state when no activity was detected. ( Yes, I know that a
router that enters sleep mode after a few minutes is indeed a sad
beast, but such is my predicament!)
This works great, no more fan going on, and the power light turns
yellow from green. No problems with using the network connection, the
pcmcia cards seem to stay powered on, and as soon as I connect to a
website on the outside or externally to the router via ssh, it works
(without any noticeable lag in response time as it 'wakes up').
The trouble is that the routers time gets screwed up, as it doesnt seem
to get updated when it is 'sleeping'. hence the uptime command is way,
way off, and worse yet, timestamps on the logs are not accurate either!
Looking through /etc/lrp.conf, I have seen a setting there for a date
server that would be connected to in order to get the correct time. Has
anyone used this? More importantly, can anyone list for me the date
servers that they use? I have not ever used one of these before, and am
in the Pacific Timezone. Also, what changes (if any) are required in
the firewall rules (i.e. are there ports that need to be opened for the
server(s) ????)
Thanks for any replies!
_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
