next up previous contents
Next: D. Configuring ossie.pth Up: OSSIE 0.6.2 User Guide Previous: B. Managing Services on   Contents


C. Creating omniNames.sh

Installing omniORB from RPM automatically starts the naming service when the system boots. If omniORB was not installed using RPM, the naming service will probably need to be started manually. To do so, create a file called omniNames.sh containing the following
 #!/bin/sh
 
 killall omniNames
 rm /sdr/logs/omninames*
 
 omniNames -start -logdir /sdr/logs &

Once this file is created, the file must be given executable permissions:

 $ chmod 755 omniNames.sh
 # cp omniNames.sh /usr/local/bin

Create a directory for the logs:

 $ mkdir /sdr/logs

The script can now be run by executing omniNames.sh in any terminal. You can check to see if omniNames is running by executing:

 $ nameclt list
If the naming service is not running you will see an error something like:
  Unexpected error when trying to narrow the NamingContext.



2008-04-25