× 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.



SIGHUP isn't signal 1 on OS/400. It's signal 15. (I don't know why, I didn't design it!)

And, of course, there's no kill command (though, I wrote my own.)

However, you'll be happy to know that your suggestion DOES work... I just tried it on my box, using my own homegrown KILL command

KILL JOB(538243/QTCP/QTOGINTD) SIGNAL(*HANGUP)

and it worked! it picked up the new config changes. You gotta love when IBM ports stuff from Unix and keeps Unix behavior. (And then doesn't document it ANYWHERE and expects you to figure it out.)


Dennis Lovelady wrote:
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.)

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-2024 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.