| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/python3-requests-toolbelt/ |
| H A D | 720240501dca0b4eacc3295665d7ced8719e11d2.patch | 32 - "Connection": "keep-alive",
41 + "keep-alive"
55 - "Connection": "keep-alive",
68 + "keep-alive"
102 - "Connection": "keep-alive",
111 + "keep-alive"
125 - "Connection": "keep-alive",
138 + "keep-alive"
172 - "Connection": "keep-alive",
181 + "keep-alive"
[all …]
|
| H A D | 090856f4159c40a2927fb88546419f2e1697ad5f.patch | 92 …alive"], "Server": ["nginx"], "Set-Cookie": ["cookie0=value0; Path=/"], "Content-Type": ["text/htm…
111 + "keep-alive"
133 + "keep-alive"
176 + "keep-alive"
201 + "keep-alive"
232 …alive\", \n \"Host\": \"http2bin.org\", \n \"User-Agent\": \"python-requests/2.5.3 CPython/2…
251 + "keep-alive"
263 …n \"Accept-Encoding\": \"gzip, deflate\", \n \"Connection\": \"keep-alive\", \n \"Host\":…
273 + "keep-alive"
304 …alive"], "date": ["Sat, 03 May 2014 17:23:06 GMT"], "access-control-allow-origin": ["*"], "www-aut…
[all …]
|
| /openbmc/qemu/qapi/ |
| H A D | sockets.json | 61 # @keep-alive: enable keep-alive when connecting to/listening on this socket.
64 # @keep-alive-count: number of keep-alive packets sent before the connection is
69 # @keep-alive-idle: time in seconds the connection needs to be idle before
75 # @keep-alive-interval: time in seconds between keep-alive packets. Only
91 '*keep-alive': 'bool',
92 '*keep-alive-count': { 'type': 'uint32', 'if': 'HAVE_TCP_KEEPCNT' },
93 '*keep-alive-idle': { 'type': 'uint32', 'if': 'HAVE_TCP_KEEPIDLE' },
94 '*keep-alive-interval': { 'type': 'uint32', 'if': 'HAVE_TCP_KEEPINTVL' },
|
| /openbmc/openbmc/poky/meta/recipes-connectivity/kea/files/ |
| H A D | fix_pid_keactrl.patch | 26 - # Use ps to check if PID is alive
28 + # Use pgrep and grep to check if PID is alive
30 # No error, so PID IS ALIVE
|
| /openbmc/u-boot/tools/binman/test/files/ |
| H A D | 2.dat | 1 Oh, don't bother apologising, I'm sorry you're alive
|
| /openbmc/u-boot/board/avionic-design/common/ |
| H A D | tamonten-ng.c | 43 /* Turn on the alive signal */ in gpio_early_init()
44 gpio_request(TEGRA_GPIO(V, 2), "ALIVE"); in gpio_early_init()
|
| /openbmc/qemu/util/ |
| H A D | qemu-sockets.c | 226 "Unable to set keep-alive option on socket"); in inet_set_sockopts()
236 "Unable to set TCP keep-alive count option on socket"); in inet_set_sockopts()
248 "Unable to set TCP keep-alive idle option on socket"); in inet_set_sockopts()
260 "Unable to set TCP keep-alive interval option on socket"); in inet_set_sockopts()
674 .name = "keep-alive",
679 .name = "keep-alive-count",
685 .name = "keep-alive-idle",
691 .name = "keep-alive-interval",
756 if (qemu_opt_find(opts, "keep-alive")) { in inet_parse()
758 addr->keep_alive = qemu_opt_get_bool(opts, "keep-alive", false); in inet_parse()
[all …]
|
| /openbmc/phosphor-host-ipmid/ |
| H A D | systemintfcmds.hpp | 11 // Major command for the heartbeat operation (verify host is alive)
|
| /openbmc/qemu/tests/qemu-iotests/tests/ |
| H A D | iothreads-nbd-export.out | 18 Checking that it is still alive...
|
| H A D | iothreads-nbd-export | 62 iotests.log('Checking that it is still alive...')
|
| /openbmc/u-boot/arch/arm/cpu/armv8/ |
| H A D | cpu-dt.c | 25 /* secure code lives in RAM, keep it alive */ in psci_update_dt()
|
| /openbmc/qemu/tests/unit/ |
| H A D | test-util-sockets.c | 503 "[::1]:5000,numeric=on,to=5006,ipv4=off,ipv6=on,keep-alive=on" in test_inet_parse_all_options_good()
505 ",keep-alive-count=10" in test_inet_parse_all_options_good()
508 ",keep-alive-idle=60" in test_inet_parse_all_options_good()
511 ",keep-alive-interval=30" in test_inet_parse_all_options_good()
542 "[::1]:5000,numeric,to=5006,ipv4,ipv6,keep-alive" in test_inet_parse_all_implicit_bool_good()
|
| /openbmc/u-boot/test/py/tests/ |
| H A D | test_net.py | 119 is pinged. The test validates that the host is alive, as reported by the
127 assert 'is alive' in output
|
| /openbmc/u-boot/board/egnite/ethernut5/ |
| H A D | ethernut5_pwrman.h | 36 /* Features, which are not essential to keep u-boot alive */
|
| /openbmc/qemu/python/qemu/utils/ |
| H A D | qemu_ga_client.py | 79 raise EnvironmentError('Agent seems not alive')
238 alive = client.ping(timeout)
239 if not alive:
|
| /openbmc/bmcweb/redfish-core/include/registries/ |
| H A D | heartbeat_event_message_registry.hpp | 32 …"This registry defines the messages to use for periodic heartbeat, also known as 'keep alive', eve…
|
| /openbmc/u-boot/arch/arm/cpu/armv7/ |
| H A D | virt-dt.c | 64 /* secure code lives in RAM, keep it alive */ in psci_update_dt()
|
| /openbmc/u-boot/doc/ |
| H A D | README.dns | 46 host 64.233.161.104 is alive
|
| /openbmc/openbmc/poky/scripts/ |
| H A D | clean-hashserver-database | 8 ALIVE_DB_MARK="alive"
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/State/BMC/ |
| H A D | Redundancy.interface.yaml | 90 to let the sibling BMC interface daemon know it is alive.
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/installed/ |
| H A D | ManagerNetworkProtocol_v1.xml | 149 … time interval, in seconds, between transmissions of the multicast NOTIFY ALIVE message from this …
150 …ALIVE message. A setting of 0 seconds shall disable this functionality. The recommended value is…
240 …MulticastIntervalSeconds` to `0` impacts other NOTIFY usage beyond NOTIFY ALIVE. It was also crea…
300 …MulticastIntervalSeconds` to `0` impacts other NOTIFY usage beyond NOTIFY ALIVE. It was also crea…
383 …MulticastIntervalSeconds` to `0` impacts other NOTIFY usage beyond NOTIFY ALIVE. It was also crea…
439 …MulticastIntervalSeconds` to `0` impacts other NOTIFY usage beyond NOTIFY ALIVE. It was also crea…
491 …MulticastIntervalSeconds` to `0` impacts other NOTIFY usage beyond NOTIFY ALIVE. It was also crea…
750 …MulticastIntervalSeconds` to `0` impacts other NOTIFY usage beyond NOTIFY ALIVE. It was also crea…
796 …MulticastIntervalSeconds` to `0` impacts other NOTIFY usage beyond NOTIFY ALIVE. It was also crea…
822 …MulticastIntervalSeconds` to `0` impacts other NOTIFY usage beyond NOTIFY ALIVE. It was also crea…
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/csdl/ |
| H A D | ManagerNetworkProtocol_v1.xml | 149 … time interval, in seconds, between transmissions of the multicast NOTIFY ALIVE message from this …
150 …ALIVE message. A setting of 0 seconds shall disable this functionality. The recommended value is…
240 …MulticastIntervalSeconds` to `0` impacts other NOTIFY usage beyond NOTIFY ALIVE. It was also crea…
300 …MulticastIntervalSeconds` to `0` impacts other NOTIFY usage beyond NOTIFY ALIVE. It was also crea…
383 …MulticastIntervalSeconds` to `0` impacts other NOTIFY usage beyond NOTIFY ALIVE. It was also crea…
439 …MulticastIntervalSeconds` to `0` impacts other NOTIFY usage beyond NOTIFY ALIVE. It was also crea…
491 …MulticastIntervalSeconds` to `0` impacts other NOTIFY usage beyond NOTIFY ALIVE. It was also crea…
750 …MulticastIntervalSeconds` to `0` impacts other NOTIFY usage beyond NOTIFY ALIVE. It was also crea…
796 …MulticastIntervalSeconds` to `0` impacts other NOTIFY usage beyond NOTIFY ALIVE. It was also crea…
822 …MulticastIntervalSeconds` to `0` impacts other NOTIFY usage beyond NOTIFY ALIVE. It was also crea…
[all …]
|
| /openbmc/gpioplus/src/gpioplus/ |
| H A D | event.hpp | 61 * provided inputs while this event is alive.
|
| /openbmc/ipmitool/src/plugins/lanplus/ |
| H A D | README.sol | 54 Periodic dispatch of "keep alive" packet to the BMC.
|
| /openbmc/docs/architecture/ |
| H A D | optionality.md | 36 include, Http keep alive, Security features like timeouts and payload size
|