|
Hi, I have logged a bug in http://bugzilla.redhat.com:
[Bug 171639] New: ypserv specific port binding fail with -p option
Can you guys reproduce this bug?
Details:
I want to assign ypserv a specifc port when started and thus make it easier
to use NIS in a firewalled environment. By assigning specific port, I can open
this port permenently on my firewall. Otherwise, I have to add the port every
time on my firewall's trusted ports after ypserv is restarted.
I am using RHEL 4.0 with ypserv 2.13.5. The man page of ypserv says:
-p --port port
ypserv will bind itself to this port. This makes it possible
to have a router filter packets to the NIS ports, so that
access to the NIS server from hosts on the Internet can be
restricted.
I tried the "-p port" option, but it failed to assign ypserv a specific port.
1. start ypserv with -p option at startup to specify the port:
/etc/init.d/ypserv start -p 1000
or
1. edit /etc/init.d/ypserv file and add "-p 1000" in the "start" section.
2. run "rpcinfo -p localhost" to check, it seems ypserv always receives a random port from portmap.
Can anyone try this on your machine? I want to make sure it doesn't only happen to me  |
|