


nisaddent(1M)         Maintenance Commands          nisaddent(1M)



NNNNAAAAMMMMEEEE
     nisaddent - create NIS+ tables from corresponding /etc files
     or NIS maps

SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
     ////uuuussssrrrr////lllliiiibbbb////nnnniiiissss////nnnniiiissssaaaaddddddddeeeennnntttt [ ----DDDD _d_e_f_a_u_l_t_s ] [ ----PPPPaaaarrrrvvvv ]
          [ ----tttt _t_a_b_l_e ] _t_y_p_e [ _n_i_s_d_o_m_a_i_n ]

     ////uuuussssrrrr////lllliiiibbbb////nnnniiiissss////nnnniiiissssaaaaddddddddeeeennnntttt [ ----DDDD _d_e_f_a_u_l_t_s ] [ ----PPPPaaaapppprrrrmmmmvvvv ] ----ffff _f_i_l_e
          [ ----tttt _t_a_b_l_e ] _t_y_p_e [ _n_i_s_d_o_m_a_i_n ]

     ////uuuussssrrrr////lllliiiibbbb////nnnniiiissss////nnnniiiissssaaaaddddddddeeeennnntttt [ ----DDDD _d_e_f_a_u_l_t_s ] [ ----PPPPaaaarrrrmmmmvvvv ]
          [ ----tttt _t_a_b_l_e ] ----yyyy _y_p_d_o_m_a_i_n [ ----YYYY _m_a_p ] _t_y_p_e [ _n_i_s_d_o_m_a_i_n ]

     ////uuuussssrrrr////lllliiiibbbb////nnnniiiissss////nnnniiiissssaaaaddddddddeeeennnntttt ----dddd [[[[----AAAAMMMMqqqq]]]] [ ----tttt _t_a_b_l_e ] _t_y_p_e
          [ _n_i_s_d_o_m_a_i_n ]

DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
     nnnniiiissssaaaaddddddddeeeennnntttt  creates  entries  in  NIS+  tables   from   their
     corresponding  ////eeeettttcccc  files  and NIS maps.  This operation is
     customized for each of the standard tables that are used  in
     the  administration  of  Solaris systems.  The _t_y_p_e argument
     specifies the type  of  the  data  being  processed.   Legal
     values for this type are one of aaaalllliiiiaaaasssseeeessss, bbbboooooooottttppppaaaarrrraaaammmmssss, eeeetttthhhheeeerrrrssss,
     ggggrrrroooouuuupppp, hhhhoooossssttttssss, nnnneeeettttiiiidddd, nnnneeeettttmmmmaaaasssskkkkssss, nnnneeeettttwwwwoooorrrrkkkkssss, ppppaaaasssssssswwwwdddd,  pppprrrroooottttooooccccoooollllssss,
     ppppuuuubbbblllliiiicccckkkkeeeeyyyy,  rrrrppppcccc, sssseeeerrrrvvvviiiicccceeeessss, sssshhhhaaaaddddoooowwww, or ttttiiiimmmmeeeezzzzoooonnnneeee for the stan-
     dard tables, or kkkkeeeeyyyy----vvvvaaaalllluuuueeee for  a  generic  two-column  (key,
     value)  table.  For  a  site specific table, which is not of
     kkkkeeeeyyyy----vvvvaaaalllluuuueeee type, one can use nnnniiiissssttttbbbbllllaaaaddddmmmm(1) to administer it.

     The NIS+ tables should have already been  created  by  nnnniiiisssstttt----
     bbbbllllaaaaddddmmmm(1), nnnniiiisssssssseeeettttuuuupppp(1M), or nnnniiiisssssssseeeerrrrvvvveeeerrrr(1M).

     It is easier to use nnnniiiissssppppooooppppuuuullllaaaatttteeee(1M) instead of nnnniiiissssaaaaddddddddeeeennnntttt  to
     populate the system tables.

     By default, nnnniiiissssaaaaddddddddeeeennnntttt reads from the standard input and adds
     this  data to the NIS+ table associated with the _t_y_p_e speci-
     fied on the command line.  An alternate NIS+  table  may  be
     specified  with  the ----tttt option.  For type kkkkeeeeyyyy----vvvvaaaalllluuuueeee, a table
     specification is required.

     Note that the _d_a_t_a type can be different than the table name
     (----tttt).  For example, the automounter tables have kkkkeeeeyyyy----vvvvaaaalllluuuueeee as
     the table type.

     Although,  there  is  a  _s_h_a_d_o_w  data  type,  there  is   no
     corresponding  _s_h_a_d_o_w table.  Both the shadow and the passwd
     data is stored in the ppppaaaasssssssswwwwdddd table itself.

     Files may be processed using the ----ffff option, and NIS  version
     2 (YP) maps may be processed using the ----yyyy option.  The merge



