Path: utzoo!attcan!uunet!lll-winken!ames!ucsd!rutgers!att!lzaz!lznh!ariel
From: ariel@lznh.UUCP (<10000>Ariel Aloni)
Newsgroups: comp.databases
Subject: Re: unify 3.2 and 4.0 selsort() problems
Keywords: unisort()==fork()
Message-ID: <1996@lznh.UUCP>
Date: 19 Jan 89 15:53:47 GMT
References: <1074@wpg.UUCP> <24897@sgi.SGI.COM> <1081@wpg.UUCP> <1995@lznh.UUCP> <300@spca6.UUCP>
Reply-To: ariel@lznh.UUCP (<10000>Ariel Aloni)
Organization: AT&T, Lincroft, NJ
Lines: 12

In article <300@spca6.UUCP> ray@spca6.UUCP (ray) writes:
>Just something every Unify HLI user should know, any call to unisort is
>will cause a fork() system call.  This is implicit in the manual, but
This is the first time i here this (shame :-). Can you clarify on the
issue ? Is an exec* also involved ? (probably yes, and an exec is
much more exepensive than a fork on most Unix sytems).
The only thing that caught my eye in the manual is something about
a "general sorting function ...". Do they mean sort(1) ?
ariel
-- 
Ariel A. Aloni                                 att!lznh!ariel
"Just because you are parnoid doesn't mean they are not after you"