For xinetd use USR2. It causes a hard reload which re-reads the configuration, and stops any servers which are no longer required.
On Redhat the easist way is # service xinetd reload On Fri, 5 Apr 2002, Morse, Richard E. wrote: - Actually, and perhaps this should be noted somewhere else?, you can do the - following: - - kill -USR1 <your-xinetd-pid-here> - - which should cause it to intelligently reload (ie, don't cut off any already - existing connections) - - HTH, - Ricky - - > -----Original Message----- - > From: Joshua Baker-LePain [mailto:[EMAIL PROTECTED]] - > Sent: Friday 05 April 2002 12:01 PM - > To: Doug Johnson - > Cc: Amanda-Users (E-mail) - > Subject: RE: amrecover - I have obviously overlooked something - > - > - > On Fri, 5 Apr 2002 at 11:48am, Doug Johnson wrote - > - > > I am assuming that I need one of these files for amandaidx - > and amidxtape. Is - > > this correct? - > > - > Yep. Mine look like: - > - > [jlb@chaos jlb]$ cat /etc/xinetd.d/amandaidx - > # default: off - > # - > # description: Part of the Amanda server package - > service amandaidx - > { - > disable = no - > socket_type = stream - > protocol = tcp - > wait = no - > user = amanda - > server = /usr/local/libexec/amindexd - > } - > [jlb@chaos jlb]$ cat /etc/xinetd.d/amidxtape - > # default: off - > # - > # description: Part of the amanda server package - > # - > service amidxtape - > { - > disable = no - > socket_type = stream - > protocol = tcp - > wait = no - > user = amanda - > server = /usr/local/libexec/amidxtaped - > } - > - > Also note that xinetd needs more than just a HUP to restart - > itself. Just - > do '/etc/init.d/xinetd restart' after adding those files, and - > you'll be - > ready to go. - > - > - > -- - > Joshua Baker-LePain - > Department of Biomedical Engineering - > Duke University - > - -- -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
