Bug 11545 - Problems with daytime (internal)
Summary: Problems with daytime (internal)
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: inetd   
(Show other bugs)
Version: 6.2
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: elale
QA Contact:
Depends On: 10786
TreeView+ depends on / blocked
Reported: 2000-05-21 02:08 UTC by elale
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-07-16 07:59:17 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
daytime/time close-wait problem patch. (469 bytes, patch)
2000-07-16 19:47 UTC, Pekka Savola
no flags Details | Diff

Description elale 2000-05-21 02:08:03 UTC
I use the service daytime in my private lan with an linux-box as a time
server trugh inetd (internal service daytime - port 13) the definition in
/etc/services is right and the definition in /etc/inetd.conf too, but with
the inetd of inetd-0.16-4.i386.rpm don't work; the same configuration with
the inetd of the netkit-base-0.10-37.i386.rpm works fine. I can send my
files if you wish. Regards

Comment 1 Pekka Savola 2000-07-15 14:18:55 UTC
0.16-4 works for me just fine.

The entry should be:

daytime stream  tcp     nowait  root    internal

Make sure you're not mistaking about UDP/TCP.

[root@lokki /root]# telnet localhost daytime
Connected to localhost.localdomain.
Escape character is '^]'.
Sat Jul 15 17:16:09 2000
telnet> quit
Connection closed.

Comment 2 Pekka Savola 2000-07-16 19:46:22 UTC
Actually, this is caused by a small bug in inetd.  It affects both daytime and
time tcp servers.

Inetd has been replaced with xinetd in Rawhide so this is kinda moot point, but
here's a patch (based on #10786) if you're interested.

Comment 3 Pekka Savola 2000-07-16 19:47:19 UTC
Created attachment 1190 [details]
daytime/time close-wait problem patch.

Note You need to log in before you can comment on or make changes to this bug.