Skip to contentSkip to conversation

Fix up uuidd man page

PATCH In review Eric Sandeen 1 participant 2 messages Jan 9, 2008

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 Fix up uuidd man page

uuidd(8) man page had a typo, and a couple of stale defaults documented.

---

misc/uuidd.8.in +2 -2
Index: e2fsprogs-1.40.4/misc/uuidd.8.in
===================================================================
@@ -64,11 +64,11 @@ UUID's.
 .TP
 .BI \-p  " pidfile"
 Specify the pathname where the pid file should be written.  By default,
-the pid file is written to /var/run/uuidd.pid.
+the pid file is written to /var/lib/libuuid/uuidd.pid.
 .TP
 .BI \-s " socketpath"
 Specify the pathname used for the unix-domain socket used by uuidd.  By
-qdefault, the pathname used is /var/run/uuidd.sock.  This is primarily
+default, the pathname used is /var/lib/libuuid/request.  This is primarily
 for debugging purposes, since the pathname is hard-coded in the libuuid
 library.
 .TP
#1 lore raw
Quoted 12 lines · Eric Sandeen

uuidd(8) man page had a typo, and a couple of stale defaults documented.

---

Index: e2fsprogs-1.40.4/misc/uuidd.8.in
===================================================================

misc/uuidd.8.in UUID's. · line 67

Quoted 5 lines
misc/uuidd.8.in +1 -1
@@ -64,11 +64,11 @@ UUID's.
 .TP
 .BI \-p  " pidfile"
 Specify the pathname where the pid file should be written.  By default,
-the pid file is written to /var/run/uuidd.pid.
+the pid file is written to /var/lib/libuuid/uuidd.pid.

Actually, hang on. Why is this in /var/lib, not /var/run?

I can see keeping state files in /var/lib so they're persistent across boots, but the pidfile?

-Eric