1nischown(1)                      User Commands                     nischown(1)
2
3
4

NAME

6       nischown - change the owner of a NIS+ object
7

SYNOPSIS

9       nischown [-AfLP] owner name...
10
11

DESCRIPTION

13       nischown  changes the owner of the NIS+ objects or entries specified by
14       name to owner. Entries are specified  using  indexed  names  (see  nis‐
15       match(1)).  If owner is not a fully qualified  NIS+ principal name (see
16       nisaddcred(1M)),  the  default  domain  (see  nisdefaults(1))  will  be
17       appended to it.
18
19
20       The  only  restriction  on  changing an object's owner is that you must
21       have modify permissions for the object. Note: If you  are  the  current
22       owner  of  an  object and you change ownership,  you may not be able to
23       regain ownership unless you have modify access to  the new object.
24
25
26       The command will fail if the master NIS+ server is not running.
27
28
29       The  NIS+ server will check the validity of the name before making  the
30       modification.
31

OPTIONS

33       The following options are supported:
34
35       -A    Modify  all  entries in all tables in the concatenation path that
36             match the search criteria specified in name. It  implies  the  -P
37             option.
38
39
40       -f    Force the operation and fail silently if it does not succeed.
41
42
43       -L    Follow links and change the owner of the linked object or entries
44             rather than the owner of the link itself.
45
46
47       -P    Follow the concatenation path within a named table.  This  option
48             is  only meaningful when either name is an indexed name or the -L
49             option is also specified and the named object is a link  pointing
50             to entries.
51
52

EXAMPLES

54       Example 1 Using the nischown Command
55
56
57       The following two examples show how to change the owner of an object to
58       a principal in a different domain, and to change it to a  principal  in
59       the local domain, respectively.
60
61
62         example% nischown bob.remote.domain. object
63         example% nischown skippy object
64
65
66
67
68       The  next  example  shows  how  to  change the owner of an entry in the
69       passwd table.
70
71
72         example% nischown bob.remote.domain. '[uid=99],passwd.org_dir'
73
74
75
76
77       This example shows how to change the object or entries pointed to by  a
78       link.
79
80
81         example% nischown -L skippy linkname
82
83
84

ENVIRONMENT VARIABLES

86       NIS_PATH     If  this  variable  is set, and the NIS+ name is not fully
87                    qualified, each directory specified will be searched until
88                    the object is found (see nisdefaults(1)).
89
90

EXIT STATUS

92       The following exit values are returned:
93
94       0    Successful operation.
95
96
97       1    Operation failed.
98
99

ATTRIBUTES

101       See attributes(5) for descriptions of the following attributes:
102
103
104
105
106       ┌─────────────────────────────┬─────────────────────────────┐
107       │      ATTRIBUTE TYPE         │      ATTRIBUTE VALUE        │
108       ├─────────────────────────────┼─────────────────────────────┤
109       │Availability                 │SUNWnisu                     │
110       └─────────────────────────────┴─────────────────────────────┘
111

SEE ALSO

113       NIS+(1), nischgrp(1), nischmod(1), nischttl(1), nisdefaults(1), nisadd‐
114       cred(1M), nismatch(1), nis_objects(3NSL), attributes(5)
115

NOTES

117       NIS+ might not be supported in future releases of the Solaris operating
118       system.  Tools  to aid the migration from NIS+ to LDAP are available in
119       the   current   Solaris   release.   For   more   information,    visit
120       http://www.sun.com/directory/nisplus/transition.html.
121
122
123
124SunOS 5.11                        2 Dec 2005                       nischown(1)
Impressum