---
From: Paul Tutcher <pault_at_mailhub.wpl.com>
You might want to check and see if innd is throttled already... Do a
"ctlinnd pause because" and it will tell you if innd is throttled
already... You also might have a problem with your active file... If
your numbering is incorrect in the active file innd with throttle
itself... You'll have to go through the process of renumbering your
active file...
I have a script that I wrote to renumber our active file after our inn
server crashed... If you need it just let me know...
Paul Tutcher
Wisconsin Power & Light
pault_at_mailhub.wpl.com
---
From: "Anil Khullar, Computer Center" <Anil.Khullar_at_mailhub.gc.cuny.edu>
If you have compiled with shared library, then you'll have to relink
the software.
---
From: "Craig I. Hagan" <hagan_at_cih.com>
dude, lets play the email tag game.
* what happens when you run innd -d ... ?
-- craig
___ ____ __ Craig I. Hagan, Pencom System Administration
| _ \/ __/| \ Pencom Office: hagan_at_psa.pencom.com
| _/\__ \| \ \ At home: hagan_at_cih.com
|_|__/___/|_|__\ "True hackers don't die, their ttl expires"
________________________________________________________
---
From: Sheila Hollenbaugh <shollen_at_valhalla.cs.wright.edu>
innd normally has pretty extensive logs, have you checked them?
We upgraded to 3.2C and are not having any problems. Our logs are
in /var/log/news.
---
From: Sheila Hollenbaugh <shollen_at_valhalla.cs.wright.edu>
Oops, just reread your message. I see you have looked in the logs.
Perhaps you can turn up the logging to debug level in
/etc/syslog.conf?
---
From: Andrew Brennan <brennan_at_crashprone.hahnemann.edu>
It's been a while since we upgraded from v2.0 to v3.2, but I believe it
wasn't much more than a recompile. Any chance the protections or maybe
some directories have been moved during the upgrade? Or, can you start
INN with debug flags to see what the problem might be??
andrew. (brennan_at_crashprone.hahnemann.edu)
---
From: Eric Bennett <bennett_at_hpel.cees.edu>
I once had a similar problem with lpd. Look for errors in the config
file - create a trivial file and see if it still dies. If that approach
doesn't pan out try just copying inetd from the older distribution / or
from backup. I doubt the interface has changed so greatly that it won't
work.
Eric B.
---
From: "Anthony D'Atri" <aad_at_nwnet.net>
Is it possible that you're not syslogging properly? You should have
something like:
news.crit /var/log/news/news.crit
news.err /var/log/news/news.err
news.notice /var/log/news/news.notice
This could be something like the history files being owned by root
instead of news.
---
From: anthony baxter <anthony.baxter_at_aaii.oz.au>
I had this happen once when inndstart lost it's setuid-root-ness. It
would run, then almost immediatly die quietly. Everything in the inn
installation area should be owned by 'news', _except_ inndstart.
---
From: Hellebo Knut <Knut.Hellebo_at_nho.hydro.com>
Regards,
You must recompile. There are a few changes from 3.0 to 3.2C that cannot be
handled properly by some packages.
--
******************************************************************
* Knut Helleboe | DAMN GOOD COFFEE !! *
* Norsk Hydro a.s | (and hot too) *
* Phone: +47 55 996870, Fax: +47 55 996342 | *
* Pager: +47 96 500718 | *
* E-mail: Knut.Hellebo_at_nho.hydro.com | Dale Cooper, FBI *
******************************************************************
---
From: "Mr. Dustin Fu" <xxfdh_at_omega.uta.edu>
Have you tried re-compiling innd?
Dustin Fu
Software Systems Specialist
Academic Computing Services
University of Texas at Arlington
xxfdh_at_omega.uta.edu
817-272-2208
---
From: Dave Sill <de5_at_sws5.ctd.ornl.gov>
Check syslog. innd never exits without a message.
-Dave
Received on Thu May 02 1996 - 19:09:56 NZST
This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:46 NZDT