| /openbmc/qemu/hw/misc/ |
| H A D | pvpanic.c | 28 static bool logged; in handle_event() local 30 if (event & ~PVPANIC_EVENTS && !logged) { in handle_event() 32 logged = true; in handle_event()
|
| /openbmc/phosphor-power/phosphor-regulators/docs/ |
| H A D | phase_fault_monitoring.md | 10 detected, an error is logged on the BMC. 16 an error is logged. This provides "de-glitching" to ignore transient hardware 19 A phase fault error will only be logged for a regulator once per system boot. 34 - The error will be logged. If the same error occurs repeatedly on regulator, it 35 will only be logged once per system boot.
|
| H A D | sensor_monitoring.md | 56 - The error will be logged. If the same error occurs repeatedly on a rail, it 57 will only be logged once per system boot.
|
| H A D | configuration.md | 50 - The error will be logged.
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/uw-imap/uw-imap/ |
| H A D | imap-2007f-format-security.patch | 16 - if (!logged++) syslog (LOG_ERR,tmp); 17 + if (!logged++) syslog (LOG_ERR, "%s", tmp);
|
| /openbmc/openbmc/poky/meta/lib/oeqa/selftest/cases/ |
| H A D | runqemu.py | 58 self.assertTrue(qemu.runner.logged, "Failed: %s, %s" % (cmd, f.read())) 82 self.assertTrue(qemu.runner.logged, "Failed: %s, %s" % (cmd, f.read())) 108 self.assertTrue(qemu.runner.logged, "Failed: %s, %s" % (cmd, f.read())) 142 self.assertTrue(qemu.runner.logged, "Failed: %s, %s" % (cmd, f.read())) 153 self.assertTrue(qemu.runner.logged, "Failed: %s, %s" % (cmd, f.read()))
|
| H A D | efibootpartition.py | 34 self.assertTrue(qemu.runner.logged, "Failed: %s" % cmd)
|
| H A D | uki.py | 60 self.assertTrue(qemu.runner.logged, "Failed: %s" % cmd)
|
| /openbmc/u-boot/test/py/ |
| H A D | u_boot_utils.py | 289 logged = False 294 if not logged: 297 logged = True
|
| /openbmc/phosphor-power/phosphor-regulators/docs/config_file/ |
| H A D | phase_fault_detection.md | 12 error should be logged warning the user that the regulator has lost redundancy. 19 detected two consecutive times (15 seconds apart) before an error is logged. 22 Phase faults are detected and logged by executing actions:
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-connectivity/gammu/gammu/ |
| H A D | gammu-smsdrc | 36 # File (or stderr, syslog, eventlog) where information will be logged 38 # Amount of information being logged, each bit mean one level
|
| /openbmc/docs/designs/ |
| H A D | redfish-resource-supplement-for-pfr.md | 46 - Event logs should be logged to redfish for Platform Firmware Resilience. 95 Below type of events should be logged as part of PFR or provisioning. These 109 Below are some cases, where firmware resiliency error events logged for 123 Below are some cases, where these events can be logged. 136 Below are few cases, where these events can be logged.
|
| /openbmc/phosphor-power/phosphor-power-sequencer/docs/ |
| H A D | pgood_faults.md | 84 If those requirements are not met, a general pgood error will be logged. 102 If a specific voltage rail is found, an error is logged against that rail. 105 application found a power supply error, then the power supply error is logged as 108 If no voltage rail is found, a general pgood error is logged.
|
| /openbmc/phosphor-fan-presence/docs/monitor/ |
| H A D | fan_missing_error_delay.md | 7 logged when the fan is not present when the attribute is not given.
|
| H A D | nonfunc_rotor_error_delay.md | 7 defaults to **no error** being logged when the attribute is not given and a
|
| /openbmc/openbmc-test-automation/lib/ |
| H A D | esel_utils.robot | 41 [Documentation] Count eSEL entries logged. 50 [Documentation] Verify eSEL entries logged.
|
| /openbmc/openbmc/meta-security/recipes-scanners/clamav/files/ |
| H A D | clamav-milter.conf.sample | 259 # This option allows to tune what is logged when a message is infected. 260 # Possible values are Off (the default - nothing is logged), 261 # Basic (minimal info logged), Full (verbose info logged) 273 # This option allows to tune what is logged when no threat is found in a scanned message. 286 # then one line is logged for each recipient and the command indicated
|
| /openbmc/openbmc/poky/meta/recipes-connectivity/ppp/ppp/ |
| H A D | pap | 11 # It will be logged to stderr or to the file specified with the -r chat option.
|
| /openbmc/openbmc/poky/meta/recipes-core/busybox/busybox/ |
| H A D | 0001-syslogd-fix-wrong-OPT_locallog-flag-detection.patch | 9 is more-less unusable while no messages are logged locally.
|
| /openbmc/openbmc/poky/meta/recipes-extended/wget/ |
| H A D | wget.inc | 4 non-interactively, so it will work in the background, after having logged off. \
|
| /openbmc/docs/ |
| H A D | console.md | 21 If you're already logged into an OpenBMC machine, you can start a console
|
| /openbmc/openbmc-test-automation/redfish/systems/LogServices/ |
| H A D | test_post_codes.robot | 23 [Documentation] Boot the system and verify PostCodes from host are logged. 37 [Documentation] Initiate Host reboot the system and verify PostCodes from host are logged. 55 [Documentation] Power off the system and verify PostCodes from host are logged.
|
| /openbmc/openbmc-test-automation/docs/ |
| H A D | redfish_coding_guidelines.md | 88 # Run 'Some Keyword' while logged in as ${LDAP_USER}/${LDAP_USER_PASSWORD}. 119 setting things right (i.e. back to a logged in state).
|
| /openbmc/docs/architecture/ |
| H A D | redfish-logging-in-bmcweb.md | 83 be logged to the journal as follows: 133 this message can be logged to the journal as follows:
|
| /openbmc/openbmc/poky/meta/recipes-extended/tcp-wrappers/tcp-wrappers-7.6/ |
| H A D | 12_makefile_config.patch | 30 # The syslog priority at which successful connections are logged.
|