Original question:
>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
> : [/etc/syslog.conf extract snipped]
> :
>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?
Consensus is unanimously "let INN do it's thing." This is particularly
important since INN creates its daily reports from the logs, and other tools
expect the logs to be in a single place based on _PATH_MOST_LOGS, not a
variable place as would happen with syslog.dated.
Saul reminded me that:
And there should be only one cron entry for news to handle this,
news.daily. They "myriad" scripts are largely invisible.
I'm still puzzled as to why I get the above message when I run innd/inndstart
as root, while running innd/innd (as root) seems to work fine.
Thanks to:
Dave Tetreault <davet_at_uriacc.uri.edu>
Guy Helmer <ghelmer_at_alpha.dsu.edu>
Saul Tannenbaum <stannenb_at_emerald.tufts.edu>
--
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 - 20:21:28 NZDT