SaLogSeverityT and SaLogSeverityFlagsT 1‌‌ Sample Clauses

SaLogSeverityT and SaLogSeverityFlagsT 1‌‌. The SaLogSeverityT and SaLogSeverityFlagsT types are used to express severity in the context of applications and system log records and log streams. #define SA_LOG_SEV_EMERGENCY 0 #define SA_LOG_SEV_ALERT 1 #define SA_LOG_SEV_CRITICAL 2 #define SA_LOG_SEV_ERROR 3 10 #define SA_LOG_SEV_WARNING 4 #define SA_LOG_SEV_NOTICE 5 #define SA_LOG_SEV_INFO 6 typedef SaUint16T SaLogSeverityT; #define SA_LOG_SEV_FLAG_EMERGENCY 0x0001 20 #define SA_LOG_SEV_FLAG_ALERT 0x0002 #define SA_LOG_SEV_FLAG_CRITICAL 0x0004 #define SA_LOG_SEV_FLAG_ERROR 0x0008 #define SA_LOG_SEV_FLAG_WARNING 0x0010 25 #define SA_LOG_SEV_FLAG_NOTICE 0x0020 #define SA_LOG_SEV_FLAG_INFO 0x0040 typedef SaUint16T SaLogSeverityFlagsT; 30 The SaLogSeverityT type is used to specify the severity level of a particular system or application log record (see Section 3.4.5.3) when saLogWriteLog() or saLogWriteLogAsync() are invoked (see Section 3.6.3). The SaLogSeverityFlagsT type is a bitmap used in the SaLogFilterSetCallbackT call- 35 back (see Section 3.6.5). In this case, each SA_LOG_SEV_ value identifies a bit position in the SaLogSeverityFlagsT bitmap to allow (bit is 1) or disallow (bit is 0) log records of a particular severity on to the associated system or application log stream. These severity levels and flags have the following interpretation (see [13]): 40 • EMERGENCY - the system is unusable • ALERT - action must be taken immediately • CRITICAL - critical conditions 1 • ERROR - error conditions • WARNING - warning conditions • NOTICE - normal but significant condition 5 • INFO - informational messages
Sample 1
AutoNDA by SimpleDocs

Related to SaLogSeverityT and SaLogSeverityFlagsT 1‌‌

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • Vlastnictví Zdravotnické zařízení si ponechá a bude uchovávat Zdravotní záznamy. Zdravotnické zařízení a Zkoušející převedou na Zadavatele veškerá svá práva, nároky a tituly, včetně práv duševního vlastnictví k Důvěrným informacím (ve smyslu níže uvedeném) a k jakýmkoli jiným Studijním datům a údajům.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:

  • Electrical appliance safety The Hirer shall ensure that any electrical appliances brought by them to the premises and used there shall be safe, in good working order, and used in a safe manner in accordance with the Electricity at Work Regulations 1989. Where a residual circuit breaker is provided the hirer must make use of it in the interests of public safety.

  • Přetrvající platnost This Section 3 “

  • FLOODPLAIN MANAGEMENT AND WETLAND PROTECTION Executive Order 11988, Floodplain Management, May 24, 1977 (42 FR 26951), 3 C.F.R., 1977 Comp., p. 117, as interpreted in HUD regulations at 24 C.F.R. Part 55, particularly Section 2(a) of the Order (For an explanation of the relationship between the decision- making process in 24 C.F.R. Part 55 and this part, see § 55.10.); and Executive Order 11990, Protection of Wetlands, May 24, 1977 (42 FR 26961), 3 C.F.R., 1977 Comp., p. 121 particularly Sections 2 and 5. COASTAL ZONE MANAGEMENT The Coastal Zone Management Act of 1972 (16 U.S.C. § 1451, et seq.), as amended, particularly sections 307(c) and (d) (16 U.S.C. § 1456(c) and (d)).

  • Přetrvávající platnost Tento odstavec 1.3 “Zdravotní záznamy a Studijní data a údaje” zůstane závazný i v případě zániku platnosti či vypršení platnosti této Smlouvy.

  • Reactive Power and Primary Frequency Response 9.6.1 Power Factor Design Criteria

  • Synchronisation Commissioning and Commercial Operation 8.1 The Developer shall provide at least forty (40) days advanced preliminary written notice and at least twenty (20) days advanced final written notice to ESCOM of the date on which it intends to synchronize the Power Project to the Grid System.

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