SunOS 5.4           Last change: 11 May 1995                    1






nisaddent(1M)         Maintenance Commands          nisaddent(1M)



     option is not available  when  reading  data  from  standard
     input.

     When a _y_p_d_o_m_a_i_n is specified, the  nnnniiiissssaaaaddddddddeeeennnntttt  command  takes
     its  input  from  the  ddddbbbbmmmm files for the appropriate NIS map
     (mmmmaaaaiiiillll....aaaalllliiiiaaaasssseeeessss,  bbbboooooooottttppppaaaarrrraaaammmmssss,   eeeetttthhhheeeerrrrssss....bbbbyyyyaaaaddddddddrrrr,   ggggrrrroooouuuupppp....bbbbyyyynnnnaaaammmmeeee,
     hhhhoooossssttttssss....bbbbyyyyaaaaddddddddrrrr,         nnnneeeettttiiiidddd....bbbbyyyynnnnaaaammmmeeee,         nnnneeeettttmmmmaaaasssskkkkssss....bbbbyyyyaaaaddddddddrrrr,
     nnnneeeettttwwwwoooorrrrkkkkssss....bbbbyyyynnnnaaaammmmeeee,      ppppaaaasssssssswwwwdddd....bbbbyyyynnnnaaaammmmeeee,       pppprrrroooottttooooccccoooollllssss....bbbbyyyynnnnaaaammmmeeee,
     ppppuuuubbbblllliiiicccckkkkeeeeyyyy....bbbbyyyynnnnaaaammmmeeee,    rrrrppppcccc....bbbbyyyynnnnuuuummmmbbbbeeeerrrr,    sssseeeerrrrvvvviiiicccceeeessss....bbbbyyyynnnnaaaammmmeeee,    or
     ttttiiiimmmmeeeezzzzoooonnnneeee....bbbbyyyynnnnaaaammmmeeee).  An alternate NIS  map  may  be  specified
     with the ----YYYY option.  For type kkkkeeeeyyyy----vvvvaaaalllluuuueeee, a map specification
     is required.  The map must be in the ////vvvvaaaarrrr////yyyypppp////_y_p_d_o_m_a_i_n direc-
     tory  on the local machine.  Note that _y_p_d_o_m_a_i_n is case sen-
     sitive.  yyyyppppxxxxffffrrrr(1M) can be used to get the NIS maps.

     If a _n_i_s_d_o_m_a_i_n is specified, nnnniiiissssaaaaddddddddeeeennnntttt operates on the  NIS+
     table  in  that NIS+ domain, otherwise the default domain is
     used.

     In terms of performance, loading up the  tables  is  fastest
     when done through the dbm files (----yyyy).

