Bug 68123 – /etc/init.d/halt does not power off with genericups driver from nut

Bug 68123 - /etc/init.d/halt does not power off with genericups driver from nut

Summary:	/etc/init.d/halt does not power off with genericups driver from nut

Status:	CLOSED RAWHIDE

Aliases:	None

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

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Bill Nottingham
QA Contact:	Brock Organ
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2002-07-06 14:32 EDT by Yuriy Osmerkin
Modified:	2014-03-16 22:28 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2002-07-06 14:32:40 EDT
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 Yuriy Osmerkin 2002-07-06 14:32:36 EDT

From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.0 (X11; Linux i686; U;) Gecko/20020408

Description of problem:
genericups driver from nut package called in /etc/init.d/halt without parameter
"-t". This prevent switch off power.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Configure nut with genericups driver.
2. Switch off UPS power.
3. Wait for "low power" and shutdown.
	

Actual Results:  Power is not switch off.

Expected Results:  Power is off.

Additional info:

Fix:
replace string in /etc/init.d/halt
... && $MODEL -k $DEVICE
with
... && $MODEL $OPTIONS -k $DEVICE

Comment 1 Florian La Roche 2002-07-09 16:43:07 EDT

I have fixed this in our internal cvs version, should be part of the
next release.

Thanks a lot,

Florian La Roche

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