upgrade 2.3.2 > 2.3.3 probs

[Jeffrey M. Vinocur]

On Thu, 26 Sep 2002, Scot Mc Pherson wrote:

> > [ please respond to inn-workers, not me personally; and you might try 
> > putting quoted text on top and new text below, and trimming the quoted 
> > text ]

Redirecting to inn-workers again...


> -rw-r--r--    1 news     news            0 Sep 25 21:45 errlog
> -rw-rw-r--    1 news     news        96615 Sep 25 21:49 expire.list
> -rw-rw-r--    1 news     news         1563 Sep 25 22:50 expire.log
> -rw-r--r--    1 news     news        13443 Sep 26 12:35 news
> -rw-r--r--    1 news     news            0 Sep 25 21:45 news.crit
> -rw-r--r--    1 news     news            0 Sep 25 21:45 news.err
> -rw-r--r--    1 news     news            0 Sep 25 21:45 news.notice
> -rw-rw----    1 news     news            0 Sep 25 21:49 unwanted.log

This is even if you run 2.3.2?  Then there's definitely something wrong 
with your syslog configuration (you might read that section of INSTALL 
carefully and see if you have any problems); you should always get copious 
logging of a functional INN.  I can imagine a few really crazy ways that 
might result in INN never starting enough to log anything, but if the 
2.3.2 isn't logging, it's definitely a logging problem.

-- 
Jeffrey M. Vinocur
jeff at litech.org