Thanks for all the great suggestions. Unfortunately, changing the environment is quite impossible. I'm stuck having to 'sudo bash'. If I can't automate through that (icky) interface, I'm stuck largely copy/pasting chunks of commands.
Why are you stuck to 'sudo bash'? Why can't you do `sudo perl_script`?
Well, even if you can't control sudo configuration and only "bash" is available for execution, then try something like
my $pid = open(OUT, "|-");
die "Can't fork\n" unless defined $pid;
if(!$pid)
{
exec "sudo bash";
die "oops no exec\n";
}
select OUT;
$| = 1;
print "echo hi there\nexit\n";
close(OUT);
Read perldoc perlipc. Section Bidirectional Communication with Another Process. Maybe this will help you to do simple automation.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|