[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [leafnode-list] Need Leafnode 2.0?
2 cents may not be applicable but:
When messing with the xinetd daemon and leafnode in the past, I have found
that for news to work, I would have to actually stop then start the service
or kill the daemon and then start it for some versions of xinetd on RedHat
machines. The special kills or service restarts would not do as documented.
If you have xinetd -d, it is very easy to tell if/when xinetd restarts since
log messages show what services are started/disabled. This was how I found
that it wasn't obeying the documented behavior for SIGHUP.
Granted, this is not supposed to be the normal case, but, I have seen it
happen.
---
Kevin R. Bulgrien, Product Engineer
Mailto:kevin.bulgrien@xxxxxxxxxxxxxxxxxx
Vertex RSI, A TriPoint Global Company http://www.tripointglobal.com/
Controls & Structures Division
1915 Harrison Road Tel: 903-295-1480 x288
Longview, TX 75604-5438 Fax: 903-295-1479
> -----Original Message-----
> From: Doug Laidlaw [mailto:laidlaws@xxxxxxxxxxxxxxx]
> Sent: Sunday, November 17, 2002 11:49 PM
> To: leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Subject: Re: [leafnode-list] Need Leafnode 2.0?
>
> I did that. I have xinetd version 2.3.4. according to the
> RPM suffix. I
> modified it as follows:
>
> #New nntp for leafnode 2.
> service nntp
> {
> flags = REUSE
> socket_type = stream
> wait = no
> user = news
> server = /opt/leafnode2/sbin/leafnode
> log_on_failure += USERID
> }
> #End of nntp.
>
>
> To restart it I have been using "service xinetd restart."
> The man page
> metions both SIGUSR2 (causes a hard reconfiguration) and
> SIGHUP (causes a
> state dump.) After running "service xinetd restart" I ran
> fetchnews from
> the /opt/leafnode/sbin/directory.
--
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list for leafnode
To unsubscribe, send mail with "unsubscribe" in the subject to the list