🚀 go-pugleaf

In article <1cnmo8INNsaa@clem.handheld.com> jmd@cube.handheld.com writes:

>
>I just finished porting INN 1.2 to the NeXT (3.0) and would like to compare  
>'war stories' with anyone else who has also converted.
>

I did too.  I fiddled around for days with the config.data file, until
I figured out that all I had to do by way of major change was to comment out
the entry in /etc/inetd.conf that I had previously made for nntp when
running the "Reference Implementation".  This entry (even when modified to 
call innd instead of nntpd) kept innd from binding to port 119.  
Apparently, innd doesn't like the inetd daemon.  

Otherwise, INN compiles near perfectly, with DEFS Dregister and DNeXT  
and a few other changes (like adding mkfifo;and using 
LOG_LOCAL7, instead of LOG_NEWS, to use the existing syslogd). 

I find the documentation for INN very thin when it comes to running
the installed software.  All in all though, it is much easier to keep track
of INN than it is to run C-News and the Reference Implementation for nntp.
It also seems faster.
--- 
eric@erix.coudert.com or eric@erix.demon.co.uk