OOOOPPPPTTTTIIIIOOOONNNNSSSS
     ----aaaa         Add the file or map to  the  NIS+  table  without
               deleting any existing entries.  This option is the
               default.  Note  that  this  mode  only  propagates
               additions and modifications, not deletions.

     ----pppp         Process the password field when loading  password
               information from a file.  By default, the password
               field is ignored because it is usually  not  valid
               (the actual password appears in a shadow file).

     ----qqqq         Dump tables in "quick" mode.  The default  method
               for  dumping tables processes each entry individu-
               ally.  For some  tables  (e.g.,  hosts),  multiple
               entries  must  be  combined into a single line, so
               extra requests to the server  must  be  made.   In
               "quick"  mode,  all of the entries for a table are
               retrieved in one call to the server, so the  table
               can  be  dumped  more quickly.  However, for large
               tables, there is a chance that  the  process  will
               run  out  of virtual memory and the table will not
               be dumped.

     ----rrrr         Replace the file or  map  in  the  existing  NIS+
               table  by first deleting any existing entries, and
               then add the entries from the source (////eeeettttcccc  files,
               or NIS+ maps).  This option has the same effect as
               the ----mmmm option.  The use of this option is _s_t_r_o_n_g_l_y
               discouraged  due  to its adverse impact on perfor-
               mance, unless there are a large number of changes.



SunOS 5.4           Last change: 11 May 1995                    2






nisaddent(1M)         Maintenance Commands          nisaddent(1M)



     ----mmmm         Merge the file or map with the NIS+ table.   This
               is  the  most efficient way to bring an NIS+ table
               up to date with a file or NIS map when  there  are
               only  a small number of changes.  This option adds
               entries that are  not  already  in  the  database,
               modifies  entries that already exist (if changed),
               and deletes  any  entries  that  are  not  in  the
               source.   Use  the ----mmmm option whenever the database
               is large and replicated, and the map being  loaded
               differs  only  in  a  few  entries.   This  option
               reduces the number of update messages that have to
               be sent to the replicas.  Also see the ----rrrr option.

     ----dddd         Dump the NIS+ table to the standard output in the
               appropriate format for the given _t_y_p_e.  For tables
               of type kkkkeeeeyyyy----vvvvaaaalllluuuueeee, use nnnniiiissssccccaaaatttt(1) instead.  To dump
               the  ccccrrrreeeedddd  table, dump the ppppuuuubbbblllliiiicccckkkkeeeeyyyy and the nnnneeeettttiiiidddd
               types.

     ----vvvv         Verbose.

     ----ffff _f_i_l_e    Specify that _f_i_l_e should be used as the source of
               input (instead of the standard input).

     ----yyyy _y_p_d_o_m_a_i_n
               Use the ddddbbbbmmmm files for  the  appropriate  NIS  map,
               from  the  NIS  domain  _y_p_d_o_m_a_i_n, as the source of
               input.  The files are expected to be on the  local
               machine in the ////vvvvaaaarrrr////yyyypppp////_y_p_d_o_m_a_i_n directory.  If the
               machine is not an NIS server, use yyyyppppxxxxffffrrrr(1M) to get
               a copy of the ddddbbbbmmmm files for the appropriate map.

     ----YYYY _m_a_p     Use the ddddbbbbmmmm files for _m_a_p as the source of input.

     ----tttt _t_a_b_l_e   Specify that _t_a_b_l_e should be the NIS+  table  for
               this  operation. This should be a relative name as
               compared to your default domain or the  _d_o_m_a_i_n_n_a_m_e
               if it has been specified.

     ----PPPP         Follow concatenation path. This option  specifies
               that  lookups should follow the concatenation path
               of a table if the initial search is unsuccessful.

     ----AAAA         All data. This option  specifies  that  the  data
               within  the table and all of the data in tables in
               the  initial   table's   concatenation   path   be
               returned.

     ----MMMM         Master server only. This  option  specifies  that
               lookups should be sent to the master server.  This
               guarantees that the most up-to-date information is
               seen  at  the  possible  expense  that  the master



SunOS 5.4           Last change: 11 May 1995                    3






