Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: tlug: Time
- To: tlug@example.com
- Subject: Re: tlug: Time
- From: "Petersen Jens-Ulrik (NRC/Tokyo)" <jens-ulrik.petersen@example.com>
- Date: 07 Sep 1999 10:30:50 +0900
- Content-Type: text/plain; charset=us-ascii
- In-Reply-To: "Stephen J. Turnbull"'s message of "Mon, 6 Sep 1999 18:16:58 +0900 (JST)"
- References: <19990907172226.A4220@example.com> <14291.34442.569917.786585@example.com>
- Reply-To: tlug@example.com
- Sender: owner-tlug@example.com
- User-Agent: Gnus/5.070096 (Pterodactyl Gnus v0.96) XEmacs/21.1 (Arches)
"Stephen J. Turnbull" <turnbull@example.com> writes: > >>>>> "FB" == "Frank Bennett" <bennett@example.com> writes: > > FB> There is a timed daemon on the new system, which I hooked up > FB> for service in /etc/inetd.conf. Sure enough, I now get a time > FB> back from this machine when I rdate against it from the other > FB> servers (running TL 3.0 at present). There's a timed in Redhat 6.0 too, in the "timed" package, though I don't use it myself: I synchronize my Linux box to our local unix servers with xntp. > I don't seem to have a timed installed on any of my Debian systems; in > fact, I can't even seem to find a package which provides it. But all > of my systems seem to give sensible responses to rdate inquiries. Out > of curiosity, I checked 133.6.33.1, and it's still giving exactly the > same date: Mon Apr 28 01:25:08 1952. > According to the rdate manpage, RFC 868 is "usually implemented" in > inetd, not a separate server. And in fact grepping /etc/inetd.conf > and /etc/services gives Yes, I think rdate and timed are not related, probably timed implements an alternative to ntp. > daytime stream tcp nowait root internal > #daytime dgram udp wait root internal > time stream tcp nowait root internal > #time dgram udp wait root internal Thanks for the tip: I realized that rdat'ing my own machine didn't work so I went to inetd.conf and sure enough the time/tcp line was commented out. Works now. > BTW, if you're still interested in CODA, 5.2.7 is definitely usable > (on i386 systems, for the first time since about 4.6.5 when I first > tried it). 5.3.1 is out, but I don't know how reliable it is. And > I dunno if it works on Sparc, yet. What was CODA again? Jens ------------------------------------------------------------------- Next Nomikai: September 17 (Fri), 19:30 Tengu TokyoEkiMae 03-3275-3691 Next Technical Meeting: October 9 (Sat), 13:00 place: Temple Univ. ------------------------------------------------------------------- more info: http://www.tlug.gr.jp Sponsor: Global Online Japan
- Follow-Ups:
- tlug: CODA [was: Time]
- From: "Stephen J. Turnbull" <turnbull@example.com>
- References:
- tlug: Time
- From: "Frank Bennett (=?iso-2022-jp?B?GyRCJVUlaSVzJS8kWSVNJUMlSBsoQg==?= )" <bennett@example.com>
- tlug: Time
- From: "Stephen J. Turnbull" <turnbull@example.com>
Home | Main Index | Thread Index
- Prev by Date: tlug: Green Frog 0.4 Development
- Next by Date: tlug: CODA [was: Time]
- Prev by thread: tlug: Time
- Next by thread: tlug: CODA [was: Time]
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links