Effect of Consents and Waivers Sample Clauses

Effect of Consents and Waivers. A consent to an amendment or a waiver by a Holder of a Note shall bind the Holder and every subsequent Holder of that Note or portion of the Note that evidences the same debt as the consenting Holder’s Note, even if notation of the consent or waiver is not made on the Note. After an amendment or waiver becomes effective, it shall bind every Holder unless it makes a change described in clauses (i) through (ix) of Section 9.2(a), in which case the amendment or waiver or other action shall bind each Holder who has consented to it and every subsequent Holder that evidences the same debt as the consenting Holder’s Notes. An amendment or waiver made pursuant to Section 9.2 shall become effective upon receipt by the Trustee of the requisite number of written consents. The Issuer may, but shall not be obligated to, fix a record date for the purpose of determining the Holders entitled to give their consent or take any other action described above or required or permitted to be taken pursuant to this Indenture. If a record date is fixed, then notwithstanding the immediately preceding paragraph, those Persons who were Holders at such record date (or their duly designated proxies), and only those Persons, shall be entitled to give such consent or to take any such action, whether or not such Persons continue to be Holders after such record date.
Sample 1Sample 2Sample 3See All (69)
AutoNDA by SimpleDocs
Effect of Consents and Waivers. A consent to an amendment, supplement or a waiver by a Holder of a Note shall bind the Holder and every subsequent Holder of that Note or portion of the Note that evidences the same debt as the consenting Holder’s Note, even if notation of the consent or waiver is not made on the Note. After an amendment or waiver becomes effective with respect to the Notes, it shall bind every Noteholder. The Company may, but shall not be obligated to, fix a record date for the purpose of determining the Noteholders entitled to give their consent or take any other action described above or required or permitted to be taken pursuant to this Indenture. If a record date is fixed, then notwithstanding the immediately preceding paragraph, those Persons who were Noteholders at such record date (or their duly designated proxies), and only those Persons, shall be entitled to give such consent or to take any such action, whether or not such Persons continue to be Holders after such record date.
Sample 1Sample 2Sample 3See All (42)
Effect of Consents and Waivers. A consent to an amendment or a waiver by a Holder of a Note will bind the Holder and every subsequent Holder of that Note or portion of the Note that evidences the same debt as the consenting Holder’s Note, even if notation of the consent or waiver is not made on the Note. After an amendment or waiver becomes effective, it will bind every Holder unless it makes a change described in clauses (i) through (ix) of Section 9.2(a), in which case the amendment or waiver or other action will bind each Holder who has consented to it and every subsequent Holder that evidences the same debt as the consenting Holder’s Notes. An amendment or waiver made pursuant to Section 9.2 will become effective upon receipt by the Trustee of the requisite number of written consents.
Sample 1
Effect of Consents and Waivers. No express or implied consent to, or waiver of, any default of Grantor by Grantee shall be construed as a consent to, or waiver of, any other default. No consent to, or waiver of, any default or any other indulgence, shall be effective unless expressed in writing by Grantee. Grantor agrees for itself, its successors and assigns, that the acceptance, before the expiration of the right of redemption and after the commencement of foreclosure proceedings of this Mortgage, of insurance proceeds, eminent domain awards, rents or anything else of value to be applied on or to the mortgage indebtedness by Grantee or any person or party holding under it shall not constitute a waiver of such foreclosure, and this agreement by Grantor shall be that agreement referred to in Section 6204 of Title 14 of the Maine Revised Statutes of 1964 as necessary to prevent such waiver of foreclosure. This agreement by Grantor is intended to apply to the acceptance and such application of any such proceeds, awards, rents, and other sums or anything else of value whether the same shall be accepted from, or for the account of, Grantor or from any other source whatsoever by Grantee or by any person or party holding under Grantee at any time or times in the future while any of the Obligations secured hereby shall remain outstanding.
Sample 1
Effect of Consents and Waivers. Except as expressly amended hereby, this Agreement and the Loan Documents shall be and remain in full force and effect. The consents and waivers granted herein are specific and limited and shall not constitute a modification, acceptance or waiver of any other provision of or Default under this Agreement, the Loan Documents or any other document or instrument entered into in connection herewith or therewith or a future modification, acceptance or waiver of the provisions set forth herein and therein (except to the extent necessary to give effect to the specific consents and waivers set forth herein).
Sample 1
Effect of Consents and Waivers. Upon the execution and delivery of the Consents and Waivers by the holders of Senior Debt, no event of default or event which, with the giving of notice, the lapse of time or both, would become an event of default shall exist under any agreement, instrument or other document evidencing Senior Debt or relating thereto.
Sample 1

Related to Effect of Consents and Waivers

  • Revocation and Effect of Consents Until an amendment, supplement or waiver becomes effective, a consent to it by a Holder of a Note is a continuing consent by the Holder of a Note and every subsequent Holder of a Note or portion of a Note that evidences the same debt as the consenting Holder's Note, even if notation of the consent is not made on any Note. However, any such Holder of a Note or subsequent Holder of a Note may revoke the consent as to its Note if the Trustee receives written notice of revocation before the date the waiver, supplement or amendment becomes effective. An amendment, supplement or waiver becomes effective in accordance with its terms and thereafter binds every Holder.

  • Amendments and Waivers (a) If the ICANN Board of Directors determines that an amendment to this Agreement (including to the Specifications referred to herein) and all other registry agreements between ICANN and the Applicable Registry Operators (the “Applicable Registry Agreements”) is desirable (each, a “Special Amendment”), ICANN may adopt a Special Amendment pursuant to the requirements of and process set forth in this Section 7.6; provided that a Special Amendment may not be a Restricted Amendment. (b) Prior to submitting a Special Amendment for Registry Operator Approval, ICANN shall first consult in good faith with the Working Group regarding the form and substance of such Special Amendment. The duration of such consultation shall be reasonably determined by ICANN based on the substance of the Special Amendment. Following such consultation, ICANN may propose the adoption of a Special Amendment by publicly posting such amendment on its website for no less than thirty (30) calendar days (the “Posting Period”) and providing notice of such proposed amendment to the Applicable Registry Operators in accordance with Section 7.9. ICANN will consider the public comments submitted on a Special Amendment during the Posting Period (including comments submitted by the Applicable Registry Operators). (c) If, within one hundred eighty (180) calendar days following the expiration of the Posting Period (the “Approval Period”), the ICANN Board of Directors approves a Special Amendment (which may be in a form different than submitted for public comment, but must address the subject matter of the Special Amendment posted for public comment, as modified to reflect and/or address input from the Working Group and public comments), ICANN shall provide notice of, and submit, such Special Amendment for approval or disapproval by the Applicable Registry Operators. If, during the sixty (60) calendar day period following the date ICANN provides such notice to the Applicable Registry Operators, such Special Amendment receives Registry Operator Approval, such Special Amendment shall be deemed approved (an “Approved Amendment”) by the Applicable Registry Operators, and shall be effective and deemed an amendment to this Agreement on the date that is sixty (60) calendar days following the date ICANN provided notice of the approval of such Approved Amendment to Registry Operator (the “Amendment Effective Date”). In the event that a Special Amendment does not receive Registry Operator Approval, the Special Amendment shall be deemed not approved by the Applicable Registry Operators (a “Rejected Amendment”). A Rejected Amendment will have no effect on the terms and conditions of this Agreement, except as set forth below. (d) If the ICANN Board of Directors reasonably determines that a Rejected Amendment falls within the subject matter categories set forth in Section 1.2 of Specification 1, the ICANN Board of Directors may adopt a resolution (the date such resolution is adopted is referred to herein as the “Resolution Adoption Date”) requesting an Issue Report (as such term is defined in ICANN’s Bylaws) by the Generic Names Supporting Organization (the “GNSO”) regarding the substance of such Rejected Amendment. The policy development process undertaken by the GNSO pursuant to such requested Issue Report is referred to herein as a “PDP.” If such PDP results in a Final Report supported by a GNSO Supermajority (as defined in ICANN’s Bylaws) that either (i) recommends adoption of the Rejected Amendment as Consensus Policy or (ii) recommends against adoption of the Rejected Amendment as Consensus Policy, and, in the case of (i) above, the Board adopts such Consensus Policy, Registry Operator shall comply with its obligations pursuant to Section 2.2 of this Agreement. In either case, ICANN will abandon the Rejected Amendment and it will have no effect on the terms and conditions of this Agreement. Notwithstanding the foregoing provisions of this Section 7.6(d), the ICANN Board of Directors shall not be required to initiate a PDP with respect to a Rejected Amendment if, at any time in the twelve (12) month period preceding the submission of such Rejected Amendment for Registry Operator Approval pursuant to Section 7.6(c), the subject matter of such Rejected Amendment was the subject of a concluded or otherwise abandoned or terminated PDP that did not result in a GNSO Supermajority recommendation. (e) If (a) a Rejected Amendment does not fall within the subject matter categories set forth in Section 1.2 of Specification 1, (b) the subject matter of a Rejected Amendment was, at any time in the twelve (12) month period preceding the submission of such Rejected Amendment for Registry Operator Approval pursuant to Section 7.6(c), the subject of a concluded or otherwise abandoned or terminated PDP that did not result in a GNSO Supermajority recommendation, or (c) a PDP does not result in a Final Report supported by a GNSO Supermajority that either (A) recommends adoption of the Rejected Amendment as Consensus Policy or (B) recommends against adoption of the Rejected Amendment as Consensus Policy (or such PDP has otherwise been abandoned or terminated for any reason), then, in any such case, such Rejected Amendment may still be adopted and become effective in the manner described below. In order for the Rejected Amendment to be adopted, the following requirements must be satisfied: (i) the subject matter of the Rejected Amendment must be within the scope of ICANN’s mission and consistent with a balanced application of its core values (as described in ICANN’s Bylaws); (ii) the Rejected Amendment must be justified by a Substantial and Compelling Reason in the Public Interest, must be likely to promote such interest, taking into account competing public and private interests that are likely to be affected by the Rejected Amendment, and must be narrowly tailored and no broader than reasonably necessary to address such Substantial and Compelling Reason in the Public Interest; (iii) to the extent the Rejected Amendment prohibits or requires conduct or activities, imposes material costs on the Applicable Registry Operators, and/or materially reduces public access to domain name services, the Rejected Amendment must be the least restrictive means reasonably available to address the Substantial and Compelling Reason in the Public Interest; (iv) the ICANN Board of Directors must submit the Rejected Amendment, along with a written explanation of the reasoning related to its determination that the Rejected Amendment meets the requirements set out in subclauses (i) through (iii) above, for public comment for a period of no less than thirty (30) calendar days; and (v) following such public comment period, the ICANN Board of Directors must (a) engage in consultation (or direct ICANN management to engage in consultation) with the Working Group, subject matter experts, members of the GNSO, relevant advisory committees and other interested stakeholders with respect to such Rejected Amendment for a period of no less than sixty (60) calendar days; and (b) following such consultation, reapprove the Rejected Amendment (which may be in a form different than submitted for Registry Operator Approval, but must address the subject matter of the Rejected Amendment, as modified to reflect and/or address input from the Working Group and public comments) by the affirmative vote of at least two-­‐thirds of the members of the ICANN Board of Directors eligible to vote on such matter, taking into account any ICANN policy affecting such eligibility, including ICANN’s Conflict of Interest Policy (a “Board Amendment”). Such Board Amendment shall, subject to Section 7.6(f), be deemed an Approved Amendment, and shall be effective and deemed an amendment to this Agreement on the date that is sixty (60) calendar days following the date ICANN provided notice of the approval of such Board Amendment to Registry Operator (which effective date shall be deemed the Amendment Effective Date hereunder). Notwithstanding the foregoing, a Board Amendment may not amend the registry fees charged by ICANN hereunder, or amend this Section 7.6. (f) Notwithstanding the provisions of Section 7.6(e), a Board Amendment shall not be deemed an Approved Amendment if, during the thirty (30) calendar day period following the approval by the ICANN Board of Directors of the Board Amendment, the Working Group, on the behalf of the Applicable Registry Operators, submits to the ICANN Board of Directors an alternative to the Board Amendment (an “Alternative Amendment”) that meets the following requirements: (i) sets forth the precise text proposed by the Working Group to amend this Agreement in lieu of the Board Amendment; (ii) addresses the Substantial and Compelling Reason in the Public Interest identified by the ICANN Board of Directors as the justification for the Board Amendment; and (iii) compared to the Board Amendment is: (a) more narrowly tailored to address such Substantial and Compelling Reason in the Public Interest, and (b) to the extent the Alternative Amendment prohibits or requires conduct or activities, imposes material costs on Affected Registry Operators, or materially reduces access to domain name services, is a less restrictive means to address the Substantial and Compelling Reason in the Public Interest. Any proposed amendment that does not meet the requirements of subclauses (i) through

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!