On Mon, May 30, 2011 at 04:56:02PM -0400, Rick Macklem wrote: > Hi, > > I have patches for the mountd, rpc.statd and rpc.lockd daemons > that are meant to keep them from failing when a dynamically > selected port# is not available for some combination of > udp,tcp X ipv4,ipv6 > > If anyone would like to test these patches, they can be found > at: > http://people.freebsd.org/~rmacklem/mountd.patch > statd.patch > lockd.patch > > Although I think I got them correct, they are rather big and ugly. >
I have checked this update for mountd in 10-CURRENT and has two questions: 1. What is the sense to try to use the same port number for all supported netconfigs if specific port number is not given in a command line option? 2. What is the sense of specifying specific IP addresses for mountd and similar RPC programs that do not have predefined port numbers? ---------- One comment for netconfig related functions usage. Each setnetconfig() call allocates memory and depending on implementation can use other resources, so endnetconfig() should be called before reusing netconfig handle. _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
