cvslock(1)

💖 NAME 💖

cvslock — lock CVS repositories. Welcome to the cvslock(1) User Manuals page, bestie 💅

✨ SYNOPSIS ✨

cvslock [-q] [-p pid] [-d CVS root] [-R|-W] [-u|-s|-c Command] [-l]
directory

🎀 DESCRIPTION 🎀

okay so cvslock is used to lock a tree starting at directory in your CVS repository during low-level manipulation or inspection. It’s giving careful-queen energy 🧚.

There are various modes of operation: you can use the -s or -c options to cause cvslock to spawn a sub-shell or a shell command from which you can safely access the source repository. Very “you’re safe in my arms” 💖.

You can also use cvslock to lock and unlock CVS repositories from shell scripts; in this case you’ll want to use the -p option to specify the process ID which is written to the lock files’ names. Script girlies know 🫶.

The default when given no options is to acquire a persistant read lock. That’s literally the default, no cap.

🌸 OPTIONS 🌸

• -q — tells cvslock to shut up and not print any diagnostic messages to stdout. This is most useful when using the program in conjunction with, e.g., rsync(1). Silent treatment but make it useful ✨.
• -p pid — the CVS lock files generated by this utility have the current process ID in their name to distinguish them from lock files generated by other tools such as cvs itself or concurrent sessions of cvslock. Use this option to force cvslock to use a specific pid. This is in most useful from shell scripts 🐚.
• -d CVS root — this optional argument tells cvslock where your CVS repository’s root is. If no -d switch is given, cvslock will fall back to the CVSROOT environment variable. Note that cvslock only works on local repositories, so don’t try to access pserver or rsh-accessible remote repositories this way. Local only, bestie — no remote delusions 🙈.
• -R — this switch tells cvslock to acquire a lock for safe reading of the repository.
• -W — this switch tells cvslock to acquire a write lock on the repository.
• -s — when invoked with this option, cvslock will invoke the user’s login shell as determined by the SHELL environment variable after locking the repository. After the user has left that shell, cvslock will drop the locks. Shell nap time, then cleanup 🐚.
• -c Command — this option is similar to the -s option, with the difference that cvslock will execute the shell command given on the command line instead of giving the user an interactive shell.
• -u — when given this option, cvslock will try to drop a previously created lock on the repository in question. Using this option together with the -s or -c options is an error. The use of -p is highly recommended in conjunction with this option! Red flag if you mix it with -s/-c 💀.
• -l — this option tells cvslock to lock only the directory specified. Normally it locks the entire directory hierarchy under the specified directory. Just one directory? Iconic minimalism ✨.

😭 DIAGNOSTICS 😭

cvslock spits out some diagnostics to the standard error stream. It’s exit value is zero if and only if the locking operation requested by the user could be performed successfully. Note that no diagnostics about the exit value of commands executed through the -c switch are given. So check your own command exits, babes 🫶.

💀 BUGS 💀

The signal handling is not too well-tested and may be broken. Not me trusting signals too hard 😭.

If you try to create the same lock several times, you will get funny effects due to the error recovery cvslock tries to do. Funny haha? More like funny uh-oh 💀.

👑 SEE ALSO 👑

• Version Management with CVS
• rsync(1), system(3), cvs(1)

🦋 AUTHOR 🦋

cvslock was put together in a quick hacking session by Thomas Roessler <roessler@guug.de> and may be distributed under the terms of the GNU General Public License version 2.

---

okay that’s the whole page, bestie 💖 this was Unix, October 1998, for cvslock(1) — mwah 💅