help-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Even more information on gdnc


From: Birch Browning
Subject: Even more information on gdnc
Date: Tue, 29 Aug 2006 20:52:22 -0700 (PDT)

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. ;-)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]