Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!mcnc!duck!spl From: spl@duck.ncsc.org (Steve Lamont) Newsgroups: comp.sys.sgi Subject: Re: What does winopen(3G) do? Keywords: winopen sgi edge background parent child wsh Message-ID: <2238@speedy.mcnc.org> Date: 30 May 90 23:48:44 GMT References: <8274@odin.corp.sgi.com> Sender: daemon@mcnc.org Distribution: na Organization: Foo Bar Brewers Cooperative Lines: 17 In article <8274@odin.corp.sgi.com> robert@sgi.com writes: >by default, winopen does a fork(), creating a running copy of your >program, then the original program terminates. > >Issue the foreground() call before you do any winopen()'s, if this is >not what you want. Pardon my puzzlement, but what are the comparative advantages of forking or not forking upon winopen()? spl (the p stands for puzzled person) -- Steve Lamont, sciViGuy (919) 248-1120 EMail: spl@ncsc.org NCSC (The other one), Box 12889, Research Triangle Park, NC 27709 "It's not a question of whose habitat it is, it's a question of how hard you hit it." -Douglas Adams, "Hitchhiker's Guide to the Galaxy"