Even more information on gdnc

Birch Browning <[email protected]>
Newsgroups gmane.comp.lib.gnustep.user
Message-ID <[email protected]>
I've been beating this thing to death. I going to win!

When starting an app using 'openapp Ink --GNU-Debug=NSMessagePort', the relevant lines are:

2006-08-29 22:27:28.381 Ink[8093] portForName: GDNCServer host: 
2006-08-29 22:27:28.381 Ink[8093] _livePort: /tmp/GNUstepSecure0/NSMessagePort/names/GDNCServer
2006-08-29 22:27:28.381 Ink[8093] port is live
2006-08-29 22:27:28.381 Ink[8093] got /tmp/GNUstepSecure0/NSMessagePort/ports/7837.0

When the same command is run as a regular user:

portForName: GDNCServer host: 
2006-08-29 19:51:10.031 Ink[8496] _livePort: /tmp/GNUstepSecure1000/NSMessagePort/names/GDNCServer
2006-08-29 19:51:10.031 Ink[8496] not live, couldn't open file (No such file or directory)
2006-08-29 19:51:10.031 Ink[8496] not a live port

As it turns out, GDNCServer is not writing th relevant info into /tmp/GNUstepSecure1000/NSMessagePort/names or 
/tmp/GNUstepSecure1000/NSMessagePort/ports.

I'm fairly certain it is not a permissions issue on these directories as Ink writes to both ../names and ../ports

This seems to be the crux of the problem. I'd be thrilled if someone would even hypothesize why this is not happening.

Boomer

P.S. I promise to stop writing to the list as soon as this is fixed. ;-)

_______________________________________________
Help-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/help-gnustep
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.