Re: Proc::Background does not take file path with spaces

Looking inside the Win32 component of Proc::Background it does some pretty dubious manipulations with the program component of its arg(s), including if, -- after it has done some other incomprehensible manipulations -- the length of the command argument is 0, then it wraps that zero length arg in quotes:

      if (length($arg) == 0 or $arg =~ /\s/) {
        $arg = "\"$arg\"";
      }
[download]

None of which bodes well for success.

If all you need is to start a process in the background, a simple:

my $pid = system 1, 'c:/program Files (x86)/vs.exe';
[download]

Does the job.

if( kill $pid, 0 ) { ... will tell you if it is still running.

kill $pid, 3; will terminate it.

waitpid $pid,0; my $retcode = $?; will get the return code.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

The start of some sanity?

Comment on Re: Proc::Background does not take file path with spaces Select or Download Code

Replies are listed 'Best First'.
Re^2: Proc::Background does not take file path with spaces by SuicideJunkie (Vicar) on Apr 27, 2012 at 13:34 UTC
On a windows command line, your parameters are all (white?)space separated. If you want a zero-length parameter you need to double quote it so it isn't ignored, like so: `USAGE: mangle.exe [filename] [password] [index number] mangle.exe unprotected.dat "" 42` [download] Parameters that are all whitespace have the same problem and solution. No idea on why it had to be done that way though.	[reply] [d/l]
Re^3: Proc::Background does not take file path with spaces by BrowserUk (Patriarch) on Apr 27, 2012 at 14:11 UTC
If you want a zero-length parameter Hm. Okay, you got me there. Mind you, in 30 years I don't remember ever having used a command that took a "zero length parameter". Every command I'm aware of that takes a password has an option to supply it. And optional parameters always come at the end. With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday' Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. The start of some sanity?	[reply]
Re^4: Proc::Background does not take file path with spaces by dinasour (Novice) on Apr 28, 2012 at 00:08 UTC
Hi Guys I end up using the following `use Win32; $CommandNew = Win32::GetShortPathName("C:\\Program Files (x86)\\vs.exe +"); Proc::Background->new($CommandNew);` [download] Thanks for looking	[reply] [d/l]


XP is just a number
	PerlMonks