On Tue, Feb 26, 2013 at 05:09:42PM +0100, Michael Haberler wrote:
>
> all messages should wind up in syslog anyway
I don't agree with this. We have an odd application that is pretty
much like other user applications, but is partly implemented in the
kernel for technical reasons. If not for this implementation
detail, I doubt we would be thinking about syslog at all. My web
browser and office applications don't log anything to syslog,
because the errors they give are for the user to consume, not the
sysadmin. Syslog is where errors for the sysadmin go.
Many (most?) of linuxcnc's errors are for the user ("Can't do G1
without Feed rate set"). These kinds of errors do NOT belong in
syslog. They need to be localized and then shown on the screen,
just like "Can't get to that website" in my browser and "12:72 is an
invalid time" in my spreadsheet.
Some other errors, like the realtime delay errors, MIGHT belong in
syslog in addition to being shown to the user. But I am not sure
what added value that gives us.
Who is our audience here? A perusal of the mailing list and forum
will show that people simply don't see error messages that don't pop
up on the screen.
For any change in error handling, to me, the primary goal to have in
mind is to solve the problem of "linuxcnc won't start and I can't
tell why". We currently have a popup in that case, but it's full of
incomprehensible garbage. Changing/improving the smell of the code
is a goal I care about WAY less than that, but if that's step 1, so
be it!
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
