Some 'System Calls' was Capturing system call output value

[Drieux]

On Friday, Nov 14, 2003, at 18:39 US/Pacific, Jerry Rocteur wrote:

> Beautiful drieux, what a sexy way to do a system call!!
>
> And I never knew about $host = hostname;.. What a neat trick..
>
> Keep 'em comin...

Wiggins is the one who deserves the point,
since he was the one with the reference
to Sys::Hostname, and when one sees such
things one should just do the

perldoc Sys::Hostname

read the pod, copy and paste from the pod
the call that one needs and move on to
the next problem.

ciao
drieux

---

[addy john]

Replaces the current process by running the given external command. If exec is given a single argument, that argument is taken as a line that is subject to shell expansion before being executed. If multiple arguments are given, the second and subsequent arguments are passed as parameters to command with no shell expansion. If the first argument is a two-element array, the first element is the command to be executed, and the second argument is used as the argv[0] value, which may show up in process listings. In MSDOS environments, the command is executed in a subshell; otherwise, one of the exec(2) system calls is used, so the running command may inherit some of the environment of the original program (including open file descriptors).