if you install gnustep-base, you get a /etc/profile.d/gnustep-4.sh which automatically launches gdnc. i have no idea what this daemon is as i don't actually use gnustep, but autorunning things like this is wrong.
Also spurious instances of the daemon are started if a user logs in with a non-X session (e.g. on the Linux console), and they keep running after the user has logged out.
Wow, that's coming back from gnustep-2.sh. From current version manpage: The gdnc daemon is used by GNUstep programs to send notifications and messages to one another. By default it uses private inter-process com‐ munications accessible only to the curtrent user on the machine on which it is running (where the operating system supports them). Every user needs to have his own instance of gdnc running. While gdnc will be started automatically as soon as it is needed, it is recom‐ mended to start gdnc in a personal login script like ~/.bashrc or ~/.cshrc. Alternatively (if you have no command-line tools which use distributed notifications) you can launch gdnc when your windowing sys‐ tem or the window manager is started. For example, on systems with X11 you can launch gdnc from your .xinitrc script or alternatively - if you are running Window Maker - put it in Window Maker's autostart script. See the GNUstep Build Guide for a sample startup script. A gnustep-base/* update is pending, it would be a good time to fix it there (updating gnustep-make and maybe notify the user in gnustep-base)
Fixed in gnustep-base/gnustep-make-2.6.6 (will be next stable target)
