template script execute a command line

Hi there,

How to execute a command line in template script?
Not getting any result.

Thanks!

 my $user = "__TAG__('iw_user');"; my $command ="cat /etc/passwd |grep ".$user; my $test=`$command`;

Find more posts tagged with

Comments

nipper

Hi there,

How to execute a command line in template script?
Not getting any result.

Thanks!

<template_script>
<![CDATA[
my $user = "__TAG__('iw_user');";
my $command ="cat /etc/passwd |grep ".$user;
my $test=`$command`;
]]>
</template_script>

<successors>
<successorset description = "Test:lithium_INSERT__($test);">
<succ v = "End"/>
</successorset>

Fixing post

nipper

OK, so is this just an example or is this actually what you want to do ? It would be much better to just open the /etc/passwd, read the contents and regex it.

Now can you run external processes from template_script. Certainly.

Here is code I use


my $host = `hostname`;
my $owner="";

if ($host =~ m|vmware2k|i) {
 $owner="vmware2k\\andy";
 $admingrp = "vmware2k\\iwTake"
 } else {
 $owner="mainserver\\tsadmin";
 $admingrp = "mainserver\\tsadmingroup"
}


and later:

<submittask name = "Submit" owner = "__INSERT__($owner);" start = "f" unlock = "t" override = "f" skiplocked = "f" savecomments = "t" skipconflicts = "f">

Adam Stoller

Hi there,

How to execute a command line in template script?
Not getting any result.

Thanks!

Original code:[html] my $user = "__TAG__('iw_user');"; my $command ="cat /etc/passwd |grep ".$user; my $test=`$command`; 

[/html]There are probably multiple things wrong with the above - for one thing you're invoking system commands where you don't need to and getting a result which - even if you got them on STDIN - probably wouldn't be what you wanted - or were you really intending to put one or more entire password entries in as a description for a successorset?

Let's just start with some basic practices:

cat file | grep pattern

is the same as [font]grep pattern file[/font] with one less shell process being spawned.

Depending on your need for searching through this information vs. memory footprints and such - if it is truly a one-off then invoking another shell process like:

my $results = qx(grep pattern file 2>&1);

is probably okay. If you intend to extract multiple pieces of information from that one file - you'll probably be better off reading it into memory - either an array, if you don't know what to use as a defining key for each line of data - or a hash which you can then more easily reference once you have it in memory.

For what you appear to be doing - if you have the userid - just call getpwnam($userid) and you'll get an array of values returned, of which the 3rd is the UID, the 7th is the GCOS field (often the "friendly name"), and you can figure out the rest if you need them:

iwperl -le 'print ((getpwnam("userid))[6]);'