I'm running DU 3.0, DEC's cc. Having done a "make all", "make update", and
"make install", and having made an initial pass at /etc/syslog.conf, I started
innd via innd/inndstart. I got the following via syslog:
Jan 26 00:27:24 omega innd: ME cant fopen /var/log/news/news Permission denied
I have set /etc/syslog.conf to use the syslog.dated construct. I'm wondering
if that's confusing INN. It looks like this:
kern.debug /var/adm/syslog.dated/kern.log
user.debug /var/adm/syslog.dated/user.log
mail.debug /var/adm/syslog.dated/mail.log
daemon.debug /var/adm/syslog.dated/daemon.log
auth.debug /var/adm/syslog.dated/auth.log
syslog.debug /var/adm/syslog.dated/syslog.log
lpr.debug /var/adm/syslog.dated/lpr.log
## Send critical messages to everyone who is logged in and to the console.
news.crit *
news.crit /dev/console
## Log news messages to separate files.
## Note that each level includes all of the above it.
## =()<news.crit _at_<_PATH_MOST_LOGS>_at_/news.crit>()=
news.crit /var/adm/syslog.dated/news.crit
## =()<news.err _at_<_PATH_MOST_LOGS>_at_/news.err>()=
news.err /var/admsyslog.dated/news.err
## =()<news.notice _at_<_PATH_MOST_LOGS>_at_/news.notice>()=
news.notice /var/adm/syslog.dated/news.notice
msgbuf.err /var/adm/crash/msgbuf.savecore
kern.debug /var/adm/messages
kern.debug /dev/console
*.emerg *
Has anyone else tried to use syslog.dated with inn, or should I just let innd
(and the myriad cron-based scripts) manage it's logs and forget syslog.dated?
--
Del Merritt del_at_IntraNet.com
IntraNet, Inc., One Gateway Center #700, Newton, MA 02158
Voice: 617-527-7020; FAX: 617-527-6779 Just say no to Clipper.
Want to buy my house or car? email me for details!
You may not add me to a commercial mailing list or send me commercial
advertising without my consent.
Received on Fri Jan 26 1996 - 16:09:30 NZDT