× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. December 2009

RE: inetd.conf newbie question

On Fri, 11 Dec 2009, Dennis Lovelady wrote:

But it appears that any time I make a change to the inetd.conf file I
have
to bounce the *INETD server to affect the change.

I believe you can "kill -1" the inetd process (which is not as scary as it
sounds), and that should effect a re-read of the .conf file. (This is from
memory though, and from Red Hat, and it's been a long time since I needed to
deal with this, so please verify.)

"kill -HUP <PID of inetd>" is the way I usually do it on linux. This causes inetd to reread inetd.conf without terminating any connections.

James Rich

if you want to understand why that is, there are many good books on
the design of operating systems. please pass them along to redmond
when you're done reading them :)
- Paul Davis on ardour-dev

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.