Bug 9365

Summary: systat/netstat entries in inetd.conf
Product: [Retired] Red Hat Linux Reporter: Randy Russell <rrussell>
Component: inetdAssignee: Jeff Johnson <jbj>
Status: CLOSED WONTFIX QA Contact:
Severity: low Docs Contact:
Priority: medium    
Version: 6.2   
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: 2000-03-27 12:00:01 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Randy Russell 2000-02-11 20:58:14 UTC
(Note: this misconfiguration is also present in 6.1 and probably numerous
earlier versions, but is of pretty trivial importance.  We might want to
make the fix for 6.2, however.)

The entries for the systat and netstat services in /etc/inetd.conf are
commented by default, which is appropriate.  Should someone choose to
uncomment those services, then HUP or otherwise restart inetd, they would
find that they could successfully connect to those services, but that the
services themselves would not execute properly.  All that would happen is
the connection followed by immediate disconnection.

The reason they seem to fail is that /etc/inetd.conf specifies that the
associated commands are to be run by the user "guest".  Because that user
does not exist, the command is not executed.  Substituting some other
unprivileged user, such as "nobody", will allow those services to perform
as expected.

Given that the services are commented out, that people seldom use these
"services", and often sys admins choose not to run ANY inetd services, this
is a very low priority bug.  Nevertheless, it is one we might wish to
change for 6.2 so that things work correctly -- even services that we might
have little enthusiasm for people running.

Comment 1 Pekka Savola 2000-07-16 16:57:00 UTC
Not an issue anymore.