Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!watmath!clyde!cbosgd!ulysses!ucbvax!apollo
From: mishkin@APOLLO.UUCP (Nathaniel Mishkin)
Newsgroups: mod.computers.apollo
Subject: Re: DM commands CV and RO
Message-ID: <8603040447.AA05021@uw-beaver.arpa>
Date: Mon, 3-Mar-86 09:45:16 EST
Article-I.D.: uw-beave.8603040447.AA05021
Posted: Mon Mar  3 09:45:16 1986
Date-Received: Wed, 5-Mar-86 04:30:35 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 27
Approved: apollo@yale-comix.arpa


    
    We just switched to 4.2BSD.  The "inlib" command, when executed from
    within csh, doesn't seem to load the mentioned library (the las doesn't
    contain the library name).  Is there a fix for this?

"inlib" is a built-in shell (/bin/csh, /bin/sh, /com/sh) command that
causes a library to be dynamically loaded into the address space of the
shell that executes the command.  The reason you're having a problem
is because the csh invokes commands (e.g. las, and any other non-builtin)
by vforking a new process and then exec'ing the command.  The exec
operation causes the contents of the "copied" address space -- including
the thing you inlib'd -- to be wiped out.

You can:

    set inprocess

if you want the csh to do its command invocations in the same process
and then the inlib'd library will be available to commands you invoke.
However, then job control (which, of course, depends on the command you
run being in a separate process) won't work.

                -- Nat Mishkin
                   Apollo Computer
                   apollo!mishkin
-------