Bug 62688 - kotalk and ktalk config in /etc/xinetd.d is broken
kotalk and ktalk config in /etc/xinetd.d is broken
Status: CLOSED RAWHIDE
Product: Red Hat Public Beta
Classification: Retired
Component: kdenetwork (Show other bugs)
skipjack-beta1
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Trond Eivind Glomsrxd
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-04-04 09:43 EST by Thomas Hopfner
Modified: 2007-04-18 12:41 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-04-04 09:43:49 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Thomas Hopfner 2002-04-04 09:43:43 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.78 [en] (X11; U; OSF1 V4.0 alpha; Nav)

Description of problem:
xinetd gives the following errors:
Mar 31 14:35:16 localhost xinetd[924]: Reading included configuration file:
/etc/xinetd.d/kotalk [line=15]
Mar 31 14:35:16 localhost xinetd[924]: Service talk: missing '{'
[line=5]
Mar 31 14:35:16 localhost xinetd[924]: Reading included configuration file:
/etc/xinetd.d/ktalk [line=11]
Mar 31 14:35:16 localhost xinetd[924]: Service ntalk: missing '{' [line=5]


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. make sure ktalkd-3.0.0-0.cvs20020321.1 is installed
2. service xinetd restart
3. watch /var/log/messages
	

Actual Results:  xinetd complains about missing "{"

Expected Results:  xinetd should read its config files without errors

Additional info:

The braces after "service (n)talk" need to be in the next line and are
not allowed to be in the same line.
Comment 1 Trond Eivind Glomsrxd 2002-04-04 10:35:59 EST
Fixed in recent versions of ktalkd (which makes it not an xinetd bug anyway...),
like 3.0.0-2

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