Use nover or agentinfo command.

Below uname command through nexec, requires cmd /c for Windows. But, your script is to identify the OS.

nexec $server cmd /c uname

Thanks,

Santhosh Kurimilla

BlackBerry# 7995072904

Using cmd /c is reserved for Windows systems:

nexec $SERVER cmd /c uname

/bin/bash: cmd: command not found

if you want it to work on linux systems do the following:

nexec $SERVER sh -c "uname -s"

Linux

I'm going to pretend to be Bill Robinson for a minute, and ask what exactly are you trying to accomplish here? What is your desired outcome? Why aren't you using the server property value for OS?

Have you tried this:

GROUP1="/Server/mygroup"

TOT_SRVS=`blcli Server listServersInGroup "$GROUP1"`

OS=$2

for server in $TOT_SRVS

do

#OS="$(nexec $server uname -s)"

echo $OS

echo "servername :$server and OS Type : $OS" >> $output_file

done

so that's kind of ok but there are some problems w/ it.

first - why are you doing this ?  why do you need to write the server:os to a file?  what are you going to do w/ that ?

so let's fix your script snippet above:

# unless you have a top level folder in the Servers workspace named 'Server' you don't include '/Server' in the group path.

GROUP1="/mygroup"

# why are you taking OS as an argument if that's what you are trying to derrive ?  so we'll take that out.

# you are not using the blcli very well here

blcli_execute Server listServersInGroup "${GROUP1}"

blcli_storeenv TOT_SRVS

# it's better habbit to use a while loop instead of a 'for' so you can handle spaces, etc. 

while read server

do

# why did you comment out the uname call ? 

OS="$(uname -D //${server} -s)"

echo "servername: ${server} and OS Type: ${OS}" >> "${output_file}"

# strip the trailing empty line from the list of servers

done <<< "$(awk 'NF' <<< "${TOT_SRVS}")"

 

 

matt's example is using a job to pass in the server name and the value of the server property.  that works if you are running this as a nsh job.  it's unclear if you are doing that or running this as a script from the command line.  instead of the uname call you could also run a blcli command to get the value of 'OS'.  that has the advantage of not needing nsh access to the targets.  if you are running this from the command line on some workstation that may be a problem.  this version of the script would look like:

GROUP1="/mygroup"

blcli_execute Server listServersInGroup "${GROUP1}"

blcli_storeenv TOT_SRVS

while read server

do

blcli_execute Server printPropertyValue ${server} "OS"

blcli_storeenv OS

echo "servername: ${server} and OS Type: ${OS}" >> "${output_file}"

done <<< "$(awk 'NF' <<< "${TOT_SRVS}")"

now, that could be slow depending if you have a lot of servers in the group.  so instead you could use a bulk dump of the property value:

GROUP1="/mygroup"

blcli_execute Server listServersInGroup "${GROUP1}"

blcli_storeenv TOT_SRVS

awk 'NF {print $1",OS"}' <<< "${TOT_SRVS}" > "/tmp/get.csv"

blcli_execute Server getBulkServerPropertyValuesAndLogResults "/tmp" "get.csv"

# results will be in /tmp/get_results.csv

uname is not a native windows command so your 'nexec cmd /c uname' won't work.