From: Andrew Kelly <akelly@transparency.org>
To: "linux-admin@vger.kernel.org" <linux-admin@vger.kernel.org>
Subject: Re: kdm listening on port 1024
Date: Wed, 09 Jul 2003 08:25:10 +0200 [thread overview]
Message-ID: <3F0BB546.49407284@transparency.org> (raw)
In-Reply-To: 20030708190038.GA1697@gudu.dominio1.net
Hi César,
César Soler wrote:
>
> On Tue, Jul 08, 2003 at 12:48:31PM +0200, Andrew Kelly wrote:
> > Hi all,
> >
> > forgive my confusion, but, why would kdm have port 1024 open
> > on a box that isn't running X?
>
> Hi Andrew,
>
> I have checked it is opened too in my RH 8.0 and there it is listening the
> rpc.statd process:
>
> [root@gudu root]# lsof -i | grep -i listen | grep 1024
> rpc.statd 429 rpcuser 6u IPv4 864 TCP *:1024 (LISTEN)
>
> are you sure that port 1024 is owned by kdm?
nmap localhost shows
1024/tcp open kdm
but you're right. lsof -i says
rpc.statd 529 root 5u IPv4 794 UDP *:1024
rpc.statd 529 root 6u IPv4 797 TCP *:1024 (LISTEN)
Thank you, César, that helps. I don't know why nfs
would show up as a desktop manager, but there you go.
nfslock was running and when I shut it down, port 1024
closed.
> hope this help...
Very much, yes. Thank you.
Andy
> Best regards
> -
> César Soler <csoler@euskalnet.net> PGP KeyID: 0x179DAD53
>
> No des la felicidad de muchos años por el riesgo de una hora.
> -- Livio.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2003-07-09 6:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-08 10:48 kdm listening on port 1024 Andrew Kelly
2003-07-08 19:00 ` César Soler
2003-07-09 6:25 ` Andrew Kelly [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F0BB546.49407284@transparency.org \
--to=akelly@transparency.org \
--cc=linux-admin@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).