Re: NIS stealing low-numbered ports?

2003-08-20 Thread Eric van Gyzen
Aaron,

I am having similar trouble with 5.1.  For me, rpc.lockd is eating up 
all my low (privileged) udp ports.  You can tell the system to use a 
different range for low ports.  Use the sysctl command and tweak the 
net.inet.ip.portrange.lowlast variable.  By default, it sets the 
lower bound for privileged ports to 600.  You might increase it past 
631 to ensure that no process snatches it up.  Of course, you would 
have fewer privileged ports, which might create problems on a busy 
machine running NIS (which is the situtation that brought this 
problem to my attention).

Cheers,
Eric

Aaron Mandel wrote:
> I'm running 4.7, using both NIS and cups. There has now twice been a
> problem where printing via cups started failing because cups
> couldn't open UDP port 631 to talk to the cups server, and both
> times, when I looked, there was an sshd belonging to some random
> (logged-in) user claiming that port. I found a short thread in the
> list archives from a few months ago saying that this was normal
> behavior with NIS, but shouldn't it be taking higher-numbered ports?
> The range of ports it uses seems to be about 600-1024; if there's a
> way to configure those numbers, we haven't found it.
> 
> Has anyone else had this problem and found a satisfactory solution?

-- 
Eric van GyzenSr. Systems Programmer
http://www.stat.duke.edu/~vangyzen/   ISDS, Duke University

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


NIS stealing low-numbered ports?

2003-08-10 Thread Aaron Mandel
I'm running 4.7, using both NIS and cups. There has now twice been a
problem where printing via cups started failing because cups couldn't open
UDP port 631 to talk to the cups server, and both times, when I looked,
there was an sshd belonging to some random (logged-in) user claiming that
port. I found a short thread in the list archives from a few months ago
saying that this was normal behavior with NIS, but shouldn't it be taking
higher-numbered ports? The range of ports it uses seems to be about
600-1024; if there's a way to configure those numbers, we haven't found
it.

Has anyone else had this problem and found a satisfactory solution?

aaron
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"