From owner-freebsd-isp Tue Sep 15 20:02:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA15485 for freebsd-isp-outgoing; Tue, 15 Sep 1998 20:02:53 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from enya.hilink.com.au (enya.hilink.com.au [203.8.14.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA15469 for ; Tue, 15 Sep 1998 20:02:49 -0700 (PDT) (envelope-from danny@enya.hilink.com.au) Received: from localhost (danny@localhost) by enya.hilink.com.au (8.8.8/8.8.7) with SMTP id KAA24728; Wed, 16 Sep 1998 10:02:46 +1000 (EST) (envelope-from danny@enya.hilink.com.au) Date: Wed, 16 Sep 1998 10:02:45 +1000 (EST) From: "Daniel O'Callaghan" To: Robert Adams cc: freebsd-isp@FreeBSD.ORG Subject: Re: Chroot + Freebsd In-Reply-To: <059801bddc31$f5ecffa0$28abf4ce@mp.siscom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 9 Sep 1998, Robert Adams wrote: > Was wondering is anything is running chroot'ed virtual servers.. we are > thinking of moving all our vitual servers into a virtual environment so that > they each have there own little system going on..then using something like > xinetd to all the servers for each.. anyone done this? I started doing this 4 years ago, and I'm still doing it. It's easy to hack apache to chroot itself into /chrootdir/192.168.1.1. Note that you'll need to start a separate instance of apache for each VWS. It's also easy to hack inetd to use getsockname(2) to find out the local IP address and chroot in the child before execing telnetd or ftpd. This is getting to be a FAQ. Maybe I should write a Handbook section on it.... Danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message