lgy@phys.washington.edu (Laurence G. Yaffe) (04/05/91)
The man page describing the syntax of the /etc/netgroup file is less than precise. Is there any standard way to break long entries across multiple lines? Experimentation (with RISCos 4.52) suggests that \<NEWLINE> is ignored when a netgroup is used by exportfs (i.e., a netgroup name appears in /etc/exports), but this does not seem to be true when netgroups are used (with NIS) in the password file (i.e., +@group entries). -- -------------------------------------------------------------------------- Laurence G. Yaffe Internet: lgy@newton.phys.washington.edu University of Washington Bitnet: yaffe@uwaphast.bitnet
trevc@moosehead.mips.com (Trevor Cotton) (04/06/91)
In article <lgy.670797538@newton>, lgy@phys.washington.edu (Laurence G. Yaffe) writes: > > The man page describing the syntax of the /etc/netgroup file is less > than precise. Is there any standard way to break long entries across > multiple lines? Experimentation (with RISCos 4.52) suggests that \<NEWLINE> > is ignored when a netgroup is used by exportfs (i.e., a netgroup name > appears in /etc/exports), but this does not seem to be true when netgroups > are used (with NIS) in the password file (i.e., +@group entries). > > -- > -------------------------------------------------------------------------- > Laurence G. Yaffe Internet: lgy@newton.phys.washington.edu > University of Washington Bitnet: yaffe@uwaphast.bitnet If you have vis.conf setup to use files to resolve netgroups, then the following applies 1) An entry has to be on one line. The \ character is not valid ( because the code uses fgets to read in each line ) 2) After the group name, the rest of the line can only contain (host,user,domain) triplets. Names of other groups are not allowed. 3) The maximum length of a line is 4096 characters. If vis.conf is set up to use NIS ( YP ) to resolve netgroups, and hence the makedbm command is used to convert the /etc/netgroups file, then 1) the \ character is valid 2) A netgroup entry can contain the name of another group as well as (host,user,domain) triplets. So, either use NIS or use a number of smaller groups, and export to multiple groups. There is an open bug on this one( bug 8355 ). --trevc--
marc@watson.ibm.com (Marc Auslander) (04/08/91)
We make extra groups - that is: biggroup1 (... biggroup2 (... ... biggroup biggroup1 biggroup2 ... -- Marc Auslander <marc@ibm.com>