Q.  My logs keep telling me there is no space for articles
A.  Edit innwatch.ctl to use "bdf" instead of "df".

Q. I am running inn on an HP machine. INN won't start up automatically.
I can start it manually.  There is no problem with news or INN once
it is started.

A.  Try adding a "sleep 10" to the bottom of /etc/rc.news, or in
/etc/rc, right after /etc/rc.news is invoked.  On some machines,
including HP, the shell started by "#!/bin/sh" when /etc/rc is executed
will exit before innd has disassociated itself from that shell.  This
causes innd to exit, sometimes without printing an error message.
(source: pjoslin@mbvlab.wpafb.af.mil (Paul Joslin ))

This problem goes away if you set HAVE_SETSID to "DO".  Something to do
with Posix Session Leader concepts.  Ick.  (source: Steve Howie 
<showie@uoguelph.ca>).  You can also do something like:

	echo /usr/lib/etc/rc.news | at now + 2 minutes

or else

	nohup su news -c /usr/local/etc/rc.news&

HP-UX 8.x and 9.x users might find a problem with getting innwatch to
start up.  People have found that having "at" start it seems to work
more reliably than other methods:

${DOINNWATCH} && {
	echo "${INNWATCH} &" | su ${NEWSUSER} -c 'at now + 2 min' > /dev/null
}

The '&' in the command line prevents innwatch from taking up an at-job 
slot.  SysV-style crons have a per-category and overall limit on the 
number of jobs executing simultaneously.

Q:  INN-1.4sec running on an HP9000 s700 with HP-UX 9.01 leaks memory
like crazy.  The innd process grows and grows, then stops with:

	"ME cant remalloc 8192 bytes Not enough space"

A:  The cause turns out to be a memory leak in the standard C library (both
/lib/libc.a and /lib/libc.sl).  Installed patch PHCO_5056 (or the latest
libc patch).

Some parts © 2009 Advameg, Inc.