[Ilugc] ypserv and xinetd problem
- From: sriram@xxxxxxxxxxxxxxxxxx (P. Sriram)
- Date: Mon, 9 Dec 2002 18:16:30 +0530 (IST)
On 9 Dec 2002, Suresh Ramasubramanian wrote:
On Mon, 2002-12-09 at 17:40, P. Sriram wrote:
[about port clashing on ypserv and imaps]
if i reboot the machine, there is a (small?) chance that the same thing
can happen again. this is really a bug, no? is there something specific
you are looking for in the logs?
Just an indication of just why it did so. I can't think of any reason
for ypserv to do this.
there is nothing about this in the logs. the log message looks exactly the
same irrespective of what port ypserv binds to. there should be something
that tells ypserv (or any other rpc fellow) what ports not to use, no? or
is this how portmap works and one just has to live with this? of course,
ypserv can be started on a set port so that this does not happen, but the
default configs dont seem to have this (suggesting it may not be needed).
maybe i have been lucky the last few years, but i have not seen this
happen before. what am i missing?
ps: am posting to group since someone else may throw some light on this
Other related posts: