There are a number of things that break when trying to use the medley script and the loadup script on Solaris.
-
head does not accept a --bytes argument: elif [ "$(uname -s | head --bytes 6)" = "CYGWIN" ] should probably use ... | cut -c1-6)"... instead, assuming CYGWIN has cut
-
medley /path/to/sysout doesn't work as advertised:
medley /opt/medley/loadups/full.sysout
head: illegal option -- bytes
In command line arguments:
ERROR: unexpected argument "/opt/medley/loadups/full.sysout"
Usage: medley [flags] [sysout] [--] [pass_args ...]
medley --full (or any other --name-of-sysout) doesn't work because script locating doesn't work (see 4)
medley --full
head: illegal option -- bytes
Error: The sysout argument --full was specified in command line arguments,
but the directory "//loadups" where full.sysout is supposed to be located
cannot be found.
Exiting.
loadup -f doesn't work because it can't find where the script directory is.
% loadup -f
/opt/medley/loadup[223]: .: /opt/medley/loadup-setup.sh: cannot open [No such file or directory]
Solaris seems to make a point of ensuring that when a script locates where it was called from it gets the source directory of the symbolic link not the directory where the symbolic link points.
There are a number of things that break when trying to use the
medleyscript and theloadupscript on Solaris.headdoes not accept a--bytesargument:elif [ "$(uname -s | head --bytes 6)" = "CYGWIN" ]should probably use... | cut -c1-6)"...instead, assuming CYGWIN hascutmedley /path/to/sysoutdoesn't work as advertised:medley --full(or any other --name-of-sysout) doesn't work because script locating doesn't work (see 4)loadup -fdoesn't work because it can't find where the script directory is.Solaris seems to make a point of ensuring that when a script locates where it was called from it gets the source directory of the symbolic link not the directory where the symbolic link points.