| severity 309099 wishlist
| quit
|
| On Sat, May 14, 2005 at 06:44:16PM +0300, Jari Aalto wrote:
| > If drop bear is not enabled in /etc/default/dropbear, the following
| > command gives no indication of the situation:
| >
| > /etc/init.d/dropbear start
| >
| > .. and the user assumes that dropbear was started when it was not.
| >
| > SUGGESTION
| >
| > Please display a message that dropbear is disabled (like openSSH gives),
| > something like this in case user tries "reload", "strart" etc.
| >
| > Start ignored. Dropbear is not enabled in /etc/default/dropbear,
|
| Hi Jari, I'm not sure that's necessary. Normally sysv init scripts
| print along a line 'Starting foo daemon... done' when starting a
| service. If it doesn't print anything, doesn't this already tell that
| starting the service didn't work out?
Hi,
How will silence indicate an error? User needs to be notified in case
of errors like this. Just like the "Starting..." message is followed by:
a) "..Done" Success
But it should also be followed by (consistency):
b) "..Failed <folled by reason>"
This is the only sensible way how user interfaces should work.
| Silently exiting with zero is also what Debian policy suggests if a
| daemon program is not executable.
The exit code is completely different matter. The question here was
about user interface and it's visible messages.
The /etc/init.d/* files are user callable scripts and they should
give proper messages, especially on error cases.
Please add error checking and error indication message.
Jari
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
