Bug 24843 – Nanny tries to execute "none"

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 24843 - Nanny tries to execute "none"

Summary:	Nanny tries to execute "none"

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat High Availability Server
Classification:	Retired
Component:	piranha (Show other bugs)
Sub Component:
Version:	1.0
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Phil Copeland
QA Contact:	Phil Copeland
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2001-01-24 08:17 EST by Tinus Strauss
Modified:	2007-04-18 12:30 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2001-01-24 08:17:10 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 Red Hat Bugzilla 2001-01-24 08:17:07 EST

Hi,

I configured nanny to use none as the loadCommand, assuming that it 
will not try to determine the load of the real servers. However, nanny tries 
to execute the command "none" which it cannot find.

The following change to nanny from piranha-0.4.17-7 fixed it for me:

--- nanny.c.orig        Wed Jan 24 10:53:17 2001
+++ nanny.c.new Wed Jan 24 14:08:53 2001
@@ -781,7 +781,7 @@
     *argp++ = loadCommand;
     *argp++ = inet_ntoa(*remoteAddr);

-    if (strcmp(loadCommand, (char *) "none"))
+    if (strcmp(loadCommand, (char *) "none") == 0)
        return -1.0; /* nothing to see here, go home silently */

     if (strcmp(loadCommand, (char *) "rup"))
[

Cheers
Tinus

Comment 1 Red Hat Bugzilla 2001-05-07 16:14:55 EDT

Patch has been applied to nanny and will appear in a future update.

Thanks!

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