Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!cornell!uw-beaver!teknowledge-vaxc!sri-unix!quintus!jabir
From: jabir@quintus
Newsgroups: comp.os.vms
Subject: exec() from a subprocess
Message-ID: <157@quintus.UUCP>
Date: 7 Jul 88 21:42:05 GMT
Sender: news@quintus.UUCP
Reply-To: jabir@quintus ()
Organization: Quintus Computer Systems, Inc.
Lines: 24


Hi,

	i was wondering if someone here could help me with the following problem:

	i am trying to have a (sub)process exec() something else on top of itself.
	unfortunately, LIB$DO_COMMAND() and LIB$RUN_PROGRAM() are not guaranteed
	to work if the parent happens to be a subprocess itself.  LIB$SPAWN() is
	not much help because i do not want to get restricted by PRCLM quotas, etc.

	the doc for LIB$DO_COMMAND() says that it will not work correctly since
	there is no CLI associated with an image "run directly as a subprocess".
	however, the doc for LIB$SPAWN() (which would be used -- via exec() -- to
	start the parent itself), says that the SPAWNer's CLI is passed on to the
	SPAWNed process.  why, then, the warning accompanying LIB$DO_COMMAND()?

	i tried LIB$DO_COMMAND() both from a top-level program and a subprocess,
	and it seems to work.  does that mean that the warning can be ignored?

	thanks.


							jabir hussain
							sun!quintus!jabir