nisaddent(1M)         Maintenance Commands          nisaddent(1M)



               server may be busy, or that it may be made busy by
               this operation.

     ----DDDD _d_e_f_a_u_l_t_s
               This option specifies a different set of  defaults
               to  be  used  during  this operation. The _d_e_f_a_u_l_t_s
               string is a series of tokens separated by  colons.
               These  tokens  represent  the default values to be
               used for the generic object properties. All of the
               legal tokens are described below.

               ttttttttllll====_t_i_m_e
                    This token sets the default time to live  for
                    objects that are created by this command. The
                    value _t_i_m_e is  specified  in  the  format  as
                    defined  by  the  nnnniiiisssscccchhhhttttttttllll(1)  command.   The
                    default is 12 hours.

               oooowwwwnnnneeeerrrr====_o_w_n_e_r_n_a_m_e
                    This token specifies that the NIS+  principal
                    _o_w_n_e_r_n_a_m_e  should own the created object. The
                    default for this value is the  principal  who
                    is executing the command.

               ggggrrrroooouuuupppp====_g_r_o_u_p_n_a_m_e
                    This token specifies that the group _g_r_o_u_p_n_a_m_e
                    should be the group owner for the object that
                    is created. The default is NNNNUUUULLLLLLLL.

               aaaacccccccceeeessssssss====_r_i_g_h_t_s
                    This token specifies the set of access rights
                    that  are to be granted for the given object.
                    The value _r_i_g_h_t_s is specified in  the  format
                    as  defined  by the nnnniiiisssscccchhhhmmmmoooodddd(1) command.  The
                    default is ----------------rrrrmmmmccccddddrrrr------------rrrr------------.

EEEEXXXXAAAAMMMMPPPPLLLLEEEESSSS
     This  example  adds  the  contents  of  ////eeeettttcccc////ppppaaaasssssssswwwwdddd  to  the
     ppppaaaasssssssswwwwdddd....oooorrrrgggg____ddddiiiirrrr table.

          eeeexxxxaaaammmmpppplllleeee%%%% ccccaaaatttt ////eeeettttcccc////ppppaaaasssssssswwwwdddd |||| nnnniiiissssaaaaddddddddeeeennnntttt ppppaaaasssssssswwwwdddd

     The next example adds the shadow information; note that  the
     table  type  here is "shadow", not "passwd", even though the
     actual information is stored in the ppppaaaasssssssswwwwdddd table.

          eeeexxxxaaaammmmpppplllleeee%%%% ccccaaaatttt ////eeeettttcccc////sssshhhhaaaaddddoooowwww |||| nnnniiiissssaaaaddddddddeeeennnntttt sssshhhhaaaaddddoooowwww

     This example replaces the hhhhoooossssttttssss....oooorrrrgggg____ddddiiiirrrr table with the  con-
     tents of ////eeeettttcccc////hhhhoooossssttttssss (in verbose mode).

          eeeexxxxaaaammmmpppplllleeee%%%% nnnniiiissssaaaaddddddddeeeennnntttt ----rrrrvvvv ----ffff ////eeeettttcccc////hhhhoooossssttttssss hhhhoooossssttttssss



SunOS 5.4           Last change: 11 May 1995                    4






