From owner-freebsd-java Wed Nov 14 1:59:46 2001 Delivered-To: freebsd-java@freebsd.org Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by hub.freebsd.org (Postfix) with ESMTP id D67D637B405 for ; Wed, 14 Nov 2001 01:59:43 -0800 (PST) Received: by l04.research.kpn.com with Internet Mail Service (5.5.2653.19) id ; Wed, 14 Nov 2001 10:59:36 +0100 Message-ID: <59063B5B4D98D311BC0D0001FA7E452205FDA0A5@l04.research.kpn.com> From: "Koster, K.J." To: 'Ernst de Haan' , Rob Simmons Cc: freebsd-java@FreeBSD.ORG Subject: RE: another orion question Date: Wed, 14 Nov 2001 10:59:33 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Dear Ernst and Rob, > > > I have another question. I have a shared box that I'm trying to run > > multiple instances of orion on. I am able to get each > > instance to listen > > on different IP addresses, but orion starts a listener on > > port 23791 on > > its own. Is there a way to get the orion instances to open > > this port separately on each IP address? > I've been wondering if it's possible to jail a whole tribe of Orion instances, each in a slammer of their own. This would solve the port 23791 problem, as well as allow users to have ssh access to "their" instance in a fairly safe way. That port is part of a protocol for remote management of Orion. I think admin.jar is the guilty party here. I remember playing with it, but tossing it aside since it did nothing that I could not do with cp(1) and kill(1). :) Kees Jan ================================================ You are only young once, but you can stay immature all your life. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message