Beefy Boxes and Bandwidth Generously Provided by pair Networks
Your skill will accomplish
what the force of many cannot

Re: IPC::Run and ACLs?

by kcott (Chancellor)
on Apr 04, 2014 at 07:57 UTC ( #1081083=note: print w/replies, xml ) Need Help??

in reply to IPC::Run and ACLs?

G'day larryl,

Take a look at Capture::Tiny. That may do what you want. If not, its SEE ALSO sections lists more than 20 modules with similar or related functionality (one or more of these may be suitable).

[Note: I can't comment on the ACL-awareness of any of those modules.]

-- Ken

Replies are listed 'Best First'.
Re^2: IPC::Run and ACLs?
by larryl (Scribe) on Apr 04, 2014 at 14:04 UTC

    Many thanks, I was not aware of Capture::Tiny, I see there is also a Capture::Tiny::Extended. It's not immediately clear to me how I would use those while sending info to the STDIN of the script, will have to look at that...

    The SEE ALSO section in Capture::Tiny is useful, I think I will check out IPC::Open3 and IPC::Open3::Simple since those handle all of STDIN, STDOUT and STDERR - hopefully they will not suffer from the same permissions problem as IPC::Run.

      "... Capture::Tiny ... not immediately clear to me how I would use those while sending info to the STDIN ..."

      Looking at other responses you've posted in this thread, I do see STDIN mentioned. I didn't notice that when I first replied: Capture::Tiny probably is unsuitable.

      IPC::Open3 is part of the core Perl distribution; if that turns out to suitable (ACL-wise), then there's no installation requirement.

      -- Ken

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1081083]
[Eily]: you could tie a variable into not having the same value each time, if you like to make people who try to debug your code facepalm
[Corion]: perl -wle 'package o; use overload q("") => sub {warn "str"; ""}, bool => sub{warn "bool"; 1}; package main; my $o={}; bless $o => o; print "Yay" if ($o && !length($o))'
[Corion]: But people writing such code should document the objects they construct and why it makes sense for an object to be invisible as string while being true in a boolean context
[hippo]: That's equal parts clever and horrendous.
[Eily]: the overload version wouldn't return true with "$x" && !length $x though, I guess
[hippo]: The more I look at this code, the more $x is a plain old scalar and the more this condition will never be true. I'm calling it a bug at this point.
[hippo]: Thanks for your input which has soothed my sanity (a little)
[Corion]: Eily: Sure - if you force both things into stringy things, then you break that magic. But that would also mean that you changed the expression, as now $x = 0.00 will be true instead of false as it were before
[Corion]: Ah no, at least in my feeble experiments that doesn't change the meaning
[Corion]: We sell sanity in small packages ;)

How do I use this? | Other CB clients
Other Users?
Others drinking their drinks and smoking their pipes about the Monastery: (9)
As of 2017-07-27 13:40 GMT
Find Nodes?
    Voting Booth?
    I came, I saw, I ...

    Results (413 votes). Check out past polls.