xref: /illumos-gate/usr/src/man/man8/in.daytimed.8 (revision bbf21555)
Copyright (c) 2004, Sun Microsystems, Inc. All Rights Reserved
The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
IN.DAYTIMED 8 "Aug 23, 2004"
in.daytimed - UDP or TCP daytime protocol service daemon


FMRI svc:/internet/daytime:default

FMRI stands for Fault Management Resource Identifier. It is used to identify resources managed by the Fault Manager. See fmd(8) and smf(7).

The in.daytimed service provides the server-side of the daytime protocol. This protocol is used for debugging and bandwidth measurement and is available on both TCP and UDP transports, through port 13.

The in.daytimed service is an inetd(8) smf(7) delegated service. The in.daytimed detects which transport is requested by examining the socket it is passed by the inetd daemon. TCP-based service

Once a connection is established, the in.daytimed generates the current date and time in ctime(3C) format as 7-bit ASCII and sends it through the connection. The server then closes the connection. Any data received from the client side of the connection is discarded.

UDP-based service

The in.daytimed listens for UDP datagrams. When a datagram is received, the server generates the current date and time in ctime(3C) format as 7-bit ASCII and inserts it in a UDP datagram sent in response to the client's request. Any received data is ignored.


See attributes(7) for descriptions of the following attributes:

Interface Stability Evolving

attributes (7), smf (7), inetd (8)

RFC 867