summaryrefslogtreecommitdiff
path: root/static/v10/man8/vipw.8
diff options
context:
space:
mode:
authorJacob McDonnell <jacob@jacobmcdonnell.com>2026-04-25 21:07:28 -0400
committerJacob McDonnell <jacob@jacobmcdonnell.com>2026-04-25 21:07:28 -0400
commit711594636704defae873be1a355a292505585afd (patch)
tree59ee13f863830d8beba6cfd02bbe813dd486c26f /static/v10/man8/vipw.8
parent3258a063c1f189d7b019e40e525b46bef9b9a7b1 (diff)
docs: Added UNIX V10 Manuals
Diffstat (limited to 'static/v10/man8/vipw.8')
-rw-r--r--static/v10/man8/vipw.823
1 files changed, 23 insertions, 0 deletions
diff --git a/static/v10/man8/vipw.8 b/static/v10/man8/vipw.8
new file mode 100644
index 00000000..05f46458
--- /dev/null
+++ b/static/v10/man8/vipw.8
@@ -0,0 +1,23 @@
+.TH VIPW 8
+.UC 4
+.SH NAME
+vipw \- edit the password file with vi
+.SH SYNOPSIS
+.B vipw
+.SH DESCRIPTION
+.I Vipw
+edits the password file while setting the appropriate locks,
+and does any necessary processing after the password file is unlocked.
+If the password file is already being edited, then you will be told
+to try again later
+.SH SEE ALSO
+chfn(1), chsh(1), passwd(1), passwd(5), adduser(8)
+.SH FILES
+/etc/vipw.lock
+.SH BUGS
+.I Vipw
+does not remove the vipw.lock file; this is not a bug, but people tend
+to think it is.
+.PP
+No one deals with left-over /etc/ptmp (the real lock) files after a system
+crash.