Re^2: Strange system call failure in OS X

I have more system calls which might be cleaner if I send them as a list. Do I break it into a separate item for each argument? Any need for quotes? Here are the other system calls. They do actually work as they are but I would like to learn how to use the system call the "right" way so to speak.

# Disable autologin
@args = ("defaults delete /Library/Preferences/com.apple.loginwindow a
+utoLoginUser");
system(@args);

# exit our test version here before doing anything irrevocable
exit 0;

# Serialize Adobe CS6 Design and Web Premium
@args = ("/Library/AdminToolBox/AdobeSerialization adobe_prtk --tool=V
+olumeSerialize --provfile=/Library/AdminToolBox/prov.xml");
system(@args);

# Bind to Active Directory
@args = ("/Library/AdminToolBox/bind.sh");
system(@args);

# This time we'll use exec since we are restarting anyway
@args = ("/sbin/shutdown -r now");
exec(@args);
[download]

Comment on Re^2: Strange system call failure in OS X Download Code

Replies are listed 'Best First'.
Re^3: Strange system call failure in OS X by Anonymous Monk on Feb 15, 2013 at 21:25 UTC
Do I break it into a separate item for each argument? Yes, it is `system "/usr/bin/foobar", "arg", "arg", "--arg=arg" ...` Any need for quotes? No. Quotes are for the shell. See system/exec.., kinda dense/long, but essentially `system q{single "st" "ri" "ng"}` could be open to shell interpolation/invoke the shell, while `system "single", "st", "ri", "ng"` will avoid the shell So list is preferable because you don't have to quote to a particular shell , just quote for perl perlop#Quote and Quote like Operators discusses making a list with qw" st ri ng "; While you're in a learning mood, get a free copy of Modern Perl See also perlrun Behind the GUI lives the Shell Windows Command Line Interpreter\|Shell\|DOS Prompt\|Batch Files\|Scripting Csh Programming Considered Harmful How Command Line Parameters Are Parsed http://www.gnu.org/software/bash/manual/bashref.html#Quoting String::ShellQuote/Win32::ShellQuote, Re: system() implementation on Windows (again), Re^3: system() implementation on Windows (again), Everyone quotes command line arguments the wrong way Proc::Background The Windows NT Command Shell exec always invokes the shell? win32, System, exec different behaviour with spaces	[reply] [d/l] [select]
Re^4: Strange system call failure in OS X by Anonymous Monk on Feb 15, 2013 at 21:39 UTC
`$ perl -MData::Dump -e " dd\@ARGV " "he llo" there "bu ddy" ["he llo", "there", "bu ddy"] $ perl -MData::Dump -e " dd\@ARGV " he llo there bu ddy ["he", "llo", "there", "bu", "ddy"] $ perl - he llo there bu ddy use Data::Dump; dd\@ARGV; __END__ ["he", "llo", "there", "bu", "ddy"] $` [download]	[reply] [d/l]


more useful options
	PerlMonks