Date: Sun, 12 Oct 1997 00:49:29 -0700 From: "Shawn Ramsey" <shawn@cpl.net> To: "T. William Wells" <bill@twwells.com>, <freebsd-questions@FreeBSD.ORG> Subject: Re: inn port Message-ID: <01bcd6e3$5ed57920$c4ac43cf@shawn.cpl.net>
next in thread | raw e-mail | index | archive | help
>Does your /etc/syslog.conf point news to those files? Keep in mind >that wherever news is logged, the files must exist at the time >that syslog is started or given a SIGHUP, otherwise it won't write >to those files. Umm.. no. :) Opps.. The *.news stuff in syslog was commented out. Here is what the log files are saying now : (news.crit) Oct 12 00:43:47 luke innd: /usr/local/news/lib/history cant dbminit SERVER No su ch file or directory (news.notice) Oct 12 00:43:47 luke innd: SERVER descriptors 360 Oct 12 00:43:47 luke innd: SERVER outgoing 347 Oct 12 00:43:47 luke innd: /usr/local/news/lib/history cant dbminit SERVER No su ch file or directory (news.err) Oct 12 00:43:47 luke innd: /usr/local/news/lib/history cant dbminit SERVER No su ch file or directory If I run ./makehistory, it generates a blank history file in /usr/local/news/lib. Is this the proper way to do it?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01bcd6e3$5ed57920$c4ac43cf>