Bug 9942

Summary: Samba / LinuxConf / inetd - Dependency Problem
Product: [Retired] Red Hat Linux Reporter: Don Head <haze>
Component: inetdAssignee: Trond Eivind Glomsrxd <teg>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-01-19 21:15: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 Don Head 2000-03-03 20:31:55 UTC
1)  Samba adds the "swat" service to /etc/inetd.conf without checking if
the inetd package (netkit-base) is installed.  This gives the user the
false impression that "swat" should be working.

Samba should have netkit-base as a dependency.  Anyone not wanting
netkit-base, and therefore the swat service, can use --nodeps to override.


2)  LinuxConf adds the "linuxconf" service to /etc/inetd.conf without
checking if the inetd package (netkit-base) is installed.  This gives the
user the false impression that "linuxconf" should be working.

LinuxConf should have netkit-base as a dependency.  Anyone not wanting
netkit-base, and therefore the "linuxconf" service, can use --nodeps to
override.


3)  The inetd package (netkit-base) installs without merging changes with
the existing /etc/inetd.conf.  If it does not find one, it creates it with
the default services.  If it finds one, it creates an inetd.rpmsave.  If
for some reason LinuxConf or Samba are installed before netkit-base, the
only two services that will be active are "linuxconf" and "swat", because
netkit-base will see an existing inetd.conf and not overwrite it.  This
means that telnet and FTP are not working.

The inetd package (netkit-base) should do some inet.conf checking upon
installation, rather than the "all or nothing" approach.


Note)  This was noticed in Red Hat 6.1.

I do not have permission to use the person's name who found this.  If she
wants credit, I'm more than happy to give it to her.  She did find it, I
just verified it and reported it.

Don Head
Linux Mentor
Wave Technologies, Inc.
dhead

Comment 1 Trond Eivind Glomsrxd 2001-01-19 21:17:30 UTC
Red Hat Linux 7 uses xinetd, where each service has its own configuration file.
This solves the above problem.