Bug 22994 – Request DHCP restart after APM resume

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 22994 - Request DHCP restart after APM resume

Summary:	Request DHCP restart after APM resume

Status:	CLOSED RAWHIDE

Aliases:	None

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

Priority	low Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Bernhard Rosenkraenzer
QA Contact:	Aaron Brown
Docs Contact:

URL:
Whiteboard:
Keywords:	FutureFeature

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2000-12-29 16:00 EST by Daniel Wolstenholme
Modified:	2007-03-26 23:38 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Enhancement
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2000-12-29 16:00:40 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 Daniel Wolstenholme 2000-12-29 16:00:38 EST

Enhancement Request:
I use a laptop with RH6.2, with APM and a Cardbus ethernet card using DHCP via pump.  Frequently, I move the laptop from one location at work to another, or home, and in between suspend the laptop using apm -s.  Of course, when I resume, I'm plugged into a different ethernet connection which can even be on a different subnet.  You should add functionality to your /etc/sysconfig/apm-scripts/apmscript script so that, if the machine is using DHCP, it shuts down the ethernet connection, and upon resuming, restarts the connection so it can get a new IP address automatically.

I can do this myself of course, but it seems like a good enhancement to make default behavior for all laptop users.

Comment 1 Bernhard Rosenkraenzer 2001-01-08 12:13:37 EST

Fixed.

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