Re: Limiting rpc.lockd to IPv4 only

[christos%zoulas.com@localhost (Christos Zoulas)]

On Aug 12,  8:07am, paul%whooppee.com@localhost (Paul Goyette) wrote:
-- Subject: Re: Limiting rpc.lockd to IPv4 only

| > This changes the semantics that have been traditional for these options.
| > (sshd, named, etc.)
| >
| > -4 forces only ipv4
| > -6 forces only ipv6
| >
| > these flags are mutually exclusive.
| > absence of both means use what's available.
| >
| > I think we should make rpc.lockd behave the same way.
| 
| So, for consistency with nfsd, should we modify lockd to only listen on 
| IPv4 by default, and require explicit option to listen on IPv6?
| 
| This is how nfsd behaves:
| 
|       -6      Listen to IPv6 requests as well as IPv4 requests. If IPv6
|               support is not available, nfsd will silently continue and
|               just use IPv4.
| 

I think it makes sense to have nfsd listen by default to both like everyone
else instead. -6 should mean on 6 and -4 should mean only 4.

christos