Hallo, dies ist ein Test.

PWD: /www/data-lst1/unixsoft/unixsoft/kaempfer/.public_html

Running in File Mode
Relative path: ./../../../../../../usr/man/man4p/ip6.4p
Real path: /usr/share/man/man4p/ip6.4p
Zurück

'\" te .\" Copyright (c) 2008, 2021, Oracle and/or its affiliates. .TH ip6 4P "24 Feb 2021" "Oracle Solaris 11.4" "Network Protocols" .SH NAME ip6 \- Internet Protocol Version 6 .SH SYNOPSIS .LP .nf #include <sys/socket.h> #include <netinet/in.h> #include <netinet/ip6.h> .fi .LP .nf s = socket(AF_INET6, SOCK_RAW, proto); .fi .LP .nf t = t_open ("/dev/rawip6", O_RDWR); .fi .SH DESCRIPTION .sp .LP The \fBIPv6\fR protocol is the next generation of the internetwork datagram delivery protocol of the Internet protocol family. Programs can use \fBIPv6\fR through higher-level protocols such as the Transmission Control Protocol (\fBTCP\fR) or the User Datagram Protocol (\fBUDP\fR), or can interface directly to \fBIPv6\fR. See \fBtcp\fR(4P) and \fBudp\fR(4P). Direct access can be by means of the socket interface, using a "raw socket," or by means of the Transport Level Interface (\fBTLI\fR). The protocol options and \fBIPv6\fR extension headers defined in the \fBIPv6\fR specification can be set in outgoing datagrams. .SH APPLICATION PROGRAMMING INTERFACE .sp .LP The \fBSTREAMS\fR driver \fB/dev/rawip6\fR is the \fBTLI\fR transport provider that provides raw access to \fBIPv6\fR. .sp .LP Raw \fBIPv6\fR sockets are connectionless and are normally used with the \fBsendto()\fR and \fBrecvfrom()\fR calls (see \fBsend\fR(3C) and \fBrecv\fR(3C)), although the \fBconnect\fR(3C) call can also be used to fix the destination for future datagrams. In this case, the \fBread\fR(2) or \fBrecv\fR(3C) and \fBwrite\fR(2) or \fBsend\fR(3C) calls can be used. Ancillary data can also be sent or received over raw \fBIPv6\fR sockets using the \fBsendmsg\fR(3C) and \fBrecvmsg\fR(3C) system calls. .sp .LP Unlike raw \fBIP\fR, \fBIPv6\fR applications do not include a complete \fBIPv6\fR header when sending; there is no \fBIPv6\fR analog to the \fBIP\fR \fBIP_HDRINCL\fR socket option. \fBIPv6\fR header values can be specified or received as ancillary data to a \fBsendmsg\fR(3C) or \fBrecvmsg\fR(3C) system call, or can be specified as sticky options on a per-socket basis by using the \fBsetsockopt\fR(3C) system call. Such sticky options are applied to all outbound packets unless overridden by ancillary data. If any ancillary data is specified in a \fBsendmsg\fR(3C) call, all sticky options not explicitly overridden revert to default values for that datagram only; the sticky options persist as set for subsequent datagrams. .sp .LP Since \fBsendmsg\fR(3C) is not supported for \fBSOCK_STREAM\fR upper level protocols such as \fBTCP\fR, ancillary data is unsupported for \fBTCP\fR. Sticky options, however, are supported. .sp .LP Since \fBsendmsg\fR(3C) is supported for \fBSOCK_DGRAM\fR upper level protocols, both ancillary data and sticky options are supported for \fBUDP\fR, \fBICMP6\fR, and raw \fBIPv6\fR sockets. .sp .LP The socket options supported at the \fBIPv6\fR level are: .sp .ne 2 .mk .na \fB\fBIPV6_BOUND_IF\fR\fR .ad .RS 24n .rt Limit reception and transmission of packets to this interface. Takes an integer as an argument; the integer is the selected interface index. .RE .sp .ne 2 .mk .na \fB\fBIPV6_UNSPEC_SRC\fR\fR .ad .RS 24n .rt Boolean. Allow/disallow sending with a zero source address. .RE .sp .ne 2 .mk .na \fB\fBIPV6_UNICAST_HOPS\fR\fR .ad .RS 24n .rt Default hop limit for unicast datagrams. This option takes an integer as an argument. Its value becomes the new default value for \fBip6_hops\fR that \fBIPv6\fR uses on outgoing unicast datagrams sent from that socket. The initial default is \fB60\fR. .RE .sp .ne 2 .mk .na \fB\fBIPV6_CHECKSUM\fR\fR .ad .RS 24n .rt Specify the integer offset in bytes into the user data of the checksum location. Does not apply to the \fBICMP6\fR protocol. Note: checksums are required for all \fBIPv6\fR datagrams; this is different from \fBIP\fR, in which datagram checksums were optional. \fBIPv6\fR computes the \fBULP\fR checksum if the value in the checksum field is zero. .RE .sp .ne 2 .mk .na \fB\fBIPV6_SEC_OPT\fR\fR .ad .RS 24n .rt Enable or obtain IPsec security settings for this socket. For more details on the protection services of IPsec, see \fBipsec\fR(4P). .RE .sp .ne 2 .mk .na \fB\fBIPV6_DONTFRAG\fR\fR .ad .RS 24n .rt Boolean. Control fragmentation. .RE .sp .ne 2 .mk .na \fB\fBIPV6_USE_MIN_MTU\fR\fR .ad .RS 24n .rt Controls whether path MTU discovery is used. If set to 1, path MTU discovery is never used and IPv6 packets are sent with the IPv6 minimum MTU. If set to -1, path MTU discovery is not used for multicast and multicast packets are sent with the IPv6 minimum MTU. If set to 0, path MTU is always performed. .RE .sp .ne 2 .mk .na \fB\fBIPV6_V6ONLY\fR\fR .ad .RS 24n .rt Boolean. If set, only V6 packets can be sent or received .RE .sp .ne 2 .mk .na \fB\fBIPV6_SRC_PREFERENCES\fR\fR .ad .RS 24n .rt Enable or obtain Source Address Selection rule settings for this socket. For more details on the Source Address Selection rules, see \fBinet6\fR(4P). .RE .sp .LP The following options are boolean switches controlling the reception of ancillary data: .sp .ne 2 .mk .na \fB\fBIPV6_RECVPKTINFO\fR\fR .ad .RS 25n .rt Enable/disable receipt of the index of the interface the packet arrived on, and of the inbound packet's destination address. .RE .sp .ne 2 .mk .na \fB\fBIPV6_RECVHOPLIMIT\fR\fR .ad .RS 25n .rt Enable/disable receipt of the inbound packet's current hoplimit. .RE .sp .ne 2 .mk .na \fB\fBIPV6_RECVHOPOPTS\fR\fR .ad .RS 25n .rt Enable/disable receipt of the inbound packet's \fBIPv6\fR hop-by-hop extension header. .RE .sp .ne 2 .mk .na \fB\fBIPV6_RECVDSTOPTS\fR\fR .ad .RS 25n .rt Enable/disable receipt of the inbound packet's \fBIPv6\fR destination options extension header. .RE .sp .ne 2 .mk .na \fB\fBIPV6_RECVRTHDR\fR\fR .ad .RS 25n .rt Enable/disable receipt of the inbound packet's \fBIPv6\fR routing header. .RE .sp .ne 2 .mk .na \fB\fBIPV6_RECVRTHDRDSTOPTS\fR\fR .ad .RS 25n .rt Enable/disable receipt of the inbound packet's intermediate-hops options extension header. This option is obsolete. \fBIPV6_RECVDSTOPTS\fR turns on receipt of both destination option headers. .RE .sp .ne 2 .mk .na \fB\fBIPV6_RECVTCLASS\fR\fR .ad .RS 25n .rt Enable/disable receipt of the traffic class of the inbound packet. .RE .sp .ne 2 .mk .na \fB\fBIPV6_RECVPATHMTU\fR\fR .ad .RS 25n .rt Enable/disable receipt of the path mtu of the inbound packet. .RE .sp .LP The following options can be set as sticky options with \fBsetsockopt\fR(3C) or as ancillary data to a \fBsendmsg\fR(3C) system call: .sp .ne 2 .mk .na \fB\fBIPV6_PKTINFO\fR\fR .ad .RS 21n .rt Set the source address and/or interface out which the packet(s) is sent. Takes a \fBstruct\fR \fBin6_pktinfo\fR as the parameter. .RE .sp .ne 2 .mk .na \fB\fBIPV6_HOPLIMIT\fR\fR .ad .RS 21n .rt Set the initial \fBhoplimit\fR for outbound datagrams. Takes an integer as the parameter. This option sets the \fBhoplimit\fR only for ancillary data or sticky options and does not change the default \fBhoplimit\fR for the socket; see \fBIPV6_UNICAST_HOPS\fR and \fBIPV6_MULTICAST_HOPS\fR to change the socket's default \fBhoplimit\fR. .RE .sp .ne 2 .mk .na \fB\fBIPV6_NEXTHOP\fR\fR .ad .RS 21n .rt Specify the \fBIPv6\fR address of the first hop, which must be a neighbor of the sending host. Takes a \fBstruct\fR \fBsockaddr_in6\fR as the parameter. When this option specifies the same address as the destination \fBIPv6\fR address of the datagram, this is equivalent to the existing \fBSO_DONTROUTE\fR option. .RE .sp .ne 2 .mk .na \fB\fBIPV6_HOPOPTS\fR\fR .ad .RS 21n .rt Specify one or more hop-by-hop options. Variable length. Takes a complete \fBIPv6\fR hop-by-hop options extension header as the parameter. .RE .sp .ne 2 .mk .na \fB\fBIPV6_DSTOPTS\fR\fR .ad .RS 21n .rt Specify one or more destination options. Variable length. Takes a complete \fBIPv6\fR destination options extension header as the parameter. .RE .sp .ne 2 .mk .na \fB\fBIPV6_RTHDR\fR\fR .ad .RS 21n .rt Specify the \fBIPv6\fR routing header. Variable length. Takes a complete \fBIPv6\fR routing header as the parameter. Currently, only type 0 routing headers are supported. .RE .sp .ne 2 .mk .na \fB\fBIPV6_RTHDRDSTOPTS\fR\fR .ad .RS 21n .rt Specify one or more destination options for all intermediate hops. May be configured, but is not applied unless an \fBIPv6\fR routing header is also configured. Variable length. Takes a complete \fBIPv6\fR destination options extension header as the parameter. .RE .sp .ne 2 .mk .na \fB\fBIPV6_PATHMTU\fR\fR .ad .RS 21n .rt Get the path MTU associated with a connected socket. Takes a ip6_mtuinfo as the parameter. .RE .sp .ne 2 .mk .na \fB\fBIPV6_TCLASS\fR\fR .ad .RS 21n .rt Set the traffic class associated with outgoing packets. The parameter is an integer. If the parameter is less then -1 or greater then 256, EINVAL is returned. If the parameter is equal to -1, use the default. If the parameter is between 0 and 255 inclusive, use that value. .RE .sp .LP The following options affect the socket's multicast behavior: .sp .ne 2 .mk .na \fB\fBIPV6_JOIN_GROUP\fR\fR .ad .RS 28n .rt Join a multicast group. Takes a \fBstruct\fR \fBipv6_mreq\fR as the parameter; the structure contains a multicast address and an interface index. .RE .sp .ne 2 .mk .na \fB\fBIPV6_LEAVE_GROUP\fR\fR .ad .RS 28n .rt Leave a multicast group. Takes a \fBstruct\fR \fBipv6_mreq\fR as the parameter; the structure contains a multicast address and an interface index. .RE .sp .ne 2 .mk .na \fB\fBMCAST_JOIN_GROUP\fR\fR .ad .RS 28n .rt Functionally equivalent to \fBIPV6_JOIN_GROUP\fR. Takes a \fBstruct\fR \fBgroup_req\fR as the parameter. The structure contains a multicast address and an interface index. .RE .sp .ne 2 .mk .na \fB\fBMCAST_BLOCK_SOURCE\fR\fR .ad .RS 28n .rt Block multicast packets on a particular multicast group whose source address matches the given source address. The specified group must be joined previously using \fBIPV6_JOIN_GROUP\fR or \fBMCAST_JOIN_GROUP\fR. Takes a \fBstruct\fR \fBgroup_source_req\fR as the parameter. The structure contains an interface index, a multicast address, and a source address. .RE .sp .ne 2 .mk .na \fB\fBMCAST_UNBLOCK_SOURCE\fR\fR .ad .RS 28n .rt Unblock multicast packets which were previously blocked using \fBMCAST_BLOCK_SOURCE\fR. Takes a \fBstruct\fR \fBgroup_source_req\fR as the parameter. The structure contains an interface index, a multicast address, and a source address. .RE .sp .ne 2 .mk .na \fB\fBMCAST_LEAVE_GROUP\fR\fR .ad .RS 28n .rt Functionally equivalent to \fBIPV6_LEAVE_GROUP\fR. Takes a \fBstruct\fR \fBgroup_req\fR as the parameter. The structure contains a multicast address and an interface index. .RE .sp .ne 2 .mk .na \fB\fBMCAST_JOIN_SOURCE_GROUP\fR\fR .ad .RS 28n .rt Begin receiving packets for the given multicast group whose source address matches the specified address. Takes a \fBstruct\fR \fBgroup_source_req\fR as the parameter. The structure contains an interface index, a multicast address, and a source address. .RE .sp .ne 2 .mk .na \fB\fBMCAST_LEAVE_SOURCE_GROUP\fR\fR .ad .RS 28n .rt Stop receiving packets for the given multicast group whose source address matches the specified address. Takes a \fBstruct\fR \fBgroup_source_req\fR as the parameter. The structure contains an interface index, a multicast address, and a source address. .RE .sp .ne 2 .mk .na \fB\fBIPV6_MULTICAST_IF\fR\fR .ad .RS 28n .rt The outgoing interface for multicast packets. This option takes an integer as an argument; the integer is the interface index of the selected interface. .RE .sp .ne 2 .mk .na \fB\fBIPV6_MULTICAST_HOPS\fR\fR .ad .RS 28n .rt Default hop limit for multicast datagrams. This option takes an integer as an argument. Its value becomes the new default value for \fBip6_hops\fR that \fBIPv6\fR uses on outgoing multicast datagrams sent from that socket. The initial default is \fB1\fR. .RE .sp .ne 2 .mk .na \fB\fBIPV6_MULTICAST_LOOP\fR\fR .ad .RS 28n .rt Loopback for multicast datagrams. Normally multicast datagrams are delivered to members on the sending host. Setting the unsigned character argument to 0 causes the opposite behavior. .RE .sp .LP The multicast socket options can be used with any datagram socket type in the \fBIPv6\fR family. .sp .LP At the socket level, the socket option \fBSO_DONTROUTE\fR can be applied. This option forces datagrams being sent to bypass routing and forwarding by forcing the \fBIPv6\fR \fBhoplimit\fR field to \fB1\fR, meaning that the packet is not forwarded by routers. .sp .LP Raw \fBIPv6\fR datagrams can also be sent and received using the \fBTLI\fR connectionless primitives. .sp .LP Datagrams flow through the \fBIPv6\fR layer in two directions: from the network \fIup\fR to user processes and from user processes \fIdown\fR to the network. Using this orientation, \fBIPv6\fR is layered \fIabove\fR the network interface drivers and \fIbelow\fR the transport protocols such as \fBUDP\fR and \fBTCP\fR. The Internet Control Message Protocol (\fBICMPv6\fR) for the Internet Protocol Version 6 (\fBIPv6\fR) is logically a part of \fBIPv6\fR. See \fBicmp6\fR(4P). .sp .LP Unlike \fBIP\fR, \fBIPv6\fR provides no checksum of the \fBIPv6\fR header. Also unlike \fBIP\fR, upper level protocol checksums are required. \fBIPv6\fR computes the \fBULP\fR/data portion checksum if the checksum field contains a zero (see \fBIPV6_CHECKSUM\fR option above). .sp .LP \fBIPv6\fR extension headers in received datagrams are processed in the \fBIPv6\fR layer according to the protocol specification. Currently recognized \fBIPv6\fR extension headers include hop-by-hop options header, destination options header, routing header (currently, only type 0 routing headers are supported), and fragment header. .sp .LP By default, the IPv6 layer does not forward IPv6 packets that are not addressed to it. This behavior can be overridden by using \fBrouteadm\fR(8) to enable the \fBipv6-forwarding\fR option. IPv6 forwarding is configured at boot time based on the setting of \fBrouteadm\fR's \fBipv6-forwarding\fR option. \fBipadm\fR(8) can also be used to enable ipv6 forwarding on a global basis. The \fBipadm set-prop\fR subcommand along with the \fBforwarding\fR property is used to enable system-wide forwarding of packets. The protocol for which forwarding needs to be enabled is specified using the \fB-m\fR option. See \fBipadm\fR(8) for more details. .sp .LP Additionally, finer-grained forwarding can be configured in IPv6. Each interface can be configured to forward IPv6 packets by setting the \fBIFF_ROUTER\fR interface flag. This flag can be set and cleared using the \fBifconfig\fR(8) \fBrouter\fR and \fB-router\fR options. If an interface's \fBIFF_ROUTER\fR flag is set, packets can be forwarded to or from the interface. If it is clear, packets is neither forwarded from this interface to others, nor forwarded to this interface. Setting the global ipv6 forwarding variable sets all of the IPv6 interfaces' \fBIFF_ROUTER\fR flags. Also, the \fBipadm set-ifprop\fR subcommand can be used to enable/disable per-interface ipv6 forwarding. See \fBipadm\fR(8) for more details. The \fBipadm set-ifprop\fR interfaces are preferred. .sp .LP The \fBIPv6\fR layer sends an \fBICMP6\fR message back to the source host in many cases when it receives a datagram that can not be handled. A \fBtime exceeded\fR \fBICMP6\fR message is sent if the \fBip6_hops\fR field in the \fBIPv6\fR header drops to zero in the process of forwarding a datagram. A \fBdestination unreachable\fR message is sent by a router or by the originating host if a datagram can not be sent on because there is no route to the final destination; it is sent by a router when it encounters a firewall prohibition; it is sent by a destination node when the transport protocol (that is, \fBTCP\fR) has no listener. A \fBpacket too big\fR message is sent by a router if the packet is larger than the \fBMTU\fR of the outgoing link (this is used for Path \fBMTU\fR Discovery). A \fBparameter problem\fR message is sent if there is a problem with a field in the \fBIPv6\fR header or any of the \fBIPv6\fR extension headers such that the packet cannot be fully processed. .sp .LP The \fBIPv6\fR layer supports fragmentation and reassembly. Datagrams are fragmented on output if the datagram is larger than the maximum transmission unit (\fBMTU\fR) of the network interface. Fragments of received datagrams are dropped from the reassembly queues if the complete datagram is not reconstructed within a short time period. .sp .LP Errors in sending discovered at the network interface driver layer are passed by IPv6 back up to the user process. .SH SEE ALSO .sp .LP \fBsvcs\fR(1), \fBread\fR(2), \fBwrite\fR(2), \fBsend\fR(3C), \fBbind\fR(3C), \fBconnect\fR(3C), \fBgetsockopt\fR(3C), \fBrecv\fR(3C), \fBrecvmsg\fR(3C), \fBsendmsg\fR(3C), \fBsetsockopt\fR(3C), \fBicmp6\fR(4P), \fBif_tcp\fR(4P), \fBinet6\fR(4P), \fBipsec\fR(4P), \fBrouting\fR(4P), \fBtcp\fR(4P), \fBudp\fR(4P), \fBsmf\fR(7), \fBifconfig\fR(8), \fBipadm\fR(8), \fBndd\fR(8), \fBrouteadm\fR(8), \fBsvcadm\fR(8) .sp .LP Deering, S. and Hinden, R. \fIRFC 8200, Internet Protocol, Version 6 (IPv6) Specification\fR. Network Working Group. July 2017. https://tools.ietf.org/html/rfc8200 .sp .LP Gilligan, R. \fIRFC 3493, Basic Socket Interface Extensions for IPv6\fR. Network Working Group. February 2003. https://tools.ietf.org/html/rfc3493 .sp .LP Stevens, W., Thomas, M., Nordmark, E., and Jinmei, T. \fIRFC 3542, Advanced Sockets API for IPv6\fR. Network Working Group. May 2003. https://tools.ietf.org/html/rfc3542 .SH DIAGNOSTICS .sp .LP A socket operation can fail with one of the following errors returned: .sp .ne 2 .mk .na \fB\fBEPROTONOSUPPORT\fR\fR .ad .RS 19n .rt Unsupported protocol (for example, IPPROTO_RAW.) .RE .sp .ne 2 .mk .na \fB\fBEACCES\fR\fR .ad .RS 19n .rt A \fBbind()\fR operation was attempted with a "reserved" port number and the effective user ID of the process was not the privileged user. .RE .sp .ne 2 .mk .na \fB\fBEADDRINUSE\fR\fR .ad .RS 19n .rt A \fBbind()\fR operation was attempted on a socket with a network address/port pair that has already been bound to another socket. .RE .sp .ne 2 .mk .na \fB\fBEADDRNOTAVAIL\fR\fR .ad .RS 19n .rt A \fBbind()\fR operation was attempted for an address that is not configured on this machine. .RE .sp .ne 2 .mk .na \fB\fBEINVAL\fR\fR .ad .RS 19n .rt A \fBsendmsg()\fR operation with a non-NULL \fBmsg_accrights\fR was attempted. .RE .sp .ne 2 .mk .na \fB\fBEINVAL\fR\fR .ad .RS 19n .rt A \fBgetsockopt()\fR or \fBsetsockopt()\fR operation with an unknown socket option name was given. .RE .sp .ne 2 .mk .na \fB\fBEINVAL\fR\fR .ad .RS 19n .rt A \fBgetsockopt()\fR or \fBsetsockopt()\fR operation was attempted with the \fBIPv6\fR option field improperly formed; an option field was shorter than the minimum value or longer than the option buffer provided; the value in the option field was invalid. .RE .sp .ne 2 .mk .na \fB\fBEISCONN\fR\fR .ad .RS 19n .rt A \fBconnect()\fR operation was attempted on a socket on which a \fBconnect()\fR operation had already been performed, and the socket could not be successfully disconnected before making the new connection. .RE .sp .ne 2 .mk .na \fB\fBEISCONN\fR\fR .ad .RS 19n .rt A \fBsendto()\fR or \fBsendmsg()\fR operation specifying an address to which the message should be sent was attempted on a socket on which a \fBconnect()\fR operation had already been performed. .RE .sp .ne 2 .mk .na \fB\fBEMSGSIZE\fR\fR .ad .RS 19n .rt A \fBsend()\fR, \fBsendto()\fR, or \fBsendmsg()\fR operation was attempted to send a datagram that was too large for an interface, but was not allowed to be fragmented (such as broadcasts). .RE .sp .ne 2 .mk .na \fB\fBENETUNREACH\fR\fR .ad .RS 19n .rt An attempt was made to establish a connection via \fBconnect()\fR, or to send a datagram by means of \fBsendto()\fR or \fBsendmsg()\fR, where there was no matching entry in the routing table; or if an \fBICMP\fR "\fBdestination unreachable\fR" message was received. .RE .sp .ne 2 .mk .na \fB\fBENOTCONN\fR\fR .ad .RS 19n .rt A \fBsend()\fR or \fBwrite()\fR operation, or a \fBsendto()\fR or \fBsendmsg()\fR operation not specifying an address to which the message should be sent, was attempted on a socket on which a \fBconnect()\fR operation had not already been performed. .RE .sp .ne 2 .mk .na \fB\fBENOBUFS\fR\fR .ad .RS 19n .rt The system ran out of memory for fragmentation buffers or other internal data structures. .RE .sp .ne 2 .mk .na \fB\fBENOMEM\fR\fR .ad .RS 19n .rt The system was unable to allocate memory for an \fBIPv6\fR socket option or other internal data structures. .RE .sp .ne 2 .mk .na \fB\fBENOPROTOOPT\fR\fR .ad .RS 19n .rt An \fBIP\fR socket option was attempted on an \fBIPv6\fR socket, or an \fBIPv6\fR socket option was attempted on an \fBIP\fR socket. .RE .sp .ne 2 .mk .na \fB\fBENOPROTOOPT\fR\fR .ad .RS 19n .rt Invalid socket type for the option. .RE .SH NOTES .sp .LP Applications using the sockets \fBAPI\fR must use the Advanced Sockets \fBAPI\fR for \fBIPv6\fR (\fIRFC 3542\fR) to see elements of the inbound packet's \fBIPv6\fR header or extension headers. .sp .LP The \fBip6\fR service is managed by the service management facility, \fBsmf\fR(7), under the service identifier: .sp .in +2 .nf svc:/network/initial:default .fi .in -2 .sp .sp .LP Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using \fBsvcadm\fR(8). The service's status can be queried using the \fBsvcs\fR(1) command.