On Wed, Aug 02, 2000 at 03:09:58PM -0400, Tony Cleveland wrote:
> I had a script that pounded the CVS server when I ran into the same/similar
> problem and that fixed it for me. Obvious question - Did you do a "killall
> -HUP inetd" after you changed inetd.conf so inetd would reread it? Of course
> it could be something different.
You do realize, of course, that a "killall" command on a Solaris machine
will bring it down, right?
If you're going to use an operating system specific command, try to choose
one that will not have negative effects on other systems.
Example, under Linux:
/bin/kill -HUP inetd
Under Solaris:
pkill -HUP inetd
Those don't, as far I know, have any negative effects if you accidently run
them on other systems. But even then, you should be careful (just as many
probably don't know that killall will kill everything on some systems, I
don't know every system and someone may decide to make pkill kill
everything!).
[Sorry to rant off topic, but I've personally been bitten by accidently
runnign killall in a wrong window I was root in and bringing down a
machine, and have since been on a crusade to stamp out the use of killall.]
mrc
--
Mike Castle Life is like a clock: You can work constantly
[EMAIL PROTECTED] and be right all the time, or not work at all
www.netcom.com/~dalgoda/ and be right at least twice a day. -- mrc
We are all of us living in the shadow of Manhattan. -- Watchmen
