Bug 26560 – ntpd "usage" message redesign

Bug 26560 - ntpd "usage" message redesign

Summary:	ntpd "usage" message redesign

Status:	CLOSED RAWHIDE

Aliases:	None

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

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Preston Brown
QA Contact:	Brian Brock
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2001-02-07 17:42 EST by Christian Rose
Modified:	2007-04-18 12:31 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-02-11 23:18:20 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 Christian Rose 2001-02-07 17:42:52 EST

#: /etc/rc.d/init.d/ntpd:72
msgid "Usage: ntpd {start|stop|restart|condrestart|status}"

If "ntpd" is replaced with $0 here, this message can be reused in
translations (other usage messages use $0), so that translators won't have
to translate each similar message individually. To make it more clear, what
I suggest is:

"Usage: $0 {start|stop|restart|condrestart|status}"

Comment 1 Preston Brown 2001-02-09 00:52:50 EST


*** This bug has been marked as a duplicate of 26525 ***

Comment 2 Christian Rose 2001-02-11 23:18:16 EST

I don't think this is a duplicate - bug 26525 talks about using $prog in the
"starting/stopping", this is about using $0 in the usage message. 
If you use $prog or $0 in both, this would be inconsistent with many other
packages, and defeat the very purpose of similar messages to make it easier for
translators by message re-use...

Comment 3 Preston Brown 2001-02-12 13:29:17 EST

both issues were solved at the same time anyway.

Comment 4 Christian Rose 2001-02-12 17:46:40 EST

Ok. Thanks!

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