https://bugzilla.novell.com/show_bug.cgi?id=637382
https://bugzilla.novell.com/show_bug.cgi?id=637382#c4
Jan Kara changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |ASSIGNED
InfoProvider|jack@novell.com |
--- Comment #4 from Jan Kara 2010-09-09 13:34:17 UTC ---
Hmm, you are right, it's a mess. I just did some experiments with the following
results:
rpc.rquotad looks for a port to use. The names of services it obtains from
getrpcbynumber_r (where a number of RPC service corresponding to quota daemon
is passed) are:
rquotad
rquotaprog
quota
rquota
/etc/services contains neither of these so we just continue telling RPC layer
that it can use any free port number. Thus in your case ports 996/tcp and
994/udp are used. On my machine different port numbers are used.
Clients are still able to connect to the server because they ask the RPC layer
for a connection to a particular RPC service and RPC layer tracks on which port
each service decided to listen).
All in all probably we should add 'quotad' to the list of aliases of the
RQUOTAPROG service or add at least one of alias names (I'd vote for rquotad) to
/etc/services. That should make the situation less confusing.
I'd also leave the port variable unset by default, so that /etc/services are
used if user does not wish otherwise. That would seem like the least surprising
solution.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.