Home
last modified time | relevance | path

Searched refs:lock (Results 1726 – 1750 of 1782) sorted by relevance

1...<<61626364656667686970>>...72

/freebsd/contrib/sqlite3/
H A Daclocal.m41295 [AC_ARG_ENABLE([libtool-lock],
1296 [AS_HELP_STRING([--disable-libtool-lock],
1583 [Whether to use a lock for old archive extraction])
2122 # Check to see if we can do hard links to lock some files if needed
2131 AC_MSG_CHECKING([if we can lock with hard links])
2146 _LT_DECL([], [need_locks], [1], [Must we lock files when doing compilation?])
H A Dltmain.sh3547 lockfile=$output_obj.lock
/freebsd/contrib/jemalloc/src/
H A Dctl.c2999 MUTEX_PROF_RESET(bin->lock); in stats_mutexes_reset_ctl()
/freebsd/contrib/llvm-project/clang/include/clang/Basic/
H A DDiagnosticGroups.td518 def ModuleLock : DiagGroup<"module-lock">;
H A DAttr.td3566 // of a successful lock acquisition.
3579 // of a successful lock acquisition.
/freebsd/contrib/sendmail/
H A DRELEASE_NOTES698 If sendmail could not lock the statistics file due to a system
2112 stale lockfile (which is ignored after the lock timeout).
2890 LIBSMDB: Fix a lock race condition that affects makemap, praliases,
6323 If the system lock table is full, only attempt to create a new
6478 mailbox lock. Patch from Randall S. Winchester of the
6725 an exclusive lock already set -- i.e., almost all systems
7049 connect many times, and thereby lock out queue runs as well
7965 lock file) per connection, so you may have to reduce
9455 MAKEMAP: lock database file while rebuilding to avoid sendmail
9457 condition between the open(... O_TRUNC ...) and the lock
[all …]
/freebsd/contrib/ntp/
H A DChangeLog2576 * One more lock-while-init in lib/isc/task.c to quiet lock analysis.
3159 * [Bug 1518] Windows ntpd should lock to one processor more
3673 * [Bug 1518] Windows ntpd should lock to one processor more
4770 * [Bug 778] ntpd fails to lock with drift=+500 when started with drift=-500.
/freebsd/contrib/unbound/
H A DMakefile.in335 lock-verify$(EXEEXT) memstats$(EXEEXT) perf$(EXEEXT) \
398 lock-verify$(EXEEXT): $(LOCKVERIFY_OBJ_LINK)
H A Dltmain.sh3455 lockfile=$output_obj.lock
/freebsd/contrib/dialog/
H A DCHANGES2060 eliminating lock-files. Only one process should be trying to display
2177 + revised lock-file management to better ensure that locks are actually
/freebsd/sys/contrib/dev/athk/ath11k/
H A Dmac.c8728 read_lock_bh(&idev->lock); in ath11k_mac_op_ipv6_changed()
8779 read_unlock_bh(&idev->lock); in ath11k_mac_op_ipv6_changed()
/freebsd/contrib/ntp/ntpd/
H A Dinvoke-ntp.conf.texi2813 -1 means "do not lock the process into memory".
2814 0 means "lock whatever memory the process wants into memory".
H A Dntp.conf.def3011 -1 means "do not lock the process into memory".
3012 0 means "lock whatever memory the process wants into memory".
/freebsd/crypto/heimdal/
H A DChangeLog.20051966 application must global lock the library, it it uses threads that
/freebsd/crypto/openssl/
H A DNEWS.md303 * The public and private DRBG instance are per thread for lock free
/freebsd/contrib/llvm-project/lldb/source/Plugins/Process/gdb-remote/
H A DProcessGDBRemote.cpp3456 std::shared_ptr<ProcessGDBRemote> process_sp = process_wp.lock(); in MonitorDebugserverProcess()
/freebsd/sys/dev/bnxt/bnxt_en/
H A Dif_bnxt.c1622 mutex_init(&bp->fw_health->lock); in __bnxt_alloc_fw_health()
/freebsd/contrib/file/
H A Dltmain.sh3458 lockfile=$output_obj.lock
/freebsd/contrib/openbsm/config/
H A Dltmain.sh3455 lockfile=$output_obj.lock
/freebsd/contrib/ldns/
H A Dltmain.sh3547 lockfile=$output_obj.lock
/freebsd/contrib/ntp/sntp/libevent/build-aux/
H A Dltmain.sh3455 lockfile=$output_obj.lock
/freebsd/contrib/ntp/sntp/libevent/
H A Dltmain.sh3455 lockfile=$output_obj.lock
/freebsd/contrib/openpam/
H A Dltmain.sh3708 lockfile=$output_obj.lock
/freebsd/contrib/libevent/build-aux/
H A Dltmain.sh3669 lockfile=$output_obj.lock
/freebsd/usr.sbin/services_mkdb/
H A Dservices1833 lockd 4045/udp # NFS lock daemon/manager

1...<<61626364656667686970>>...72