81733 – when zapping a service, "Forcibly..." is better than "Manually..."

Bug 81733 - when zapping a service, "Forcibly..." is better than "Manually..."

Summary: when zapping a service, "Forcibly..." is better than "Manually..."

Status:	RESOLVED WONTFIX

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] baselayout (show other bugs)
Hardware:	All Linux

Importance:	High trivial (vote)
Assignee:	Gentoo's Team for Core System packages

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2005-02-12 06:15 UTC by Benno Schulenberg
Modified:	2005-02-14 18:54 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

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

Description Benno Schulenberg 2005-02-12 06:15:01 UTC

When zapping a service, the message says "Manually resetting <service> to 
stopped state."  But a script has no hands.  :)  The term "Forcibly" seems 
more appropriate.


Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Comment 1 Stian Skjelstad 2005-02-13 21:32:38 UTC

"Forcibly" might indicate that the script will kill/signal processes, while all it does is to nullify the pid-file.

Comment 2 SpanKY gentoo-dev

2005-02-14 18:54:33 UTC

manually is fine ... technically the user is manually running zap to force the service
to the stop state rather than running stop and letting the script do it