Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!sdd.hp.com!ucsd!ucbvax!NAZGUL.PHYSICS.MCGILL.CA!loki
From: loki@NAZGUL.PHYSICS.MCGILL.CA (Loki Jorgenson Rm421)
Newsgroups: comp.sys.sgi
Subject: exec'ing graphics-based processes
Message-ID: <9101241839.AA10580@nazgul.physics.mcgill.ca>
Date: 24 Jan 91 18:39:06 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 18


	OK... riddle me this, Graphics-Gurus:  If I exec() a process,
I have to live with having no access to graphics in this new process.
This is according to exec(2). ( I don't understand why)

	Unfortunately, I need to pass on a socket to this new process,
which is a graphics-oriented process, so a fork() or exec() is necessary.
So I am in a double bind.  Is there a way out?

	I am admittedly a bit green when it comes to using sockets so
there may be some vital info which I am missing.

Thanks,
                             __          __
Loki Jorgenson              / /          \ \  node:  loki@Physics.McGill.CA
Grad, Systems Manager      / //////  \\\\\\ \ BITNET: PY29@MCGILLA
Physics, McGill University \ \\\\\\  ////// / fax:   (514) 398-8434
Montreal Quebec CANADA      \_\          /_/  phone: (514) 398-7027