|
|
Once an application is installed under OKP, use the openserver(1) command to run it. Applications running under OKP can be debugged using a special version of the UnixWare 7 truss command, osrtruss(1).
There are a number of methods for installing OpenServer applications under OKP:
Use the openserver(1) command to run OpenServer applications under OKP.
To enter the OKP environment and run an application from the command line, you would typically enter a series of commands like the following:
$ openserver [openserver] cd application_path [openserver] ./command arg...where application_path is the path to the application's startup directory, and command is the name of the command that starts the application. Using openserver in this manner launches an OpenServer shell with an OpenServer execution environment. For example, when you execute the man command at the [openserver] prompt, you are accessing the OpenServer man command and manual pages.
Another way to do launch an OpenServer application is to remain in UnixWare mode, change directory to where the application executable is located, and execute openserver as follows:
cd /openserver/application_path openserver ./command arg...
This method is intended primarily for use in OpenServer application startup scripts, and (UnixWare) system startup scripts that launch OpenServer applications when the system boots.
To start your OKP applications automatically on boot, create a startup script in /etc/init.d that runs the required commands, as in the example above. (Your application may require additonal commands specific to the application.) Place a link to the script in /etc/rc2.d, following the naming convention described on the rc2(1M) manual page.
Some applications may experience minor problems, due to implementation differences between UnixWare 7 and OpenServer 5. Use the information in this chapter to debug your application, and see Porting, integration, and compatibility in the Development Kit documentation for compatibility and porting information.
The first step in resolving such problems is to check the information in ``OKP Limitations'' to see if your application is using facilities that are not supported under OKP.
The following sections provide information about identifying and resolving some of the most common issues that can occur.
The osrtruss(1) utility is used to trace system calls and signals in OpenServer applications. See the osrtruss(1) manual page for how to use osrtruss under OKP. To run an application under osrtruss from a UnixWare shell:
cd /openserver/<app_path> osrtruss -f [truss_options] openserver "./myapp arg1 arg2 ..."
Note the following:
If your application has problems detecting your System Type, System Release, or executing installation and/or shell scripts, it may be due to a file that is not present on your system. Try copying the appropriate file from an OpenServer system. If you do not have one available, see the manual pages for OpenServer at the Product Documentation web site for a description of the file and try to re-create the file yourself in the appropriate location under /openserver.
Though uncommon, if the application fails while kernel tunable parameters are being set, try setting the equivalent UnixWare 7 tunable parameters by hand and then installing or running the application again. For information about UnixWare 7 tunable parameters, see Tunable Parameters.
If your application is a console or ``character-based'' application, it is likely to execute correctly under OKP. If not, try setting the poll_delay_compatibility tunable to change what happens for OpenServer binaries that poll with zero timeout.