any DAYTIME server

Hi,

Does anybody aware of any DAYTIME server running now a days. Is 13 the
port number used for most of the DAYTIME servers? THANKS
Aamir

aamircheema@gmail.com wrote:
> Hi,
>
> Does anybody aware of any DAYTIME server running now a days. Is 13 the
> port number used for most of the DAYTIME servers? THANKS
> Aamir

I don't know of an implemented one, but any networking book will use
daytime as a get-your-feet-wet example. It's about 2 lines of code
wrapped in xinetd or similar.

I suggest, if your goal is clock synchronization, that you use ntpd
instead.

aamircheema@gmail.com wrote:
> Hi,

> Does anybody aware of any DAYTIME server running now a days. Is 13 the
> port number used for most of the DAYTIME servers? THANKS
> Aamir

Did you try

> grep daytime /etc/services
daytime 13/tcp # Daytime (RFC 867)
daytime 13/udp # Daytime (RFC 867)


--
Uwe Bonnes bon@elektron.ikp.physik.tu-darmstadt.de

Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

On 2 Aug 2006, in the Usenet newsgroup comp.os.linux.networking, in article
<1154533991.323380.105640@m73g2000cwd.googlegroups .com>, aamircheema@gmail.com
wrote:

>Does anybody aware of any DAYTIME server running now a days.

>NNTP-Posting-Host: 129.94.6.28

[compton ~]$ zgrep ' 129.94' IP.ADDR/stats/[ALR]*
IP.ADDR/stats/APNIC.gz:AU 129.94.0.0 255.255.0.0 allocated
[compton ~]$

Oz? No, not off the top of the head. time_a.timefreq.bldrdoc.gov in
Boulder, Colorado, USA _usually_ has a server running, but that's half
the way around the world from you, so accuracy is going to suck. But
then, you probably have one on your Linux box - it's built into the
network stack (an old inetd.conf file:)

#daytime stream tcp nowait root internal
#daytime dgram udp wait root internal

>Is 13 the port number used for most of the DAYTIME servers? THANKS

0867 Daytime Protocol. J. Postel. May 1983. (Format: TXT=2289 bytes)
(Also STD0025) (Status: STANDARD)

0868 Time Protocol. J. Postel, K. Harrenstien. May 1983. (Format:
TXT=3024 bytes) (Also STD0026) (Status: STANDARD)

1305 Network Time Protocol (Version 3) Specification, Implementation
and Analysis. D. Mills. March 1992. (Format: TXT=307085, PDF=442493
bytes) (Obsoletes RFC0958, RFC1059, RFC1119) (Status: DRAFT STANDARD)

4330 Simple Network Time Protocol (SNTP) Version 4 for IPv4, IPv6 and
OSI. D. Mills. January 2006. (Format: TXT=67930 bytes) (Obsoletes
RFC2030, RFC1769) (Status: INFORMATIONAL)

Pay your money - take your pick. "daytime' is port 13. 'time' is port 37.
NTP and SNTP is port 123. Actually, 'daytime' servers are not all that
common, as most everyone is using NTP.

Old guy

Not trying to beat a dead horse, but I guess I will anyway.

Daytime service returns a human-readable date. As far as time
synchronization goes, it is right next to worthless. Most of the
people who write one as their first network server use the output of
the "date" command and push it back out of the port.

I don't recall your ever saying exactly why you want daytime, if it
matters. If you're trying to experiment with socket programming it's
useful, but if you want to make your computer clock right then pretty
much every other network time scheme is better.

Ken Roberts <forums@hoverclub.net> wrote:
> I suggest, if your goal is clock synchronization, that you use ntpd
> instead.

Particularly as RFC 827 states that, "There is no specific syntax for
the daytime".

ntp is very easy to set up (or ntpdate if you're not permanently
connected). Use 0.XX.pool.ntp.org, 1.XX.pool.ntp.org, and
2.XX.pool.ntp.org for your servers, where XX is your country's ISO code,
and you'll be a happy bunny ever after.

Chris