From owner-freebsd-questions Tue Jun 10 17:55:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA17431 for questions-outgoing; Tue, 10 Jun 1997 17:55:22 -0700 (PDT) Received: from bureau6.utcc.utoronto.ca (bureau6.utcc.utoronto.ca [128.100.132.16]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id RAA17423 for ; Tue, 10 Jun 1997 17:55:19 -0700 (PDT) Received: from ingli.interlog.com ([207.34.213.11]) by bureau6.utcc.utoronto.ca with SMTP id <159930(6)>; Tue, 10 Jun 1997 20:54:33 -0400 Message-ID: <339DF49E.5AC6@utoronto.ca> Date: Tue, 10 Jun 1997 20:43:10 -0400 From: edward.ing@utoronto.ca X-Mailer: Mozilla 3.01 (Win95; I) MIME-Version: 1.0 To: freebsd-questions@FreeBSD.ORG Subject: User server daemons listening on SOCKETS? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Is it possible to programme a server daemon that listens on a Socket and then spawns a new connection process to provide the service to run under a users environment rather than the root environment. For example I was going to write a Java server to run a user account and distribute a client so that users of the client can connact my server over the internet. I don't have root access to unix box on the 'Net so I would like to resort to running a service from my user account. Is this easily accomplished? Or will unix kernels not allow this kind of "sockets-on-user-demand" processes? If I can, how can I write a routine to automatically determine which ports are free so my server will not spawn a process which will uses a port that another daemon on the host is using? What security loop-holes might there be? edward.ing@utoronto.ca