Re: Gnome and WM

[Desync <desync nwlink com>]

The applets (or is it the panel?) are also binding sockets to listen on. 

Is this something that will be changed, or is it just something to do
with my configuration of GNOME at compile?

I hope it will change. I found that I was able to crash the panel
entirely (remotely) by connecting to those ports and flooding it.

Using firewalls would not help, since it seems to use the normal
convention of binding the next availble port (in sequential order) so
guessing the ports to firewall would be impossible.



Christopher Seawood wrote:
> 
> On Thu, 18 Jun 1998, kluster wrote:
> 
> > How can I use windowmaker and gnome?  I have tried adding this to my
> > .xinitrc (which consisted only of exec wmaker):
> >
> > background-properties --init &
> > keyboard-properties --init &
> > mouse-properties --init &
> > panel &
> > exec wmaker
> >
> > But I don't get the gnome taskbar and get an error:
> >
> > **Could not communicate with panel
> >
> 
> A friend ran into a similar problem earlier this week.  He claims that
> adding the name of the local machine to your /etc/hosts file fixes the
> problem. Apparently, mico checks to see if your hostname, as returned by
> `hostname`, is in /etc/hosts and croaks if it's not.
> 
> - cls
> 
> --
>          To unsubscribe: mail gnome-list-request@gnome.org with
>                        "unsubscribe" as the Subject.