Solaris scripts

mukey

 I am attempting to get scripts to run on a solaris box (SunOS 5.10 sun4v).  Its a simple script that returns the uptime of the system.

 ------------------------------------------
#!/bin/ksh

utime=`uptime`
days=`uptime | awk '{print $3}'`

echo "Message: $utime"
echo "Statistic: $days"
exit 0
--------------------------------------------

The error message I am receiving is "Connection timeout. Job canceled by scheduler."

I can see the solarwinds script user logging into the server via ssh.  I can also see the temp. script files in /tmp and they are executable and return valid results.

The user stays logged in for 5 minutes (polling timeout), then disconnects.  Doing a "who", I can see the the user is sitting at a "sh" prompt for a majority of the time.  It seems as if its having issues exiting the shell after its done running the script? 

josh.clark

This is a bug.  When the monitor starts it switchs to the sh shell.  On Linux distros, this is a sym-link to bash.  On Solaris, this seems to be the original borne shell.  This shell has a command line limit of around 267 characters.  One of the commands we send is large (its actaully several command sent together).  Anyway, this can be longer than the 267 limit.  Once the limit is hit, you can't even hit enter to submit the partial command.  So the monitor just sits there waut for a reply that will never come.

 As a work around, you could create a shell function or an alias for the Solaris user the script runs as.  This would map sh to bash.  You could add something like this to the user's .profile

function sh() { bash; }

 This will start bash whenever we call sh.