| |
<font size=3>'''IT IS BEST PRACTICE NOT to double-click''' </font> the installation script, and instead run it from the command line, as the installation script will exit and history will be lost! |
|
<font size=3>'''IT IS BEST PRACTICE NOT to double-click''' </font> the installation script, and instead run it from the command line, as the installation script will exit and history will be lost! |
| |
|
+ |
There are a few options (depending on OS) to help with debugging.
|
| |
|
+ |
The following should be able to work regardless of vendor.
|
| |
|
+ |
Any output from a script/prompt can be redirected to a file. This can be achieved by invoking the ">" key while typing a script to execute. For example, the following will redirect to a file: <pre>install.sh > install.out</pre>
|
| |
|
+ |
= Operating System Specific =
|
| |
|
+ |
The following are specific to each OS.
|
| |
|
+ |
When installing on *nix systems, the '''install.sh''' script should be used as the *.bat file is for Windows installations only. If already in the installer directory, the file needs to be called as '''./install.sh''' as just '''install.sh''' will not execute.
|
| |
|
+ |
The [http://unixhelp.ed.ac.uk/CGI/man-cgi?script man page for script] has more details on '''script''', but basically script will capture every keystroke that is performed within the terminal. It also captures the current screen output. Therefore, you can potentially redirect the entire installation to file as well as any keys you may hit, while also rendering to the screen. After script is invoked and the installation has completed (whether in error or success), type '''<font face="monospace">exit</font>''' to finish the script (which will then be saved to a file). You can then upload the script output to Supportal for further analysis if you wish.
|
