Open System Services Management and Operations Guide (G06.30+, H06.08+, J06.03+)

nn
is the processor number of the processor you want the process to run in.
object_file_path
is the OSS pathname for the program object file to be executed as the process.
"$@"
causes any parameters entered for the process to be sent to the process.
1. Place the script file in a special directory you control, secured so that it can be executed by
everyone but not altered by anyone.
2. Add your special directory to the PATH environment variable used to find program files. You
need to do this only the first time you create such a script, provided you always use the same
OSS directory.
Most users use the PATH definition in /etc/profile, so change that file such that your
special directory is searched first.
3. Notify those users that have their own .profile file or otherwise alter the PATH variable
about what you are doing so that they can make comparable changes to their definitions of
PATH.
For example, the following steps change the system to run all C language program compilations
in processor 4:
1. Put the following lines into a file called /usr/local/script/c89:
#! /bin/sh
run -cpu=4 /usr/bin/c89 "$@"
2. Secure the file for only read and execute access by entering:
chmod a=rx /usr/local/script/c89
3. Change the PATH environment variable in /etc/profile to something similar to the
following:
export PATH=/usr/local/script:/bin:/bin/unsupported:
/usr/ucb:/usr/bin
4. Post a broadcast message to users.
Managing OSS Interprocess Communication Facilities
The OSS interprocess communication (IPC) facilities require little management. However, applications
can fail and leave no-longer-used message queues, semaphore IDs, or shared memory segment
IDs in the system. You can detect such wasted resources by regularly monitoring IPC facility use
and correcting the situation when necessary.
OSS IPC facilities such as message queues, semaphores, and shared memory segments can be
monitored and controlled with OSS shell commands. The ipcs command displays information for
those IPC mechanisms. The ipcrm command removes facilities associated with failed processes.
See the ipcs(1) and ipcrm(1) reference pages either online or in the Open System Services
Shell and Utilities Reference Manual.
OSS named pipes (FIFOs) can be monitored using the OSS shell ls -l -F command on the
directory containing the FIFO. The output from the command lists FIFOs with a p as the first character
in the mode field.
OSS AF_UNIX (local) sockets have filenames and can also be watched using the ls -l command.
The output from the command lists AF_UNIX sockets with an s as the first character in the mode
field. OSS AF_UNIX sockets are administered by configuring, starting, and stopping their servers.
See “Managing Servers” (page 90), for information about OSS AF_UNIX sockets local servers.
OSS IPC facilities such as unnamed pipes and OSS AF_INET or AF_INET6 sockets are more
difficult to monitor.
72 Operating the OSS Environment