Bug 5695

Summary: improper upgrade
Product: [Retired] Red Hat Linux Reporter: Wil Harris <wil>
Component: linuxconfAssignee: Michael K. Johnson <johnsonm>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 1999-11-24 16:09:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Wil Harris 1999-10-07 19:42:07 UTC 
During the upgrade of Linuxconf it continuely adds to the
/etc/inetd.conf file rather than checking to see if it
already has an entry. This causes the /etc/inetd.conf file
to end up looking like:

linuxconf stream tcp wait root /bin/linuxconf linuxconf
--http
#swat      stream  tcp     nowait.400      root
/usr/sbin/swat swat
#swat      stream  tcp     nowait.400      root
/usr/sbin/swat swat

linuxconf stream tcp wait root /bin/linuxconf linuxconf
--http

linuxconf stream tcp wait root /bin/linuxconf linuxconf
--http
#swat      stream  tcp     nowait.400      root
/usr/sbin/swat swat

linuxconf stream tcp wait root /bin/linuxconf linuxconf
--http

linuxconf stream tcp wait root /bin/linuxconf linuxconf
--http

linuxconf stream tcp wait root /bin/linuxconf linuxconf
--http

linuxconf stream tcp wait root /bin/linuxconf linuxconf
--http
#swat      stream  tcp     nowait.400      root
/usr/sbin/swat swat
Comment 1 Michael K. Johnson 1999-11-24 16:09:59 UTC 
It used to do this, but has since been fixed.  However, we do not
attempt to remove the duplicate entries from inetd.conf, as they
are harmless and our attempts could easily do more harm than good.