At 06:08 AM 11/12/2005, you wrote:
> I disabled identd in inetd.conf. > I issued a kill -1 on the identd process. ^^^^^identd process or inetd process ? After a change in inetd.conf you want to kill -HUP the latter, inetd. If you see an identd running than you may either see something spawned by inetd or a standalone identd which is not ran from inetd. In that case you'll need to kill identd and/or remove it from your rc startup. Dw.
Thanks...but I did that (was a typo). I just dont understand why (when identD is disabled in inetd.conf) that the machine does not immediately respond back with CONNECTION REFUSED - but sits for 5-8 seconds.
As a better fix for now, I simply added a block RST into pf.conf and basically accomplished the same thing.
-- J.D. Bronson Information Services West Allis Memorial Hospital Aurora Health Care - Milwaukee, Wisconsin Office: 414.978.8282 // Fax: 414.977.5299 Microsoft Gives you Windows || Unix Gives you a home
