Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!ub!uhura.cc.rochester.edu!rochester!kodak!ispd-newsserver!weimer
From: weimer@ssd.kodak.com (Gary Weimer)
Newsgroups: comp.unix.questions
Subject: Re: mv'ing files from a C program
Message-ID: <1990Nov15.183359.963@ssd.kodak.com>
Date: 15 Nov 90 18:33:59 GMT
References: <22@mixcom.UUCP> <1990Nov15.132952.11932@virtech.uucp>
Sender: news@ssd.kodak.com
Distribution: na
Organization: Eastman Kodak
Lines: 11

In article <1990Nov15.132952.11932@virtech.uucp> cpcahil@virtech.UUCP (Conor P. Cahill) writes:
>You don't have to use system(3), you can use fork/execl(2) (or one of it's 
>family of functions) as follows:
>
>	if( fork() == 0 )
>		execl("/bin/mv","mv",oldfile,newfile,(char *)0);
>	else
>		wait((int *)0);

That's just about exactly what system(3) does. (i.e. you gain nothing for
all the added code)