On Tuesday 21 August 2001 05:00 pm, you wrote:
> Spoke to soon as to my problem beign solved, what is happening now is that
> the tar/zip operations are still running when my script copies ythe files
> and dates them for the archive folder, the working part of the script is
> something like
>
> ex
Doh, you're right. Just like unix exec. I stand corrected. :)
-Original Message-
From: Bob Showalter [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 22, 2001 8:02 AM
To: '[EMAIL PROTECTED]'
Subject: RE: Help request for backup perl script
> -Original Message--
> -Original Message-
> From: Rogers, Gary (AP- Server Adminstrator)
> [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, August 22, 2001 9:51 AM
> To: 'Duston S. Horacek'; perl
> Subject: RE: Help request for backup perl script
>
>
> exec() forks off a p
exec() forks off a process and lets it run without caring about the return
process. It's kinda like UPD, you can exec as many processes as you want and
perl isn't too concerned with what happens with the processes.
system() forks off a process and waits for it to finish. It's like TCP, it
wants t
OK, I have been reading the Learning Perl book but I think I know this one.
The system() function should wait for the process to finish before moving on
(read this a couple days ago, might be misremembering it) but for really
fine control you can use the fork() then exec(), and maybe throw in a
wa
You probably want a semicolon instead of the pipe
exec("tar -z -cf area.tgz ../Mud/area/; cp area.tgz
archive/area_$backupdate.tgz");
I didn't see the original post, but you might want to consider using system
instead of exec. You cannot do anything
after an exec except for check its return stat
For all those that helped, thank you, the script works great, and now will
zip the files in the directories I need it to, then move them to an archive
folder, thanks to
matthschulz [[EMAIL PROTECTED]]
and
Troy Denkinger [[EMAIL PROTECTED]]
who gave me the date portions with two seperate ideas tha
