[unix-history] / share / doc / usd / 11.notes / 4.7

.\" Copyright (c) 1980 The Regents of the University of California.
.\" All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\" 1. Redistributions of source code must retain the above copyright
.\"    notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\"    notice, this list of conditions and the following disclaimer in the
.\"    documentation and/or other materials provided with the distribution.
.\" 3. All advertising materials mentioning features or use of this software
.\"    must display the following acknowledgement:
.\"	This product includes software developed by the University of
.\"	California, Berkeley and its contributors.
.\" 4. Neither the name of the University nor the names of its contributors
.\"    may be used to endorse or promote products derived from this software
.\"    without specific prior written permission.
.\"
.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE.
.\"
.\"	from: @(#)4.7	6.2 (Berkeley) 4/17/91
.\"	4.7,v 1.2 1993/08/01 07:37:23 mycroft Exp
.\"
.se "Modifying Access Rights for Many Notesfiles"

	It is convenient to add entries to a large number of
access lists simultaneously.
The nfaccess program adds an access specification to each of
a specified list of notesfiles.
Nfaccess functions similarly to chmod(1).
Nfaccess is invoked as:

	nfaccess <access-right> notesfile [notesfile ...]

The ``access-right'' is formatted as: ``type:name=mode''.
Type can be any of ``user'', ``group'', or ``system'';
capitalized variants are also valid.
The ``type:'' specification can be omitted.
``User'' is assumed in these cases.
The ``mode'' field consists of a sequence of the
characters ``d'', ``r'', ``w'', ``a'' and ``n''.
These indicate director, read, write, answer (respond) and null
access respectively.

	Nfaccess requires user and group entries to be valid
by looking for them in /etc/passwd and /etc/group.
System entries are not checked for validity.
Nfaccess will add the entry to the access list of the specified
notesfiles.
If an entry for that particular user, group or system exists,
the new access right replaces the old access rights.
The computed mode is an absolute mode; the previous value in
the access list (if any) is replaced with the new mode.

	Any user can run the nfaccess program.
Nfaccess refuses to modify access lists for any notesfile
where the user is not a director.
The nfaccess program is stored in the notesfile utility
directory, typically ``/usr/spool/notes/.utilities''.

	Nfaccess is often used to remedy missing permissions
in a number of notesfiles.
One example is when the notesfile administrator is replaced;
nfaccess is used to grant director access to the appropriate
notesfiles (usually most of them).
As new notesfiles are created, the access list can be tuned
by placing lists of access-rights in the file
``/usr/spool/notes/.utilities/access-template''.
These access-rights are added to the default access list
of newly created notesfiles.
Commit	Line	Data
15637ed4 RG	1	.\" Copyright (c) 1980 The Regents of the University of California.
	2	.\" All rights reserved.
	3	.\"
	4	.\" Redistribution and use in source and binary forms, with or without
	5	.\" modification, are permitted provided that the following conditions
	6	.\" are met:
	7	.\" 1. Redistributions of source code must retain the above copyright
	8	.\" notice, this list of conditions and the following disclaimer.
	9	.\" 2. Redistributions in binary form must reproduce the above copyright
	10	.\" notice, this list of conditions and the following disclaimer in the
	11	.\" documentation and/or other materials provided with the distribution.
	12	.\" 3. All advertising materials mentioning features or use of this software
	13	.\" must display the following acknowledgement:
	14	.\" This product includes software developed by the University of
	15	.\" California, Berkeley and its contributors.
	16	.\" 4. Neither the name of the University nor the names of its contributors
	17	.\" may be used to endorse or promote products derived from this software
	18	.\" without specific prior written permission.
	19	.\"
	20	.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
	21	.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
	22	.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
	23	.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
	24	.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
	25	.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
	26	.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
	27	.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
	28	.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
	29	.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
	30	.\" SUCH DAMAGE.
	31	.\"
78ed81a3	32	.\" from: @(#)4.7 6.2 (Berkeley) 4/17/91
78ed81a3	33	.\" 4.7,v 1.2 1993/08/01 07:37:23 mycroft Exp
15637ed4 RG	34	.\"
	35	.se "Modifying Access Rights for Many Notesfiles"
	36
	37	It is convenient to add entries to a large number of
	38	access lists simultaneously.
	39	The nfaccess program adds an access specification to each of
	40	a specified list of notesfiles.
	41	Nfaccess functions similarly to chmod(1).
	42	Nfaccess is invoked as:
	43
	44	nfaccess <access-right> notesfile [notesfile ...]
	45
	46	The ``access-right'' is formatted as: ``type:name=mode''.
	47	Type can be any of ``user'', ``group'', or ``system'';
	48	capitalized variants are also valid.
	49	The ``type:'' specification can be omitted.
	50	``User'' is assumed in these cases.
	51	The ``mode'' field consists of a sequence of the
	52	characters ``d'', ``r'', ``w'', ``a'' and ``n''.
	53	These indicate director, read, write, answer (respond) and null
	54	access respectively.
	55
	56	Nfaccess requires user and group entries to be valid
	57	by looking for them in /etc/passwd and /etc/group.
	58	System entries are not checked for validity.
	59	Nfaccess will add the entry to the access list of the specified
	60	notesfiles.
	61	If an entry for that particular user, group or system exists,
	62	the new access right replaces the old access rights.
	63	The computed mode is an absolute mode; the previous value in
	64	the access list (if any) is replaced with the new mode.
	65
	66	Any user can run the nfaccess program.
	67	Nfaccess refuses to modify access lists for any notesfile
	68	where the user is not a director.
	69	The nfaccess program is stored in the notesfile utility
	70	directory, typically ``/usr/spool/notes/.utilities''.
	71
	72	Nfaccess is often used to remedy missing permissions
	73	in a number of notesfiles.
	74	One example is when the notesfile administrator is replaced;
	75	nfaccess is used to grant director access to the appropriate
	76	notesfiles (usually most of them).
	77	As new notesfiles are created, the access list can be tuned
	78	by placing lists of access-rights in the file
	79	``/usr/spool/notes/.utilities/access-template''.
	80	These access-rights are added to the default access list
	81	of newly created notesfiles.