In some client/server relationships where they only run on one specific
machine the server opens a port internally for the client to connect to.
This does not necessarily mean these ports are accessible from outside I
don't think. One has to remember that the client/server relationship is
not exclusive to programs that use networks or the internet to
communicate.
Maybe someone else has another spin on this or, if Gnome is the
*cuplprit*, there may be something in the Gnome documentation.
Ken Wilson
First Law of Optimization: The speed of a nonworking program is
irrelevant
(Steve Heller, 'Efficient C/C++ Programming')
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Justin Fisher
> Sent: Friday, August 27, 1999 11:30 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [newbie] Im listening on some wierd tcp ports..
>
>
> Okay, wierd, they are in use by GNOME's panel and other panel
> applets...
> why do they listen on a port that accepts connections from
> anything? and
> why do they need to listen at all.. hmm i guess its like remotely
> configureable or something maybe. Somebody know?
>
> Justin Fisher: [EMAIL PROTECTED]
>
> On Thu, 26 Aug 1999, Axalon Bloodstone wrote:
>
> >
> > lsof -i
> >
> > On Thu, 26 Aug 1999, Justin Fisher wrote:
> >
> > > a piece of `netstat -a`
> > >
> > > tcp 0 0 *:3446 *:*
> LISTEN
> > > tcp 0 0 *:3384 *:*
> LISTEN
> > > tcp 0 0 *:3380 *:*
> LISTEN
> > > tcp 0 0 *:3379 *:*
> LISTEN
> > > tcp 0 0 *:3378 *:*
> LISTEN
> > > tcp 0 0 *:3377 *:*
> LISTEN
> > >
> > >
> > > Whats on those???
> > >
> > > Justin Fisher: [EMAIL PROTECTED]
> > >
> > >
> >
> > --
> > MandrakeSoft http://www.mandrakesoft.com/
> > --Axalon
> >
>
