Why does STM report that the networking is not configured correctly?
STM uses sockets to communicate between processes. When networking is incorrectly configured, STM may hang indefinitely. To help users identify this problem, STM incorporates a check to verify that the networking was correctly configured. Unfortunately, this check falsely reports bad configurations in certain cases, including when an ATM network card is the primary LAN connection. This problem was corrected in the IPR 9802 release. On prior releases, the following work-around can be used (alternately, you can update your copy of STM to a more recent version). • Edit file /sbin/init.d/diagnostic (You will need to be logged on as “root” to do so.) • Just above the line “PATH=/sbin:/usr/sbin:/usr/bin” (just below the comments at the top of the file,) add the line: export DONT_CHECK_LAN=1 • Log on as “root”. • Start the diagnostic daemon with the command: /sbin/init.d/diagnostic start • Before starting xstm, mstm or cstm, type: export DONT_CHECK_LAN=1 • After you make the change described
