From: Bruce Allen <ballen@gr...> - 2004-05-03 21:25:04
> # In the FAQ section, there is an entry that says:
> # What do I do if I have problems, or need support?
> This appears to make the barrier for bug reports quite high IMHO:
> subscribing to a mailing list. I think bug reporting should be made as
> easy as possible. This means in prominent places and with no barriers. I
> understand however that providing an email address or a mailto: link may
> not be desirable due to spam.
It says (note final sentence):
First, search the support mailing list archives to see if your question
has been answered. Instructions are in the following paragraph. If you
don't find an answer there, then please send an email to the
smartmontools-support mailing list. This is a moderated forum: you are not
required to subscribe to the list in order to post your question.
I would like users to first search the mailing list archives before
writing. Otherwise we simply end up answering the same questions over and
> # > - The echo -n "smartd " should have the space not appended, but prepended.
> # > I think this is true not only for FreeBSD, but other OSs as well.
> # Could you please explain this further, and comment on this:
> # https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=107454
> Well, the BSD way for startup script output is:
> 1. The framework does echo -n "Starting local daemons:"
> 2. Each local daemon is started and does echo -n " foobard"
> 3. The framework does echo "."
> (Similar for shutdown)
> This leads to output along
> Starting local daemons: apache privoxy smokeping smartd.
> Currently it looks like this:
> Starting local daemons: apache privoxy smokepingsmartd .
OK. I think that this needs only to be fixed for FreeBSD, not for
Solaris, Linux, NetBSD, etc.
> As for https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=107454,
> If it is intended also for FreeBSD, it would be nice to retain the
> old behavior of just echo -n " smartd" if it is called from within
> the startup framework. The interactive case can be as verbose as you
> It might well be the BSD port maintainer decides to provide a complete
> implementation suited for BSD. I'm not involved in these matters; I just
> noticed the run-together smokepingsmartd and wanted to let you know.
Thank you. It should be easy to fix. Ed?
Get latest updates about Open Source Projects, Conferences and News.