From owner-freebsd-bugs Thu Jun 10 11: 0: 8 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 9C43414CC3 for ; Thu, 10 Jun 1999 11:00:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id LAA69193; Thu, 10 Jun 1999 11:00:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Thu, 10 Jun 1999 11:00:02 -0700 (PDT) Message-Id: <199906101800.LAA69193@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Sheldon Hearn Subject: Re: bin/11987: vacation(1) documentation and error logging both suck Reply-To: Sheldon Hearn Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/11987; it has been noted by GNATS. From: Sheldon Hearn To: "Ronald F. Guilmette" Cc: freebsd-gnats-submit@freebsd.org Subject: Re: bin/11987: vacation(1) documentation and error logging both suck Date: Thu, 10 Jun 1999 19:58:15 +0200 On Thu, 10 Jun 1999 10:23:20 MST, "Ronald F. Guilmette" wrote: > 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.) vacation(1): Fatal errors, such as calling vacation with incorrect arguments, or with non-existent logins, are logged in the system log file, using syslog(3). syslog(3): LOG_USER Messages generated by random user processes. This is the default facility identifier if none is specified. > Right. But if the sysadmin is away on a three week vacation in the > Bahamas, and if the poor end user just has to figure out the problem > for himself/herself This is not a problem specific to vacation(1). I really do think this is a simple case of reading too fast. I know it's not easy to admit, and I only feel qualified to say so because I myself am so good at it. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message