[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[leafnode-list] Re: Installation/configuration problems, help please
On Mon, Oct 19, 2009 at 02:52:43PM +0200, Matthias Andree wrote:
> Am 19.10.2009, 12:01 Uhr, schrieb Chris G <cl@xxxxxxxx>:
> > My other problem was that although the NNTP entry had been added to
> > /etc/inetd.conf inetd hadn't been restarted and thus hadn't re-read
> > /etc/inetd.conf. I thought that a 'kill -1' of inetd should make it
> > re-read /etc/inetd.conf but, looking at the manual page, it seems I
> > was wrong - I should have been sending it a SIGHUP. I actually fixed
> > the problem by rebooting after which (as I reported earlier) tin could
> > see the NNTP server.
> kill -1 should send a SIGHUP on Linux (and in fact several other systems,
> such as FreeBSD or Solaris 8 and 10).
Sorry, I'm being really silly now arent I! I'd not looked to see what
signal 1 corresponded to and, for some reason, I thought SIGHUP was a
non-standard signal used to do this for inetd. My background is on
Solaris systems which I started using way back in the late 1980s and I
tend to use the numbers for 'kill' as a consequence.
> > So maybe I need to raise an Ubuntu bug asking that the "8 minutes past
> > each hour" run of fetchnews is documented and also that the
> > requirement to send a SIGHUP to inetd is added.
> The latter should be done in the postinstall script, or by means of an
> apt/dpkg trigger it seems.
So it seems that something else must have been preventing inetd from
running leafnode. I *definitely* did several 'kill -1 <pid>' to inetd
after installing leafnode and neither tin nor 'telnet localhost 119'
got a response. After I rebooted it worked OK.
Oh well, I think the chances of finding the cause now are very slight.
I might well try uninstalling and then reinstalling leafnode to see if
I get the same problem again, that will be quite easy and all I need
to preserve before doing it is the leafnode config file.
leafnode-list mailing list