Bug 31464 – %m in printf is not handled.

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 31464 - %m in printf is not handled.

Summary:	%m in printf is not handled.

Status:	CLOSED WONTFIX

Aliases:	None

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

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Erik Troan
QA Contact:	Brock Organ
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2001-03-11 18:27 EST by hjl
Modified:	2007-04-18 12:32 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:	2001-09-17 16:05:56 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)
A patch for %m (1.10 KB, patch) 2001-03-11 18:28 EST, hjl	no flags	Details \| Diff
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description hjl 2001-03-11 18:27:56 EST

%m in printf is not handled. Loader uses it.
I will post a patch.

Comment 1 hjl 2001-03-11 18:28:31 EST

Created attachment 12384 [details]
A patch for %m

Comment 2 Glen Foster 2001-03-12 14:40:59 EST

This defect considered MUST-FIX (show-stopper) for Florence Gold

Comment 3 Erik Troan 2001-03-12 16:36:21 EST

This is hardly a show stopper. It causes %m to appear in some logs instead of
"localhost".

Comment 4 Glen Foster 2001-03-12 17:38:06 EST

Take it up with Mike Fulbright (he made the call) and leave qa-whiteboard alone,
please.

Comment 5 Michael Fulbright 2001-03-12 17:39:47 EST

ewt it has a patch - just need you to say if its ok or not.

Comment 6 Erik Troan 2001-03-12 19:14:24 EST

I don't like the patch -- I'd rather remove the %m's whereever possible to save
code space. It doesn't need to be done for this release though, as it doesn't
actually cause any problems.

I'll let you and Glen sort it out.

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