/illumos-gate/usr/src/lib/libresolv2/ |
H A D | install.xml | 3 <!-- 29 --> 31 <service_bundle type='manifest' name='SUNWcsr:dns-install'> 52 <dependent name='network-service' 56 </dependent> 58 <dependent name='dns-client' 62 </dependent> 67 exec='/lib/svc/method/dns-install' 80 <property_group name='install_props' type='application'> 106 <pg_pattern name='install_props' type='application'
|
/illumos-gate/usr/src/man/man3kvm/ |
H A D | kvm_open.3kvm | 8 kvm_open, kvm_close \- specify a kernel to examine 12 \fBcc\fR [ \fIflag\fR\&.\|.\|. ] \fIfile\fR\&.\|.\|. \fB-lkvm\fR [ \fIlibrary\fR\&.\|.\|.] 78 pointer, no error messages will be printed. If it is non-null, it is assumed to 85 Applications using \fBlibkvm\fR are dependent on the underlying data model of 91 For example, a 32\(mibit application that uses the 32\(mibit version of the 93 a 64\(mibit application that uses the 64\(mibit version of the \fBlibkvm\fR 105 The \fBkvm_open()\fR function returns a non-null value suitable for use with 154 MT-Level Unsafe 179 created. While a 32-bit application running on a 64-bit kernel can examine a 180 32-bit core dump, a 64-bit application running on a 64-bit kernel cannot [all …]
|
/illumos-gate/usr/src/man/man7/ |
H A D | filesystem.7 | 25 filesystem \- File system organization 53 start-up script, which is run as part of the booting process. \fB/var\fR can be 59 software are also approved locations for add-on system software or for 62 platform-dependent configuration files that are bundled with Solaris software. 66 In the following descriptions, \fIsubsystem\fR is a category of application or 72 \fBplatform-dependent\fR, \fBplatform-independent\fR, and 73 \fBplatform-specific\fR. Platform refers to a machines Instruction Set 74 Architecture or processor type, such as is returned by \fBuname\fR \fB-i\fR. 75 \fBPlatform-dependent\fR refers to a file that is installed on all platforms 76 and whose contents vary depending on the platform. Like a platform-dependent [all …]
|
/illumos-gate/usr/src/man/man3elf/ |
H A D | gelf.3elf | 14 gelf_update_syminfo, gelf_xlatetof, gelf_xlatetom \- generic class-independent 172 \fBGElf\fR is a generic, \fBELF\fR class-independent \fBAPI\fR for manipulating 174 handling 32-bit and 64-bit \fBELF\fR format object files. \fBGElf\fR is a 175 translation layer between the application and the class-dependent parts of the 176 \fBELF\fR library. Thus, the application can use \fBGElf\fR, which in turn, 178 the application. The data structures returned are all large enough to hold 179 32-bit and 64-bit data. 182 \fBGElf\fR provides a simple, class-independent layer of indirection over the 183 class-dependent \fBELF32\fR and \fBELF64\fR \fBAPI\fR's. \fBGElf\fR is 191 should be avoided. Also, data accessed by type-casting the \fBElf_Data\fR [all …]
|
H A D | elf32_getehdr.3elf | 8 elf32_getehdr, elf32_newehdr, elf64_getehdr, elf64_newehdr \- retrieve 9 class-dependent object file header 13 cc [ \fIflag\fR ... ] \fIfile\fR ... \fB-lelf\fR [ \fIlibrary\fR ... ] 37 For a 32-bit class file, \fBelf32_getehdr()\fR returns a pointer to an 43 system error occurs, the file is not a 32-bit class file, or \fIelf\fR is 77 An application can use \fBelf_getident()\fR to inspect the identification bytes 81 An application can use \fBelf_getshnum()\fR and \fBelf_getshstrndx()\fR to 100 MT-Level MT-Safe
|
/illumos-gate/usr/src/man/man3nsl/ |
H A D | rpc_gss_get_principal_name.3nsl | 8 rpc_gss_get_principal_name \- Get principal names at server 31 mechanism-dependent principal name of the \fBrpc_gss_principal_t\fR structure 37 domain name. An application can choose to set unneeded parameters to 49 An opaque, mechanism-dependent structure representing the client's principal 117 MT-Level MT-Safe 133 Linn, J. \fIRFC 2078, Generic Security Service Application Program Interface, Version 2\fR. Network…
|
H A D | rpcsec_gss.3nsl | 8 rpcsec_gss \- security flavor incorporating GSS-API protections 12 cc [ \fIflag\fR... ] \fIfile\fR... -lnsl [ \fIlibrary\fR... ] 19 \fBRPCSEC_GSS\fR is a security flavor which sits "on top" of the \fBGSS-API\fR 21 \fBRPCSEC_GSS\fR can take advantage of \fBGSS-API\fR security features; 23 Kerberos) that works with the \fBGSS-API.\fR 26 The \fBGSS-API\fR offers two security services beyond the traditional 32 they wish to use. Type of security service is mechanism-independent. 35 Before exchanging data with a peer, an application must establish a context for 37 \fBrpc_gss_seccreate()\fR, which allows the application to specify the security 40 integrity or privacy, and is mechanism-dependent.) Once a context is [all …]
|
/illumos-gate/usr/src/cmd/smbsrv/smbd/ |
H A D | server.xml | 3 <!-- 26 Copyright 2016 Hans Rosenfeld <rosenfeld@grumpf.hope-2000.org> 35 --> 37 <service_bundle type='manifest' name='SUNWsmbsr:smb-server'> 39 <!-- 1. Name the service to 'network/smb/server' --> 45 <!-- 2. Create default service instance. --> 48 <!-- 3. Service has single instance --> 51 <!-- 4. Identify dependencies --> 60 <!-- Must have all local filesystems mounted before we share them --> 61 <dependency name='filesystem-local' [all …]
|
/illumos-gate/usr/src/cmd/auditd/ |
H A D | auditd.xml | 3 <!-- 29 --> 53 <service_fmri value='svc:/milestone/name-services' /> 61 <service_fmri value='svc:/system/system-log' /> 65 <dependent 66 name='multi-user' 69 <service_fmri value='svc:/milestone/multi-user'/> 70 </dependent> 72 <dependent 73 name='console-login' [all …]
|
/illumos-gate/usr/src/cmd/svc/milestone/ |
H A D | rmtmpfiles.xml | 3 <!-- 33 --> 54 <dependent 55 name='rmtmpfiles_multi-user' 58 <service_fmri value='svc:/milestone/multi-user' /> 59 </dependent> 77 <!-- 80 --> 81 <property_group name='options' type='application'> 95 <pg_pattern name="options" type="application">
|
H A D | network-install.xml | 3 <!-- 29 --> 31 <service_bundle type='manifest' name='SUNWcsr:network-install'> 47 <service_fmri value='svc:/network/ip-interface-management' /> 50 <dependent name='physical_default' 54 </dependent> 59 exec='/lib/svc/method/net-install' 72 <!-- The following property group is used only at install time to 73 configure an initial IPv4 network interface --> 74 <property_group name='install_ipv4_interface' type='application'> [all …]
|
H A D | network-netcfg.xml | 3 <!-- 30 --> 32 <service_bundle type='manifest' name='SUNWcsr:network-netcfg'> 43 <!-- 46 --> 47 <dependent 52 </dependent> 83 <property_group name='netcfgd' type='application' >
|
/illumos-gate/usr/src/lib/libsecdb/ |
H A D | rbac.xml | 3 <!-- 30 --> 51 <dependent 55 <service_fmri value='svc:/system/manifest-import' /> 56 </dependent> 58 <dependent 59 name='name-service-cache' 62 <service_fmri value='svc:/system/name-service-cache' /> 63 </dependent> 68 exec='/lib/svc/method/svc-rbac start' [all …]
|
/illumos-gate/usr/src/lib/libdscp/svc/ |
H A D | dscp.xml | 3 <!-- 30 --> 43 <!-- Required for the basic networking to be up --> 52 <!-- Required as non-root local directories could be accessed --> 54 name='local-filesystems' 61 <!-- Required for the DSCP IPsec keys to be installed --> 70 <!-- On OPL platform, the 'dcs' requires the DSCP to be up --> 71 <dependent 76 </dependent> 78 <!-- The FMA event-Transport module requires the DSCP to be up --> [all …]
|
/illumos-gate/usr/src/cmd/lp/lib/papi/ |
H A D | lpsched-misc.c | 120 if ((result[0] == '\0') && (id != -1)) { in printer_name_from_uri_id() 123 snprintf(path, sizeof (path), "%d-0", id); in printer_name_from_uri_id() 125 result = request->destination; in printer_name_from_uri_id() 137 * LP content type <-> MIME type conversion table. (order dependent) 144 { "application/octet-stream", "raw" }, 145 { "application/octet-stream", "any" }, 146 { "application/postscript", "postscript" }, 147 { "application/postscript", "ps" }, 148 { "application/x-cif", "cif" }, 149 { "application/x-dvi", "dvi" }, [all …]
|
/illumos-gate/usr/src/man/man3c/ |
H A D | fputc.3c | 16 .\" Standard for Information Technology -- Portable Operating System 18 .\" Copyright (C) 2001-2004 by the Institute of Electrical and Electronics 48 fputc, putc, putc_unlocked, putchar, putchar_unlocked, putw \- put a byte on a 85 position indicated by the associated file-position indicator for the stream (if 133 a non-zero value, sets the error indicator for the associated \fIstream\fR, and 204 \fBopen_wmemstream\fR(3C) and a wide-character or byte sequence buffered is 206 implementation-dependent conditions. 248 A request was made of a non-existent device, or the request was outside the 266 using \fBputw()\fR are implementation-dependent, and possibly cannot be read 267 using \fBgetw\fR(3C) by a different application or by the same application [all …]
|
H A D | pthread_attr_getguardsize.3c | 16 .\" Standard for Information Technology -- Portable Operating System 18 .\" Copyright (C) 2001-2004 by the Institute of Electrical and Electronics 49 pthread_attr_getguardsize, pthread_attr_setguardsize \- get or set thread 54 cc -mt [ \fIflag\fR... ] \fIfile\fR... -lpthread [ \fIlibrary\fR... ] 74 application overflows into this buffer an error results (possibly in a 78 The \fIguardsize\fR attribute is provided to the application for two reasons: 83 application that creates a large number of threads, and which knows its threads 118 The actual value of \fBPAGESIZE\fR is implementation-dependent and may not be 125 responsibility of the application to manage stack overflow along with stack 180 MT-Level MT-Safe
|
H A D | fwrite.3c | 16 .\" Standard for Information Technology -- Portable Operating System 18 .\" Copyright (C) 2001-2004 by the Institute of Electrical and Electronics 49 fwrite \- binary output 62 \fBunsigned char\fR exactly overlaying the object. The file-position indicator 64 written. If an error occurs, the resulting value of the file-position indicator 88 written using \fBfwrite()\fR are application-dependent, and possibly cannot be 89 read using \fBfread\fR(3C) by a different application or by the same 90 application on a different processor. 104 MT-Level MT-Safe
|
H A D | fread.3c | 16 .\" Standard for Information Technology -- Portable Operating System 18 .\" Copyright (C) 2001-2004 by the Institute of Electrical and Electronics 49 fread \- binary input 66 file-position indicator for the stream (if defined) is advanced by the number 68 file-position indicator for the stream is unspecified. If a partial element is 84 end-of-file is encountered. If \fIsize\fR or \fInitems\fR is 0, \fBfread()\fR 118 between an error condition and end-of-file condition. See \fBferror\fR(3C). 122 written using \fBfwrite\fR(3C) are application-dependent, and possibly cannot 123 be read using \fBfread()\fR by a different application or by the same 124 application on a different processor. [all …]
|
/illumos-gate/usr/src/man/man3socket/ |
H A D | inet6_rth.3socket | 10 inet6_rth_segments, inet6_rth_getaddr \- Routing header manipulation 14 \fBcc\fR [ \fIflag\fR ... ] \fIfile\fR ... \fB-lsocket\fR [\fIlibrary\fR] 89 To receive a routing header, the application must enable the 105 To send a routing header, the application specifies it either as ancillary data 108 described in \fIRFC-2460\fR. Applications can specify no more than one outgoing 112 The application can remove any sticky routing header by calling 116 When using ancillary data, a routing header is passed between the application 120 implementation-dependent and should not be accessed directly by the 121 application, but should be accessed using the \fBinet6_rth\fR functions. 138 currently defines only the Type 0 header. See \fIRFC-2460\fR. The Type 0 header [all …]
|
/illumos-gate/usr/src/man/man3head/ |
H A D | siginfo.h.3head | 9 siginfo.h, siginfo \- signal generation information 37 \fBsi_signo\fR contains the system-generated signal number. For the 41 If \fBsi_errno\fR is non-zero, it contains an error number associated with 132 \fBsi_value\fR contains the application specified value, which is passed to the 133 application's signal-catching function at the time of the signal delivery if 139 Non-user generated signals can arise for a number of reasons. For all of these 156 ILL_COPROC co-processor error 172 BUS_ADRERR non-existent physical address 196 signals do not already possess kernel-level \fBsiginfo\fR codes, the 198 kernel-generated signal from an established resource control value. [all …]
|
/illumos-gate/usr/src/cmd/varpd/ |
H A D | varpd.xml | 3 <!-- 15 --> 23 <dependency name="varpd-datalink-management" 27 <service_fmri value="svc:/network/datalink-management:default" /> 30 <dependency name="varpd-device-local" 37 <dependency name="varpd-filesystem-minimal" 44 <dependent name='varpd-network-physical-default' 48 </dependent> 62 <property_group name='varpd' type='application'>
|
/illumos-gate/usr/src/man/man4i/ |
H A D | prnio.4i | 34 .Bl -bullet -offset indent 47 During the Identification phase, the application retrieves a set of device 57 During the Setup phase the application sets some interface attributes and 88 may set non-zero error code as appropriate. 101 The application can perform some additional cleanup 106 .Bl -tag -width PRNIOC_GET_IFINFO 108 Application can retrieve printer interface capabilities using this command. 117 .Bl -tag -width PRN_1284_STATUS 120 bidirectional mode, instead of forward-only mode. 122 If this bit is set, the interface allows device hot-plugging. [all …]
|
/illumos-gate/usr/src/cmd/cmd-inet/usr.lib/in.mpathd/ |
H A D | network-ipmp.xml | 4 <!-- 20 --> 36 <dependent name='network-physical' grouping='optional_all' 39 </dependent> 41 <exec_method type='method' name='start' exec='/lib/svc/method/net-ipmp' 49 <exec_method type='method' name='refresh' exec=':kill -HUP' 53 <property_group name='config' type='application'>
|
/illumos-gate/usr/src/man/man4d/ |
H A D | ticlts.4d | 9 ticlts, ticots, ticotsord \- loopback transport providers 30 ``loopback transport providers,'' that is, stand-alone networks at the 33 loopback network. Loopback transports present a \fBTPI\fR (STREAMS-level) 34 interface to application processes and are intended to be accessed via the 35 \fBTLI\fR (application-level) interface. They are implemented as clone devices 36 and support address spaces consisting of ``flex-addresses,'' that is, arbitrary 40 \fBticlts\fR is a datagram-mode transport provider. It offers (connectionless) 82 \fBticots\fR is a virtual circuit-mode transport provider. It offers 83 (connection-oriented) service of type \fBT_COTS\fR. Its default address size is 119 peer-initiated disconnect [all …]
|