From owner-freebsd-security Thu Dec 24 11:35:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09868 for freebsd-security-outgoing; Thu, 24 Dec 1998 11:35:40 -0800 (PST) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA09862 for ; Thu, 24 Dec 1998 11:35:37 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id LAA34947; Thu, 24 Dec 1998 11:35:24 -0800 (PST) (envelope-from dillon) Date: Thu, 24 Dec 1998 11:35:24 -0800 (PST) From: Matthew Dillon Message-Id: <199812241935.LAA34947@apollo.backplane.com> To: Jeff Gray Cc: "Joseph T. Lee" , freebsd-security@FreeBSD.ORG Subject: Re: Do I really need inetd? References: Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org :Matt, : :Appreciate the suggestion. : :To save some of us syntax problems maybe you could post the lines, ones :that work are always nice. : :Thanks :Jeff I usually just run: inetd -l -R 1024 If you want, you can also add in the '-c N' option to absolutely guarentee that an attack will not take the machine down. i.e. '-c 600' or something like that. If you need fine control for specific services, you can specify a maxchild after the wait|nowait field, i.e. 'wait/200' rather then 'wait'. I suggest playing with it. The manual page is quite clear on the matter. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message