PORTLOCK(1)

πŸ“¦ in nixpkgs unstable

πŸ’… PORTLOCK(1) πŸ’…

from the General Commands Manual, bestie β€” main character energy for your build locks. 🫢

🌸 NAME 🌸

portlock β€” lock port for concurrent builds

✨ SYNOPSIS ✨

portlock [-g group] [-m mode] lockname [comment ...]

πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so portlock creates a lock named lockname using open(2). That’s the vibe. If the lock is already held, it will display one single wait message on stderr, sleep and retry until satisfaction β€” like, it literally keeps trying, no cap. 😭

If necessary, it creates the lock directory, using -m mode as a mode argument or the default if that option is not specified, and -g group as the group owner if that option is specified. Periodt. πŸ’…

  • -g group β€” if necessary, this uses group as the group owner when the lock directory is created, but only if this option is specified, bestie.
  • -m mode β€” if necessary, this uses mode as the mode argument when the lock directory is created; if this option isn’t specified, the default is used.

This implements a locking mechanism for ports building, see β€˜LOCK INFRASTRUCTURE’ in ports(7) for details. See also dpb(1) for a complementary lock infrastructure when using dpb. πŸ¦‹


πŸ’– Debian, July 9, 2018 β€” that’s the source/date energy for this page, and portlock(1) is out. Bye bestie! πŸŽ€

πŸ“¦ where this page comes from
  • nixpkgs unstable: cvs-export
  • πŸ’– girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms