Bug 40303 - linuxconf-web does not start
Summary: linuxconf-web does not start
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: linuxconf
Version: 7.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-05-11 20:51 UTC by Need Real Name
Modified: 2007-04-18 16:33 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 18:47:59 UTC
Embargoed:


Attachments (Terms of Use)

Description Need Real Name 2001-05-11 20:51:01 UTC
Description of problem:
The linuxconf-web access does not work under xinetd because of an error
in the distribution package.

How reproducible:
Always

Steps to Reproduce:
1. rpm -i linuxconf*rpm 
2. /sbin/linuxconf (and enable linuxconf network access)
3. pico /etc/xinetd.d/linuxconf-web (and set disabled=no)
4. /sbin/service xinetd reload
5. (try to connect to http://localhost:98)

Actual Results:  No response from localhost

Actual Workaround:

The linuxconf-web is not defined in the file /etc/services. You must tell 
xinetd that it is an unlisted service. Look in:

pico /etc/xinetd.d/linuxconf-web 

Add the following type, port and protocol lines:

# default: off
# description: The Linuxconf system can also be accessed via a web \
#              browser.  Enabling this service will allow connections to \
#              Linuxconf running in web UI mode.
service linuxconf
{
        type            = UNLISTED
	socket_type	= stream
        protocol        = tcp
	wait		= yes
	user		= root
	server		= /sbin/linuxconf
	server_args	= --http
	disable		= no
        port            = 8000
}

An then reload:

sbin/service xinetd reload

And try it (port 8000 by default)

lynx http://localhost:8000

Voila!

Comment 1 Brent Fox 2002-06-05 16:17:17 UTC
Closing because we don't ship linuxconf anymore

Comment 2 Red Hat Bugzilla 2006-02-21 18:47:59 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


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