Hi,
Something that really started bothering me when working on the
ha-list is the amount of time and bandwidth used just to figure
out what the heck is going on, where is the problem, and finally
logs and configuration. Not to talk about threads spanning pages.
I guess that you all know what I'm talking about.
Our documentation is not in a good shape, but the problem
reporting procedure is really good. The problem stems from the
fact that just a tiny procent of people actually read
documentation. Incidentally, one of my favourite fortunes:
guru, n:
A computer owner who can read the manual.
To the point: Most of the problem/bug reporting begs to be
automated. For example, like this:
# Problem-Report setup report1
... do whatever makes the problem show ...
# Problem-Report pack report1
# mutt -s myproblem -a report1.tar.bz2 ha-list < mydesc.txt
The second part Alan suggested would be enquiring user about
various aspects of the issue they encountered, such as
description. I can recall now the debian's reportbug.
Any suggestions? Anybody already wrote some code which could help?
Cheers,
--
Dejan
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
