To improve performance and prevent network issues, you
must run the Name Service Caching Daemon. To ensure your servers are
properly synchronized, you should also run the Network Time Protocol
daemon.
About this task
Comprehensive information about completing the operating
system preparation may be found in the WebSphere® Application Server
Network Deployment information center.
The Name Service Caching Daemon must
be started on each Linux server where you plan to deploy WebSphere Telecom Web Services
Server components.
- Use grep to determine if the Name
Service Caching Daemon is running. For example:
ps -elf | grep "nscd"
- If it is not running, start it.
- Change to the /etc/init.d directory. For
example:
cd /etc/init.d
- Run nscd. For example:
./nscd start
- To configure the Name Service Caching Daemon
to start when the system is started, update rcdefault_runlevel.d.
- To determine the default_runlevel, observe /etc//inittabn. You will see the following:
id:5:initdefault:
# System initialization.
si::sysinit:/etc/rc.d/rc.sysinit
The first line
indicates that the default runlevel is 5.
- To update rc5.d, do the following:
cd /etc/rc.d/rc5.d
ln -s ../init.d/nscd S60nscd
ln -s ../init.d/nscd K60nscd
- Ensure that the Network Time Protocol daemon is configured
and running.