Installation guide

2: Server-Resident Application Software Development
DC 900-1325I 41
When the Freeway reboots, the rc.startsra file will be copied to the /tmp/boot directory
and executed after the
bootcfg file is processed.
Rather than use the vi editor, you may also create the rc.startsra file on your PC, then
transfer it to the Freeway disk drive. Refer to Section 4.2.1 on page 59 for further infor-
mation on this method.
2.7.2 Secondary SRA Startup File (rc.startsra.local)
If the rc.startsra file already exists in the /tmp/boot directory, it may be because there is
already an SRA running on your system (for example: the Protogate Monitor SRA). In
this case you may simply edit the existing
rc.startsra file and place the commands for
starting your SRA (from Section 2.7.1) at an appropriate place near the end of the file.
However, if you receive later updates to the existing SRA, the updates may overwrite the
existing
rc.startsra file and your added commands will be deleted.
To prevent this from happening, you can place your SRA start commands in a file
named
rc.startsra.local. Protogate adds commands in the rc.startsra files it distributes to
also check for “local” command files of the form
rc.startsra.local*. This is done specifi-
cally so that your added SRA commands will not get deleted by future updates of Pro-
togate SRAs.
Look at the existing rc.startsra file to see what local files it calls. Figure 2–1 shows an
example of a Protogate
rc.startsra file. In this example, there are two locations in the file
where local startsra files are executed. The file
rc.startsra.local is executed near the start of
the file, and
rc.startsra.local2 is executed near the end of the file. Using this example, you
could put your SRA startup commands in the file rc.startsra.local or in
rc.startsra.local2
depending on when you want to start your SRA relative to the other commands within
the main
rc.startsra file.