Shlomi Fish wrote:
What system() does (at least on UNIX-like OSes) is fork a child, call exec()
with a new process and wait for the new child to terminate (plus some other
stuff to get rid of misbehaviours).
... and if you call "system" with just one long string, then Perl opens the
system def
Hi xiaolan,
On Tue, 14 May 2013 18:51:51 +0800
xiaolan wrote:
> Thanks all the answers.
> Shlomi long time no see :)
Yes. :-) I am available on IM:
http://www.shlomifish.org/me/contact-me/
>
> Have another question that, what's the difference between the system call
> child process and the
Thanks all the answers.
Shlomi long time no see :)
Have another question that, what's the difference between the system call
child process and the native forked child process?
Does the child process of system call have the problems of receiving
signals from the parent?
On Tue, May 14, 2013 a
Hi Brian,
thanks for replying well to xiaolan’s question.
Regards,
Shlomi Fish
--
-
Shlomi Fish http://www.shlomifish.org/
My Public Domain Photos - http://www.flickr.com/photos/shlomif/
95% of Programmers consider
On Tue, May 14, 2013 at 12:35 AM, xiaolan wrote:
> Hello,
>
> what's the disadvantage when calling a system command from Perl?
> i.e, system call to "rsync" rather than using the File::Rsync module.
> is it hard to control the signals between the caller process and the
> called system command?
>
On Tue, May 14, 2013 at 5:35 AM, xiaolan wrote:
> Hello,
>
> what's the disadvantage when calling a system command from Perl?
> i.e, system call to "rsync" rather than using the File::Rsync module.
> is it hard to control the signals between the caller process and the called
> system command?
We
