|
From: | Richard Frith-Macdonald |
Subject: | [bug #13899] gnustep-base-1.11.0 gdnc doesn't register to gdomap |
Date: | Sat, 23 Jul 2005 17:57:55 +0000 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050517 Firefox/1.0.4 (Debian package 1.0.4-2) |
Update of bug #13899 (project gnustep): Item Group: Bug => Documentation _______________________________________________________ Follow-up Comment #1: I think this is a query rather than a bug report ... Distributed notifications and the gdnc server now use message ports by default. That means gdnc needs to be started as the user, not as system. It also means that it should not show up in gdomap as it's no longer using socket ports (gdomap gives the names of socket ports). Other things which have not moved over to explicitly selecting message/socket based connections will generate a warning message until the next base release at which the default behavior for all connections will change. To suppress the warning message you need to do set the NSPortIsMessagePort as suggested in the warning message. eg. defaults write NSGlobalDomain NSPortIsMessagePort YES _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?func=detailitem&item_id=13899> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |