Red Hat Directory Server Sample Clauses

Red Hat Directory Server. 软 件 订 阅 Directory Server 的服务级别(如附录 1 第 2 节所述)取决于运行 Directory Server 之系统、物理节点或虚拟节点的 Red Hat Enterprise Linux 订阅服务级别(例如,如果基础 Red Hat Enterprise Linux 软件订阅的服务级别 为高级,则 Directory Server 将获得高级级别支持)。
AutoNDA by SimpleDocs
Red Hat Directory Server. 1 — 5 Ç — 5 ࠋ Red Hat Directory Server §GŸ5Çj?ÿ¬s G—Ÿ5ª.G࣏ —hÇh@1—5Ç—5࡟౑$Çh@ ྜ࡟ fl.¾Š
Red Hat Directory Server. ࣅࢫ サӲࢫPj?ࢩࣙࣥ サ y࢕JPࢺj サ—ࣂ—Œサ—ࣅࢫJҮЫ(௜ᒓᩥ᭩ 1ࠊ➨ 2 㡯࡟ㄝ᫂)ࡣࠊy࢕JPࢺj サ—ࣂ—Ç✌ືࡉࡏࡿࢩࢫȳ࣒ࠊ≀⌮/ —ࢻࡲ½ࡣ௬᝿/—ࢻŒRed Hat Enterprise Linux サӲࢫPj? ࢩࣙࣥŒサ—ࣅࢫJҮЫ࡟ᇶY࠸ZỴᐃࡉࢀࡲࡍ(౛:Red Hat Enterprise Linux /ࣇࢺ࢘±࢔サӲࢫPj?ࢩࣙࣥŒサ—ࣅࢫJ ҮЫࡀ?J࣑࢔࣒Œgྜࠊy࢕JPࢺj サ—ࣂ—ࡣ?J࣑࢔࣒ JҮЫŒサ࣏—ࢺÇpࡅࡲࡍ)。
Red Hat Directory Server. Ÿ5 GŸ5Çj?ÿ¬s G yÇJÇhj G—‰—§G—Ÿ5JŸk(fiᒓ@᭩ 1.ø 2 ‰࡟ %᫂)ª.yÇJÇhj G—‰—Ç✌$Çt@ÿ5y£.fl⌮J —fi£½ª௬᝿J—fi§Red Hat Enterprise Linux GŸ5Çj? ÿ¬s§G—Ÿ5JŸk࡟ᇶŸ”€Ỵ;Çh£g(౛:Red Hat Enterprise Linux ∫€hfi±{GŸ5Çj?ÿ¬s§G—X0X Xx‰?J½{£§ྜ.yÇJÇhj G—‰—ª?J½{£ JŸk§G࣏—hÇpfl£g)ࠋ

Related to Red Hat Directory Server

  • Red Hat Directory Server Use Cases Subscription Services are provided for Red Hat Directory Server only when used for its supported Use Case in accordance with the terms of this Exhibit and Table 3.1 below.

  • Other Directory Services 73.10.1 Both parties acknowledge that CenturyLink’s directory publisher is not a party to this Agreement and that the provisions contained in this Agreement are not binding upon CenturyLink’s directory publisher.

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-­‐based Directory Service at <whois.nic.TLD> providing free public query-­‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-­‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry.

  • Directory Listing and Directory Distribution 41 5. Voice Information Service Traffic 43 6. Intercept and Referral Announcements 44 7. Originating Line Number Screening (OLNS) 44 8. Operations Support Systems (OSS) Services 44 9. Poles, Ducts, Conduits and Xxxxxx-xx-Xxx 00 00. Telephone Numbers 51 11. Routing for Operator Services and Directory Assistance Traffic 51 12. Unauthorized Carrier Change Charges 52 13. Good Faith Performance 52 INTERCONNECTION ATTACHMENT. 53 1. General 53 2. Points of Interconnection and Trunk Types 53 3. Alternative Interconnection Arrangements 57 4. Initiating Interconnection 58 5. Transmission and Routing of Telephone Exchange Service Traffic 59

  • Project Director The individual designated by the juvenile board or Chief Administrative Officer, who is to be responsible for the administration and coordination of grant funds in accordance with this Contract ,, the general grant requirements, and applicable Targeted Grant requirements.

  • Directory Listings 15.1.1 CBT, as publisher of its White Pages, will include Primary Listings of CLEC’s resale directory customers in its White Pages, and shall cause its publisher to include primary listings of CLEC’s directory customers in its Publisher’s Yellow Pages Directories under the following terms and conditions:

  • STUDENT DIRECTORY INFORMATION Upon enrolling in the Dual Credit program, each Student’s general directory information (defined by the College, pursuant to FERPA, to exclude student addresses) will become part of the College’s student general directory information, and will be subject to the Texas Public Information Act.

  • AIN Selective Carrier Routing for Operator Services, Directory Assistance and Repair Centers 4.3.1 BellSouth will provide AIN Selective Carrier Routing at the request of <<customer_name>>. AIN Selective Carrier Routing will provide <<customer_name>> with the capability of routing operator calls, 0+ and 0- and 0+ NPA (LNPA) 555-1212 directory assistance, 1+411 directory assistance and 611 repair center calls to pre-selected destinations.

  • Red Hat Enterprise Linux Server Add-Ons Red Hat Enterprise Linux Server Subscriptions may be purchased with one or more add-on options (“Add-On(s)”). Add-Ons require a separate paid and active Software Subscriptions for each Unit that deploys, installs, uses or executes such Add-On. Each Unit of Add- Ons must match the Support Level (Standard and/or Premium), Unit of Measure and capacity as the underlying Red Hat Enterprise Linux Unit. Add-Ons are not supported on Red Hat Enterprise Linux Subscriptions with a Self-support service level except Smart Management Add-Ons. The Add-Ons include: High Availability, Load Balancer, Resilient Storage, Scalable File System, Smart Management, Extended Update Support, Extended Life Cycle Support and High Performance Network.

  • Custom Branding for Directory Assistance (DA) is not available for certain classes of service, including but not limited to Hotel/Motel services, WATS service, and certain PBX services.

Time is Money Join Law Insider Premium to draft better contracts faster.