According to T. Sean: While burning my CPU.
>
> On 3/20/99 17:26, Ray Olszewski at [EMAIL PROTECTED] wrote:
>
> >
> >Checking /etc/services is not enough. You need to check /etc/inetd.conf and
> >see if the time service is being run or is commented out (has # as first
> >character in the line).
> >
> >Older distributions defaulted to running almost every inetd service. As this
> >was increasingly recognized as a security weakness, most moved to running
> >only the few services that even beginners would know about, like telnet and
> >ftp, and commenting the others out (based on the assumption that if you knew
> >enough about the service to want it, you also knew how to activate it).
> >
> >If it is commented out in inetd.conf, just uncomment the line, save the
> >file, and restart inetd.
> >
>
> Ray and Richard,
>
> Thanks for your pointers to inetd and inetd.conf. I don't have this
> thing completely worked out yet, but due to your help, I was able to
> follow the inetd trail to several man pages and eventually
> /usr/doc/packages/xntp. As you have said so often, Richard, there is a
> great deal of information available on one's own machine. You just have
> to read it.
>
> As I said, I haven't gotten this thing completely licked yet. It looks
> like I will have to set up xntpd to start at boot, and I may have to add
> a line or two to my inetd.conf file. I will let you know how it works
> out.
>
I have never used ntpdate, however a normal timeserver on a Redhat 4.2
machine has the following in /etc/inetd.conf
time stream tcp nowait root internal
time dgram udp wait root internal
In /etc/services
time 37/tcp timserver
time 37/udp timserver
I love the way they spel it /etc/services "timserver"
That must be an origanal typo, as its been like that for years..
I only use "netdate" i belive oanother possablity is "rdate" as well.
> >At 06:08 AM 3/20/99 -0500, T. Sean (Theo) Schulze wrote [abridged]:
> >
> >>When I enter 'ntpdate -dv 192.168.0.3', I get an error message back
> >>saying "No server suitable for synchronization found". I can ping the
> >>other machine, 192.168.0.3 (the Linux box), just fine, so it is not a
> >>network problem. (At least, I don't know what I don't know that might
> >>make it a network problem.) ntpdate sends its packets to port 123, and
> >>my /etc/services shows ntp on that port with both tcp and ucp. So, that
> >>should work, shouldn't it?
>
> Cheers,
>
> Sean
>
>
> Theo. Sean Schulze
>
> [EMAIL PROTECTED] [EMAIL PROTECTED]
> **************************************************
> There are two major products that have come out of
> Berkeley: LSD and Unix. Is it just a coincidence?
>
>
--
Regards Richard.
[EMAIL PROTECTED]
