🚀 go-pugleaf

Hello, TooltalkER,
 
Sometime ago I posted a question regarding my problem while
using Tooltalk File Scoping. 
  
I want to thank Mark Soloway and Frank Greco. They pointed out several 
important places in Tooltalk that might affect the File Scoping 
function, such as "real_path_name" etc.
 
As Mark suggested, I set the environment variable TT_DM_DEBUG=8
and looked at the traced data. I found one of the place that caused
the function fail. In dm_server_svc.C, there is a place hard coded
the file system table as /etc/mtab. However, it is a different file
name in our machine (/etc/mnttab in UNIX SVR4.0 2.0). 
  
Unfortunately, my problem is still not solved. Two program running on
two machine (using file-scoping) still can not pass data to each
other. I noticed when the application startup, the rpc.ttdbserverd
created a directory TT_DB. Is there any way that I can direct the
location that the TT_DB be created? Any environmental variable
should be set? When two app run on the same machine, they work fine
(ie., can pass data to each other). However, if the app try to send data 
to the other app in the OTHER machine, it does not work and after a
few time message_send, the tooltalk hangs (or data queue full?). Kill
the app and re-start the app, the app works again. But, it hangs after
a few times message_send, and so on. (I mean the Toooltalk function
hangs but the application is still running)
  
There are many information in the rpc.ttdbserverd traced data 
(with env TT_DM_DEBUG=8). Does anybody have idea how to interprate
those information? 
  
Kevin Feng
ckf@hover.att.com