Bug 62136 - syntax error in /etc/xinetd.d/ktalk and kotalk
Summary: syntax error in /etc/xinetd.d/ktalk and kotalk
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: kdenetwork   
(Show other bugs)
Version: skipjack-beta1
Hardware: i386 Linux
medium
medium
Target Milestone: ---
Assignee: Bernhard Rosenkraenzer
QA Contact: Brock Organ
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-03-27 20:11 UTC by jmbastia
Modified: 2007-04-18 16:41 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-03-27 21:57:13 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description jmbastia 2002-03-27 20:11:35 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020310

Description of problem:
The '{' character belongs on its own line in /etc/xinetd.d/ktalk and kotalk. 
xinetd leaves messages in /var/log/messages complaining that the '{' character
is missing.

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


How reproducible:
Always

Steps to Reproduce:
1. Start xinetd service
2. Examine /var/log/messages for notes about ktalk and kotalk

	

Actual Results:  The following two messages appeared in /var/log/messages
xinetd[17744]: Service talk: missing '{' [line=5]
xinetd[17744]: Service ntalk: missing '{' [line=5]

Expected Results:  No error messages should be in /var/log/messages related to
the pseudo-missing '{' character.

Additional info:

The /etc/xinetd.d/ktalk and kotalk files actually belong to the ktalk package,
but that package did appear in Bugzilla, so I chose xinetd instead.

Comment 1 Trond Eivind Glomsrxd 2002-03-27 21:57:08 UTC
Not an xinetd problem, refiling against kdenetwork.

Comment 2 Bernhard Rosenkraenzer 2002-03-27 22:05:05 UTC
Fixed in 3.0.0-1


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