From owner-freebsd-bugs Thu Jun 10 13:31:58 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from smtp13.bellglobal.com (smtp13.bellglobal.com [204.101.251.52]) by hub.freebsd.org (Postfix) with ESMTP id C824514D96; Thu, 10 Jun 1999 13:31:47 -0700 (PDT) (envelope-from vanderh@ecf.toronto.edu) Received: from localhost.nowhere (ppp18372.on.bellglobal.com [206.172.130.52]) by smtp13.bellglobal.com (8.8.5/8.8.5) with ESMTP id QAA10594; Thu, 10 Jun 1999 16:32:57 -0400 (EDT) Received: (from tim@localhost) by localhost.nowhere (8.9.3/8.9.1) id QAA01343; Thu, 10 Jun 1999 16:32:02 -0400 (EDT) (envelope-from tim) Date: Thu, 10 Jun 1999 16:32:01 -0400 From: Tim Vanderhoek To: "Ronald F. Guilmette" , sheldonh@FreeBSD.ORG Cc: freebsd-bugs@FreeBSD.ORG Subject: Re: bin/11987: vacation(1) documentation and error logging both suck Message-ID: <19990610163201.A1147@mad> References: <199906101730.KAA65998@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199906101730.KAA65998@freefall.freebsd.org>; from Ronald F. Guilmette on Thu, Jun 10, 1999 at 10:30:01AM -0700 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Jun 10, 1999 at 10:30:01AM -0700, Ronald F. Guilmette wrote: > > >2) The manpage _does_ mention that erorr messages are logged through the > > syslog(3) interface. The manpage has always mentioned this. > > Hummm... You're right. > > I still don't see where the specific syslog facility used by the program > is mentioned. That is an _important_ bit of data. (The facility used > for logging is the "user" facility.) Actually, when we had our first little email exchange, I went glanced through the source and I seem to recall that it doesn't even use the "user" facility consistently. Anyways, I'll reopen the PR and assign it to myself in a moment. I can't promise you that I'll get to it anytime soon... FWIW, Ronald, I think it was the wording, not the content, of your bugreport that caused both me, sheldonh, and probably a lot of other readers, to have more-or-less the same reaction. Phrases "XXX should be done" are the type that usually need to have their words backed-up with code. More generally, we really do need a different PR state for PRs that have a fairly obvious solution that just needs to get coded. This would give us something better to point at next time some random person with unknown qualifications asks on the lists "Hi! What can I do to help FreeBSD". TBH, I have yet to see a list of this type actually succeed, but... Sheldon, since your the PR-guy of the moment... Suggestions? :-) [Maybe a webpage? Maybe assign some problems to "userland _improvements_"? I think what's been done with the ports and docs prs has worked reasonably well.] -- This is my .signature which gets appended to the end of my messages. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message