nisaddent(1M)         Maintenance Commands          nisaddent(1M)



     This example merges the ppppaaaasssssssswwwwdddd map from yyyyyyyyppppddddoooommmmaaaaiiiinnnn  with  the
     ppppaaaasssssssswwwwdddd....oooorrrrgggg____ddddiiiirrrr....nnnniiiissssddddoooommmmaaaaiiiinnnn  table (in verbose mode). The exam-
     ple assumes that the ////vvvvaaaarrrr////yyyypppp////mmmmyyyyyyyyppppddddoooommmmaaaaiiiinnnn  directory  contains
     the yyyyppppppppaaaasssssssswwwwdddd map.

          eeeexxxxaaaammmmpppplllleeee%%%% nnnniiiissssaaaaddddddddeeeennnntttt ----mmmmvvvv ----yyyy mmmmyyyyyyyyppppddddoooommmmaaaaiiiinnnn ppppaaaasssssssswwwwdddd nnnniiiissssddddoooommmmaaaaiiiinnnn

     This example merges the aaaauuuuttttoooo....mmmmaaaasssstttteeeerrrr map from mmmmyyyyyyyyppppddddoooommmmaaaaiiiinnnn with
     the aaaauuuuttttoooo____mmmmaaaasssstttteeeerrrr....oooorrrrgggg____ddddiiiirrrr table.

          eeeexxxxaaaammmmpppplllleeee%%%% nnnniiiissssaaaaddddddddeeeennnntttt ----mmmm ----yyyy mmmmyyyyyyyyppppddddoooommmmaaaaiiiinnnn ----YYYY aaaauuuuttttoooo....mmmmaaaasssstttteeeerrrr \\\\
                 ----tttt aaaauuuuttttoooo____mmmmaaaasssstttteeeerrrr....oooorrrrgggg____ddddiiiirrrr kkkkeeeeyyyy----vvvvaaaalllluuuueeee

     This example dumps the hhhhoooossssttttssss....oooorrrrgggg____ddddiiiirrrr table.

          eeeexxxxaaaammmmpppplllleeee%%%% nnnniiiissssaaaaddddddddeeeennnntttt ----dddd hhhhoooossssttttssss

EEEENNNNVVVVIIIIRRRROOOONNNNMMMMEEEENNNNTTTT
     NNNNIIIISSSS____DDDDEEEEFFFFAAAAUUUULLLLTTTTSSSS   This variable contains a default string  that
                    will  override the NIS+ standard defaults. If
                    the ----DDDD switch is used, those values will then
                    override  both  the NNNNIIIISSSS____DDDDEEEEFFFFAAAAUUUULLLLTTTTSSSS variable and
                    the standard  defaults.   To  avoid  security
                    accidents,   the   access   rights   in   the
                    NNNNIIIISSSS____DDDDEEEEFFFFAAAAUUUULLLLTTTTSSSS variable  are  ignored  for  the
                    ppppaaaasssssssswwwwdddd  table  (but  access  rights specified
                    with ----DDDD are used).

     NNNNIIIISSSS____PPPPAAAATTTTHHHH       If this variable is set, and neither the _n_i_s_-
                    _d_o_m_a_i_n  nor  the  _t_a_b_l_e  are fully qualified,
                    each directory specified in NNNNIIIISSSS____PPPPAAAATTTTHHHH will  be
                    searched until the table is found (see nnnniiiissssddddeeee----
                    ffffaaaauuuullllttttssss(1)).

EEEEXXXXIIIITTTT CCCCOOOODDDDEEEESSSS
     0000    Success.

     1111    Failure caused by an error other than parsing.

     2222    A parsing error occurred on an entry.  A parsing  error
          does  not  cause  termination;  the invalid entries are
          simply skipped.

SSSSEEEEEEEE AAAALLLLSSSSOOOO
     nnnniiiissssccccaaaatttt(1),   nnnniiiisssscccchhhhmmmmoooodddd(1),   nnnniiiissssddddeeeeffffaaaauuuullllttttssss(1),    nnnniiiissssttttbbbbllllaaaaddddmmmm(1),
     nnnniiiissssppppooooppppuuuullllaaaatttteeee(1M),   nnnniiiisssssssseeeerrrrvvvveeeerrrr(1M),  nnnniiiisssssssseeeettttuuuupppp(1M),  yyyyppppxxxxffffrrrr(1M),
     hhhhoooossssttttssss(4), ppppaaaasssssssswwwwdddd(4), sssshhhhaaaaddddoooowwww(4)








SunOS 5.4           Last change: 11 May 1995                    5



