555 The netgroup \fBmemberTriples\fR can have format \fB(host, user, domain)\fR or
 556 \fBgroupname\fR. The format is specified by the attribute:
 557 .sp
 558 .in +2
 559 .nf
 560 nisLDAPsplitField memberTriple: \e
 561       ("(%s,%s,%s)", host, user, domain) , \e
 562       ("%s", group)
 563 .fi
 564 .in -2
 565 
 566 Later operations can then use field names \fBhost\fR, \fBuser\fR, \fBdomain\fR,
 567 \fBgroup\fR or \fBmemberTriple\fR. Because lines are processed in order, if
 568 \fBhost\fR, \fBuser\fR and \fBdomain\fR are found, \fBgroup\fR will not be
 569 generated.
 570 .sp
 571 Several maps and databaseIds may contain fields that are to be split in the
 572 same way. As a consequence, the names of fields to be split must be unique
 573 across all maps and databaseIds.
 574 .sp
 575 Only one level of spliting is supported.That is, a subfield cannot be split
 576 into further subfields.
 577 .RE
 578 
 579 .sp
 580 .ne 2
 581 .na
 582 \fB\fBnisLDAPrepeatedFieldSeparators\fR\fR
 583 .ad
 584 .sp .6
 585 .RS 4n
 586 Where there is a list of repeated, splitable fields,
 587 \fBnisLDAPrepeatedFieldSeparators\fR specifies which characters separate
 588 instances of the splitable field.
 589 .sp
 590 The syntax for the \fBnisLDAPrepeatedFieldSeparators\fR attribute is as
 591 follows:
 592 .sp
 593 .in +2
 594 .nf
 595 "nisLDAPrepeatedFieldSeparators" fieldName \e"sepChar[...]\e"
 596 sepChar = A separator character.
 597 .fi
 598 .in -2
 599 
 600 The default value is space or tab. If repeated splitable fields are adjacent,
 601 that is, there is no separating character, then the following should be
 602 specified:
 603 .sp
 604 .in +2
 605 .nf
 606 nisLDAPrepeatedFieldSeparators netIdEntry: ""
 607 .fi
 608 .in -2
 609 
 610 .RE
 611 
 612 .sp
 613 .ne 2
 614 .na
 615 \fB\fBnisLDAPcommentChar\fR\fR
 616 .ad
 617 .sp .6
 618 .RS 4n
 619 Specifies which character represents the start of the special comment field in
 620 a given NIS map. If this attribute is not present then the default comment

 555 The netgroup \fBmemberTriples\fR can have format \fB(host, user, domain)\fR or
 556 \fBgroupname\fR. The format is specified by the attribute:
 557 .sp
 558 .in +2
 559 .nf
 560 nisLDAPsplitField memberTriple: \e
 561       ("(%s,%s,%s)", host, user, domain) , \e
 562       ("%s", group)
 563 .fi
 564 .in -2
 565 
 566 Later operations can then use field names \fBhost\fR, \fBuser\fR, \fBdomain\fR,
 567 \fBgroup\fR or \fBmemberTriple\fR. Because lines are processed in order, if
 568 \fBhost\fR, \fBuser\fR and \fBdomain\fR are found, \fBgroup\fR will not be
 569 generated.
 570 .sp
 571 Several maps and databaseIds may contain fields that are to be split in the
 572 same way. As a consequence, the names of fields to be split must be unique
 573 across all maps and databaseIds.
 574 .sp
 575 Only one level of splitting is supported. That is, a subfield cannot be split
 576 into further subfields.
 577 .RE
 578 
 579 .sp
 580 .ne 2
 581 .na
 582 \fB\fBnisLDAPrepeatedFieldSeparators\fR\fR
 583 .ad
 584 .sp .6
 585 .RS 4n
 586 Where there is a list of repeated, splittable fields,
 587 \fBnisLDAPrepeatedFieldSeparators\fR specifies which characters separate
 588 instances of the splittable field.
 589 .sp
 590 The syntax for the \fBnisLDAPrepeatedFieldSeparators\fR attribute is as
 591 follows:
 592 .sp
 593 .in +2
 594 .nf
 595 "nisLDAPrepeatedFieldSeparators" fieldName \e"sepChar[...]\e"
 596 sepChar = A separator character.
 597 .fi
 598 .in -2
 599 
 600 The default value is space or tab. If repeated splittable fields are adjacent,
 601 that is, there is no separating character, then the following should be
 602 specified:
 603 .sp
 604 .in +2
 605 .nf
 606 nisLDAPrepeatedFieldSeparators netIdEntry: ""
 607 .fi
 608 .in -2
 609 
 610 .RE
 611 
 612 .sp
 613 .ne 2
 614 .na
 615 \fB\fBnisLDAPcommentChar\fR\fR
 616 .ad
 617 .sp .6
 618 .RS 4n
 619 Specifies which character represents the start of the special comment field in
 620 a given NIS map. If this attribute is not present then the default comment