| /openbmc/qemu/tests/qemu-iotests/ |
| H A D | 182 | 52 _launch_qemu -drive file=$TEST_IMG,if=none,id=drive0,file.locking=on \ 58 -drive file=$TEST_IMG,if=none,id=drive0,file.locking=on \ 151 _launch_qemu -drive file=$TEST_IMG,if=none,file.locking=on
|
| H A D | 182.out | 6 QEMU_PROG: -drive file=TEST_DIR/t.qcow2,if=none,id=drive0,file.locking=on: Failed to get "write" lo… 18 'locking': 'on' 34 'locking': 'on'
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-extended/python3-portalocker/ |
| H A D | python3-portalocker_3.1.1.bb | 1 SUMMARY = "Cross-platform locking library" 2 DESCRIPTION = "Portalocker is a library to provide an easy API to file locking"
|
| /openbmc/u-boot/doc/ |
| H A D | README.N1213 | 24 - TLB locking support 36 - Cache locking support.
|
| H A D | README.NDS32 | 23 - Non-bus locking synchronization instructions.
|
| H A D | README.sched | 16 - There are NO primitives for thread synchronization (locking,
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
| H A D | python3-pid_3.0.4.bb | 1 SUMMARY = "Pidfile featuring stale detection and file-locking, can also \
|
| H A D | python3-lockfile_0.12.2.bb | 4 SUMMARY = "Platform-independent file locking module"
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-benchmark/lmbench/lmbench/ |
| H A D | 0001-doc-Fix-typos-in-manual-pages.patch | 37 lat_fcntl \- fcntl file locking benchmark 66 -lat_fcntl \- fcntl file locking benchmark
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-dbs/mysql/mariadb/ |
| H A D | my.cnf | 16 skip-external-locking
|
| /openbmc/docs/designs/ |
| H A D | estoraged.md | 71 different devices will have different command sets for device locking, e.g. 112 For eMMC devices, we plan to enable the password locking feature (CMD42), to 119 Support for hardware locking on other types of devices can be added as needed, 120 but at the very least, encryption-only locking will be available, even if 121 hardware locking isn't supported for a particular device. 125 and the device password (if hardware locking is available). The passwords will
|
| /openbmc/openbmc/poky/meta/recipes-support/libdaemon/ |
| H A D | libdaemon_0.14.bb | 4 as well as file locking to ensure that only a single copy of a given daemon \
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/procmail/procmail/ |
| H A D | from-debian-to-modify-parameters.patch | 105 -/*#define NO_flock_LOCK /* use of those kernel-locking methods */ 106 +#define NO_flock_LOCK /* use of those kernel-locking methods */ 109 if you want to disable particular locking styles but are unsure which
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/uw-imap/uw-imap/ |
| H A D | imap-2007f-format-security.patch | 14 sprintf (tmp,"File locking failure: %s",strerror (errno));
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/liblockfile/ |
| H A D | liblockfile_1.17.bb | 1 SUMMARY = "File locking library"
|
| /openbmc/qemu/docs/system/ |
| H A D | qemu-block-drivers.rst.inc | 866 Disk image file locking 876 File Descriptor (OFD) locking API, and can be configured to fall back to POSIX 877 locking if the POSIX host doesn't support Linux OFD locking. 879 To explicitly enable image locking, specify "locking=on" in the file protocol 880 driver options. If OFD locking is not possible, a warning will be printed and 881 the POSIX locking API will be used. In this case there is a risk that the lock 883 shortcomings of the POSIX locking API. 899 Alternatively, locking can be fully disabled by "locking=off" block device 901 "file.locking=off" as the protocol driver is normally placed as a "file" child 906 -blockdev driver=qcow2,file.filename=/path/to/image,file.locking=off,file.driver=file [all …]
|
| /openbmc/openbmc/poky/meta/recipes-graphics/wayland/weston-init/ |
| H A D | weston.ini | 15 #locking=true
|
| /openbmc/u-boot/doc/imx/common/ |
| H A D | imx5.txt | 36 After programming a MAC address, consider locking the MAC fuses. This is
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/sanlock/ |
| H A D | sanlock_4.0.0.bb | 3 to the storage can perform locking. An application running on the \
|
| /openbmc/openbmc/poky/meta/classes/ |
| H A D | extrausers.bbclass | 37 # Different from useradd.bbclass, there's no file locking issue here, as
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/User/ |
| H A D | README.md | 32 - MaxLoginAttemptBeforeLockout - Permissible attempt before locking out the user
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/memcached/ |
| H A D | memcached_1.6.38.bb | 4 to take advantage of its versatile no-locking memory access system. Clients \
|
| /openbmc/openbmc/meta-openembedded/meta-networking/files/waf-cross-answers/ |
| H A D | cross-answers-aarch64.txt | 31 Checking whether fcntl locking is available: OK
|
| H A D | cross-answers-mips64el.txt | 31 Checking whether fcntl locking is available: OK
|
| H A D | cross-answers-powerpc.txt | 32 Checking whether fcntl locking is available: OK
|