Re^2: IPC::Run and ACLs?

Replies are listed 'Best First'.
Re^3: IPC::Run and ACLs? by BrowserUk (Patriarch) on Apr 03, 2014 at 21:40 UTC
I was thinking it might be speedier to switch to a different existing module Why are you using IPC::Run instead of (say) system or a piped-open? 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.	[reply]
Re^4: IPC::Run and ACLs? by larryl (Monk) on Apr 03, 2014 at 21:58 UTC
In this case I need to be able to send STDIN and have access to both STDERR and STDOUT, and could switch to an alternative that can do that, but I'm not aware that can be done with system() or a piped open().	[reply]
Re^3: IPC::Run and ACLs? by wjw (Priest) on Apr 04, 2014 at 06:55 UTC
Once again, I know nothing of working with IPC, and thus was curious...dug around a bit on CPAN and noticed that IPC::Run3 seems to be reasonably current and has only a couple of bugs with recent activity dating around March this year. Again, this might not even be appropriate or applicable, but thought that the patch idea might work (or be more hopeful) if you tried it with a more recent package. At the bottom of the CPAN link above there seems to be a comparison to IPC::Run, though I don't know how objective that might be. At any rate, hope this is worth considering(aka reasonably helpful) for you. ...the majority is always wrong, and always the last to know about it... Insanity: Doing the same thing over and over again and expecting different results.	[reply]
Re^4: IPC::Run and ACLs? by larryl (Monk) on Apr 04, 2014 at 13:58 UTC
Thanks, I took a quick peek at IPC::Run3 too and it also was failing, although I am not sure if for the exact same reason. I may go back and take a closer look.	[reply]


"be consistent"
	PerlMonks