[OpenIndiana-discuss] rpc/bind service manifest

[Marcel Telka]

On Fri, Jan 25, 2013 at 10:49:35AM +0100, real-men-dont-click at gmx.net wrote:
> -----Original message-----
> From:	Marcel Telka <marcel at telka.sk>
> Sent:	Fri 25-01-2013 10:29
> Subject:	Re: [OpenIndiana-discuss] rpc/bind service manifest
> To:	Discussion list for OpenIndiana <openindiana-discuss at openindiana.org>; 
> > On Fri, Jan 25, 2013 at 10:19:18AM +0100, real-men-dont-click at gmx.net wrote:
> > > Hello everybody,
> > > 
> > > we spend some time last night to bring up the NIS service on an OI 151a7 
> > installation. We had severe difficulties to connect the slave servers and ended 
> > up snooping the interface....
> > > 
> > > To make a long story short, the service is configured to only listen locally 
> > (strange for a RemoteProcedureCall service, isn't it)
> > > 
> > > The solution was to adjust the service manifest of network/rpc/bind 
> > accordingly:
> > > 
> > > change
> > > 
> > > <propval name='local_only' type='boolean' value='true'/>
> > > 
> > > to
> > > 
> > > <propval name='local_only' type='boolean' value='false'/>
> > > 
> > > 
> > > Perhaps the default setting should be changed.....
> > 
> > Hi,
> > 
> > I'd say the NIS service should do something similar as the nlockmgr does:
> > http://src.illumos.org/source/xref/illumos-gate/usr/src/cmd/fs.d/nfs/svc/nlockmg
> > r
> > 
> > I think the local_only is set to true by default because "secure by default"
> > approach.
> > 
> 
> 
> Marcel,
> 
> I think you're right. Changing the property automatically when NIS is
> installed/enabled would indeed be the best option..

Feel free to implement it. Contribution is always welcome :).

-- 
+-------------------------------------------+
| Marcel Telka   e-mail:   marcel at telka.sk  |
|                homepage: http://telka.sk/ |
|                jabber:   marcel at jabber.sk |
+-------------------------------------------+