This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallAnywhere
- :
- InstallAnywhere Forum
- :
- !: not found
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 14, 2009
06:30 AM
!: not found
When I am trying to execute my solaris installer I get this message...
!: not found
The installer executes fine and I am successfully able to install my solaris installer,but why this message.?
Thanks
-Vikz
!: not found
The installer executes fine and I am successfully able to install my solaris installer,but why this message.?
Thanks
-Vikz
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 06, 2009
04:06 PM
I am also getting the same message on Solaris. Any idea?
Could it be an issue with creating the package using JDK 1.6? Our previous release with JDK 1.5 do not have this issue.
Preparing to install...
Checking for POSIX df.
Found POSIX df.
Checking tail options...
Using tail -n 1.
True location of the self extractor: /space/966/setup.bin
Creating installer data directory: /tmp/install.dir.20377
Creating installer data directory: /tmp/install.dir.20377/InstallerData
Gathering free-space information...
Space needed to complete the self-extraction: 3524306 blocks
setup.bin: !: not found
Available space: 8576736 blocks
Available blocks: 8576736 Needed blocks: 3524306 (block = 512 bytes)
Computed number of blocks to extract: 2136
Extracting the JRE from the installer archive...
Extracting JRE from setup.bin to /tmp/install.dir.20377/Solaris/resource/jre_padded ...
Extracting done, exit code = 0
Extracting JRE from /tmp/install.dir.20377/Solaris/resource/jre_padded to /tmp/install.dir.20377/Solaris/resource/vm.tar.Z ...
Extracting done, exit code = 0
Unpacking the JRE...
Could it be an issue with creating the package using JDK 1.6? Our previous release with JDK 1.5 do not have this issue.
Preparing to install...
Checking for POSIX df.
Found POSIX df.
Checking tail options...
Using tail -n 1.
True location of the self extractor: /space/966/setup.bin
Creating installer data directory: /tmp/install.dir.20377
Creating installer data directory: /tmp/install.dir.20377/InstallerData
Gathering free-space information...
Space needed to complete the self-extraction: 3524306 blocks
setup.bin: !: not found
Available space: 8576736 blocks
Available blocks: 8576736 Needed blocks: 3524306 (block = 512 bytes)
Computed number of blocks to extract: 2136
Extracting the JRE from the installer archive...
Extracting JRE from setup.bin to /tmp/install.dir.20377/Solaris/resource/jre_padded ...
Extracting done, exit code = 0
Extracting JRE from /tmp/install.dir.20377/Solaris/resource/jre_padded to /tmp/install.dir.20377/Solaris/resource/vm.tar.Z ...
Extracting done, exit code = 0
Unpacking the JRE...
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 07, 2009
02:13 AM
This occurs in the self-extracting phase before installation and it's somewhere in this code taken from the Unix self-extractor:
[CODE]
[ $LAX_DEBUG ] && echo "Space needed to complete the self-extraction: $NEEDED_SPACE blocks"
sePwd=`pwd`
cd "$INSTBASE"
AVAIL_SPACE=`$DF_CMD . 2>/dev/null | awk "{print \\\$$DF_AVAIL_COL}" | tail $TAILN1ARG`
isValidNumber()
{
awk 'BEGIN {
if ( ARGV[1] ~ /^[0-9]+$/ ) {
exit(0);
} else {
exit(1);
}
}' "$1"
return $?
}
if ! isValidNumber "$AVAIL_SPACE"; then
echo "DF output not POSIX standard"
AVAIL_SPACE=`$DF_CMD . 2>/dev/null | awk -F: '{ print $2 }' | awk '{ print $1 }' | tail $TAILN1ARG`
if ! isValidNumber "$AVAIL_SPACE"; then
unset $AVAIL_SPACE
fi
fi
[ $LAX_DEBUG ] && echo "Available space: $AVAIL_SPACE blocks"
[/CODE]
[CODE]
[ $LAX_DEBUG ] && echo "Space needed to complete the self-extraction: $NEEDED_SPACE blocks"
sePwd=`pwd`
cd "$INSTBASE"
AVAIL_SPACE=`$DF_CMD . 2>/dev/null | awk "{print \\\$$DF_AVAIL_COL}" | tail $TAILN1ARG`
isValidNumber()
{
awk 'BEGIN {
if ( ARGV[1] ~ /^[0-9]+$/ ) {
exit(0);
} else {
exit(1);
}
}' "$1"
return $?
}
if ! isValidNumber "$AVAIL_SPACE"; then
echo "DF output not POSIX standard"
AVAIL_SPACE=`$DF_CMD . 2>/dev/null | awk -F: '{ print $2 }' | awk '{ print $1 }' | tail $TAILN1ARG`
if ! isValidNumber "$AVAIL_SPACE"; then
unset $AVAIL_SPACE
fi
fi
[ $LAX_DEBUG ] && echo "Available space: $AVAIL_SPACE blocks"
[/CODE]
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 09, 2009
12:23 AM
pv7721 wrote:
This occurs in the self-extracting phase before installation and it's somewhere in this code taken from the Unix self-extractor:
[CODE]
[ $LAX_DEBUG ] && echo "Space needed to complete the self-extraction: $NEEDED_SPACE blocks"
sePwd=`pwd`
cd "$INSTBASE"
AVAIL_SPACE=`$DF_CMD . 2>/dev/null | awk "{print \\\$$DF_AVAIL_COL}" | tail $TAILN1ARG`
isValidNumber()
{
awk 'BEGIN {
if ( ARGV[1] ~ /^[0-9]+$/ ) {
exit(0);
} else {
exit(1);
}
}' "$1"
return $?
}
if ! isValidNumber "$AVAIL_SPACE"; then
echo "DF output not POSIX standard"
AVAIL_SPACE=`$DF_CMD . 2>/dev/null | awk -F: '{ print $2 }' | awk '{ print $1 }' | tail $TAILN1ARG`
if ! isValidNumber "$AVAIL_SPACE"; then
unset $AVAIL_SPACE
fi
fi
[ $LAX_DEBUG ] && echo "Available space: $AVAIL_SPACE blocks"
[/CODE]
I believe its the problem of the shell.The error message appears when the installer is executed in bash and sh, it does not come up in ksh.
Thanks
Vikz
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 09, 2009
04:45 AM
You can try and to submit a bug report, if you want!
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)