Bug 49404 - linuxconf web access fails on changes update
Summary: linuxconf web access fails on changes update
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: linuxconf
Version: 7.1
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2001-07-19 05:10 UTC by Nikolai Turchanikov
Modified: 2007-04-18 16:34 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2006-02-21 18:48:03 UTC

Attachments (Terms of Use)

Description Nikolai Turchanikov 2001-07-19 05:10:52 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.2-2 i586; en-US; m18)
Gecko/20010131 Netscape6/6.01

Description of problem:
When linuxconf accessed via web browser (xinetd 2.3.0-1.71 installed)
the initial connection succeeds, but attempt to update a change
in configuration field fails.

the browser indicates broken connection (lynx message:
"Unexpected network error; connection aborted")

At the same time, xinitd syslog entry pops the message:
"warning: can't get client address: Transport endpoint is not

If linuxconf started with --http option, then everything works
fine with connection to the port 8000, thus indicating the
linuxconf-xinetd communication problem

How reproducible:

Steps to Reproduce:
1.Ugrade (install) to xinetd 2.3.0-1.71
2.Make appropriate linuxconf and xinetd configuration to enable web access
to linuxconf (as per Red Hat documentation)
3.Start browser with http://localhost:98
4.Change contents of any field and press button "Accept"

Actual Results:  failed to accept configuration changes

Expected Results:  expected to accept and update configuration changes

Additional info:

Lynx error message:
"Unexpected network error; connection aborted"

Xinetd warning message:
"warning: can't get client address: Transport endpoint is not

The version of xinetd that comes with Red Hat 7.1 CDs does not
work with linuxconf at all, therefore the upgrade to the recently
posted updated xinetd version (2.3.0-1.71) is required

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

Comment 2 Red Hat Bugzilla 2006-02-21 18:48:03 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.