for root to accept netgroups would be really convenient, but NetApp said this would be fair sized performance hit. We got them to allow subnet entries into the root access list, which has proven to be workable for us.
At 8:12 AM -0500 4/12/02, Mike Carroll wrote:
I would love to see this fixed, or changed to function like this as well....
-----Original Message----- From: Chris Blackmor [mailto:chris.blackmor@amd.com] Sent: Thursday, April 11, 2002 8:55 AM To: Frank Bonnet Cc: toasters@mathworks.com Subject: Re: local netgroup ?
Frank, I don't know about local netgroups anymore (got away from those a very long time ago). We do use NIS netgroups in our exports for the access= however we are still specifying hosts in the root= and the rw=.
Does anyone know if the root= and rw= will be accepting netgroups? We tried to get this to work a few months ago and it didn't. Last night I spent quite some time auditing the exports file on all 22 of our filers (each with more than 10 lines) and the root=/rw= were what took the bulk of the time.
C-
On Thu, Apr 11, 2002 at 11:36:36AM +0200, Frank Bonnet wrote:
Hi
Is it possible to use a local netgroup file instead of the NIS netgroup map on a filer ( ontap 6.1.2R2 ). I have too much hosts to put in /etc/exports file
-- Frank Bonnet
--
- Chris Blackmor _______ |
- Advanced Micro Devices ____ | | A good horse never comes
- Phone: (512) 602-1608 /| | | | in a bad color!
- Fax: (512) 602-5155 | |___| | |
- Email: chris.blackmor@amd.com |____/ | | Author
Unknown*
My comments are mine, and mine alone.
----------------------------------------- (on Chiaro SMTP Relay)
This e-mail and any files transmitted with it are the property of Chiaro Networks, Ltd., and may contain confidential and privileged material for the sole use of the intended recipient(s) to whom this e-mail is addressed. If you are not one of the named recipient(s), or otherwise have reason to believe that you have received this message in error, please notify the sender and delete all copies from your system. Any other use, retention, dissemination, forwarding, printing or copying of this e-mail is strictly prohibited.