comment on

@cdarke

This worked and thank you. I had to make two small changes (noted in the code below) but I have success.

The first change was enclosing the script execution command in single quotes and the second was adding perl to the command call.

The end result is two perl scripts.

The orignal script (with updates)

&Chg_User ($other_user);
#&Chg_Directory ($dir_location);
…
…
…
## the sub_routines below
sub Chg_User {
   #system("su -c ./script2.pl");       #from cdarke
   system("su -c 'perl script2.pl'");     #with changes
   
   #if ( $chg_result == -1) {
   #   print "wrong password: $!\n";
   #   exit (-1);
   #}
}
sub Chg_Directory {
   system (“cd”, “$_[0]”);        
}
[download]

and script2.pl (with the script for the "other_user" shell)

   print ("Not the cOmMaNd LiNe from script2 \n");
[download]

I would like to get the IPC::ShellCmd package to see if this will eliminate the need of a second script file; however, this takes care of my needs for the day and moves me closer to my goal

Thanks to all of you.

In reply to Re^3: system commands and returns by perl_zen
in thread system commands and returns by perl_zen

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.


Come for the quick hacks, stay for the epiphanies.
	PerlMonks