Tom Emerson <[EMAIL PROTECTED]> wrote: > Alan, to you it is insanely obvious, to a first timer reading hundreds of > lines of "potentially" useful output, the critical bits are "buried in the > noise"
It's only a few hundred lines of text, most of which are simple to understand. It should take less time to read that text than to send a message to the list, and wait for a response. > would it have really taken that long for you to say: That is exactly, 100%, my point. Would it have taken HIM that long to READ the debug log? No. So he was too lazy to read the messages, and I was too lazy to cut & paste the relevant portions for him to digest. But you're upset at my behaviour, and not at his. Nice. > Things to check: [ok alan, this is where it gets subjective, and I'm sure for > you overly repetitive -- NOW you can refer someone to a FAQ (if it's in > there) and specifically WHERE in the FAQ to start looking] The debug information contains sufficient information for someone to solve most problems, IF and ONLY IF they read it. Adding more documentation, FAQ entries, and answering questions on email lists will NOT help the people who too lazy to do anything themselves. What they want is for someone else to do the "hard thinking" for them. The way to correct that attitude is NOT through more documentation: they don't care, and won't read it. The way to correct it is to tell them to do some work themselves. > Not the exact answer, but some directions for someone new to this to start > looking... Type up a step-by-step "howto" guide for debugging problems like this, and I'll include it in the server documentation. But don't expect it to answer many of these questions... the people who need it the most won't bother to read it. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
