taguti wrote:
>
>>did you try fork and exec
>>
>
> No I don't like to do it if possible.
You know a system call basically does a fork and exec except it
waits for the call to finish.
--
,-/- __ _ _ $Bill Luebkert ICQ=162126130
(_/ / )// // DBE Collectibles
> I don't know what LD_PRELOAD does to affect the backgrounding,
It's very harmful.
For example I must do "LD_PRELOAD=;export LD_PRELOAD"
during installing CPAN module.
Unless I fail on make after "perl Makefile.PL".
> did you try fork and exec
No I don't like to do it if possible.
> and if ne
taguti wrote:
>> You can run a command in the background with:
>>
>> system("cmd &");
>>
>
> Oh I remember this. Yes, but now my env has:
> LD_PRELOAD=/lib/libthread.so.1
> which is required for DBD::Oracle.
> And when I run "testexec1.pl", I get core dump.
> I can do it when I reset
> You can run a command in the background with:
>
> system("cmd &");
Oh I remember this. Yes, but now my env has:
LD_PRELOAD=/lib/libthread.so.1
which is required for DBD::Oracle.
And when I run "testexec1.pl", I get core dump.
I can do it when I reset:
LD_PRELOAD=;export LD_PRELOA
> If you just want to run another Perl script and not have the existing Perl
> script wait for it to return use "exec" instead of "system". Taken from the
My main script is started by cron on every 00 minutes,
00:00, 01:00, 02:00 and so on, and it must execute another
script on xx::00 & xx::15 &
