Bug 52267
Summary: | Linuxconf web access is totally hosed | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | John Morris <jmorris> |
Component: | linuxconf | Assignee: | Nalin Dahyabhai <nalin> |
Status: | CLOSED WONTFIX | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.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: | 2006-02-21 18:48:06 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
John Morris
2001-08-22 07:30:31 UTC
Now in 7.2 it's even worse. Now it does seem to repond to the --port 98 switch, but it doesn't stay running. It won't run from xinitd and still only seems to service one connection then exit. I know linuxconf is supposed to be scheduled for removal, but until there is a replacement that can do what it does I need to make it work! Correction. Linuxconf will work on 7.2 But a line in /etc/hosts.allow with: ALL: localhost would not allow lynx "http://localhost:98" to work. Adding in a line with the hostname in question and switching localhost for the hostname in the lynx comnmand still didn't bring joy. However, adding: linuxconf: ALL works. So is this a problem with tcpwrappers, xinitd or linuxconf.... too late to worry about such matters, it works. Linuxconf does its own access controls so I hope I can get away with that ALL for now. Closing because we don't ship linuxconf anymore Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |