Bug 8348 – linuxconf fails to update changes runtime.

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 8348 - linuxconf fails to update changes runtime.

Summary:	linuxconf fails to update changes runtime.

Status:	CLOSED WONTFIX

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	linuxconf (Show other bugs)
Sub Component:
Version:	6.1
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Nalin Dahyabhai
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2000-01-10 15:41 EST by tommy.svensson
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2006-02-21 13:47:35 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description tommy.svensson 2000-01-10 15:41:47 EST

Linuxconf fails to update changes runtime. After making changes I
have to reboot to get the changes. It is starting to feel like
windows ;-).

I have to admit that I only tried changeing the hostname. Maybe
the hostname can't be reset runtime ?

Comment 1 Nalin Dahyabhai 2000-01-17 12:22:59 EST

The system hostname is one of the few things that is only set at boot-time.
Most configuration changes made with Linuxconf take effect immediately.  If you
need to make this take effect immediately, run these commands at a bash prompt:
. /etc/sysconfig/network
hostname $HOSTNAME
and then use this command to verify that your hostname has been changed:
hostname

Comment 2 Brent Fox 2002-06-05 12:20:11 EDT

Closing because we don't ship linuxconf anymore

Comment 3 Red Hat Bugzilla 2006-02-21 13:47:35 EST

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.