개요

• 솔라나라에 설명된 어플리케이션에 대해 맨 페이지를 찾아 출력한다.
• MAN 페이지에 대한 설명은 윈디하나의 솔라나라: MAN 페이지을 참고하자.
• svcadm(8)을 검색하려면 섹션에서 8 을 선택하고, 맨 페이지 이름에 svcadm을 입력하고 검색을 누른다.

sysobj(7)

sy...j(7)Standards, Environments, Macros, Character Sets, and miscellansyy...j(7)

NAME
       sysobj - system object database

DESCRIPTION
       The system objects database, sysobj enables the following tasks:

           o      Storing objects describing a part of the system, such as de‐
                  vices


           o      Looking objects up in a flexible way


           o      Associating  persistent  data in the form of properties with
                  the objects


           o      Cross-referencing namespaces in which the objects appear



       The following sections provide an overview of the sysobj database.

   Naming
       Namespaces and property classes used in the sysobj database  should  be
       named  consistently and documented in the Section 7 manual page for the
       class of objects they are associated with. The Object  Classes  section
       below contains a list of all currently defined object classes.


       Each  object  can  appear  in multiple namespaces. It is recommended to
       prefix the namespace with the class name of the objects  the  namespace
       represents.  For  example, for objects of the class, device, namespaces
       are of the format, device-XXXX.


       Property class names must follow the same format.

   Object Classes
       Each object is a part of at least one class, its primary class, and can
       be part of multiple classes. The following list specifies all  existing
       object classes, and the man pages that describe these classes:


       device          sysobj-device(7)


       device-minor    sysobj-device(7)



   Client Recommendations
       Since  sysobj  is  a centralized database used by multiple clients, you
       must take care to coordinate access. If you implement a  new  class  of
       objects,  you  must  implement  a  new  plugin,  to be delivered in the
       /usr/lib/sysobj/plugins path, to control access to that  new  class  of
       objects.  The  default access model allows read access and denies write
       access.


       Deleting objects or aliases or both should be the least  common  opera‐
       tion, with the possible exception of initialization on system boot. De‐
       velopers must ensure that these operations do not create unexpected re‐
       sults for other clients.

SEE ALSO
       libsysobj(3LIB),       sysobj_add_alias(3SYSOBJ),      sysobj_add_prop‐
       erty(3SYSOBJ), sysobj_create(3SYSOBJ),  sysobj_event_register(3SYSOBJ),
       sysobjadm(8), sysobjd(8)

Oracle Solaris 11.4               01 Feb 2017                        sy...j(7)