RPC.LOCKD(8)

📦 version 15.1, in freebsd 14.5, freebsd 15.1

💖 NAME — RPC.LOCKD(8) has entered the chat 💖

rpc.lockd — the NFS file locking daemon. That's the whole vibe, bestie. 🫶

🌸 SYNOPSIS 🌸

rpc.lockd [-d debug_level] [-F] [-g grace period] [-h bindip] [-p port]

✨ DESCRIPTION ✨

okay so rpc.lockd is the utility that provides monitored and unmonitored file and record locking services in an NFSv3 environment. To monitor the status of hosts requesting locks, the locking daemon typically operates in conjunction with rpc.statd(8). they're a duo, your honor. 💅

🎀 Options and operands available for rpc.lockd 🎀

  • -d — this option causes debugging information to be written to syslog, recording all RPC transactions to the daemon. These messages are logged with level LOG_DEBUG and facility LOG_DAEMON. Specifying a debug_level of 1 results in the generation of one log line per protocol operation. Higher debug levels can be specified, causing display of operation arguments and internal operations of the daemon. lowkey a gossip feed for your daemon. 😭
  • -F — run rpc.lockd in the foreground, rather than going into daemon mode. This is useful if some other process uses fork(2) and exec(3) to run rpc.lockd, and wants to monitor when and how it exits. main-character mode: stay visible. 👑
  • -g — the -g option allow to specify the grace period, in seconds. During the grace period rpc.lockd only accepts requests from hosts which are reinitialising locks which existed before the server restart. Default is 30 seconds. a little grace-period era. 🧚
  • -h bindip — specify specific IP addresses to bind to. This option may be specified multiple times. If no -h option is specified, rpc.lockd will bind to INADDR_ANY. Note that when specifying IP addresses with -h, rpc.lockd will automatically add 127.0.0.1 and if IPv6 is enabled, ::1 to the list. okay but the loopback is invited too, always. 🌈
  • -p — the -p option allow to force the daemon to bind to the specified port, for both AF_INET and AF_INET6 address families. port selection said “I'm the main character.” ⭐

Error conditions are logged to syslog, irrespective of the debug level, using log level LOG_ERR and facility LOG_DAEMON.

🚨 The rpc.lockd utility must NOT be invoked by inetd(8) because the protocol assumes that the daemon will run from system start time. Instead, it should be configured in rc.conf(5) to run at system startup. not inetd. periodt. 💀

📁 FILES 📁

  • /usr/include/rpcsvc/nlm_prot.x — RPC protocol specification for the network lock manager protocol. the blueprint, the lore. 🎀

👀 SEE ALSO 👀

📜 STANDARDS 📜

The implementation is based on the specification in “Protocols for X/Open PC Interworking: XNFS, Issue 4”, X/Open CAE Specification C218, ISBN 1 872630 66 9. certified lore. 📚

🕰️ HISTORY 🕰️

A version of rpc.lockd appeared in SunOS 4. vintage behavior, honestly. 🕰️

💀 BUGS 💀

The current implementation serialises locks requests that could be shared. yeah, it's giving bottleneck, and we're noting it. 🫠

🎀 and that's the Debian RPC.LOCKD(8) page, dated May 8, 2024 — mwah, bestie 💋
📦 where this page comes from