From: Eric Sandeen <sandeen@redhat.com>
To: Theodore Tso <tytso@mit.edu>,
ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] Fix up uuidd man page
Date: Wed, 09 Jan 2008 10:45:01 -0600 [thread overview]
Message-ID: <4784FA0D.7010600@redhat.com> (raw)
In-Reply-To: <4784F0F0.9090303@redhat.com>
Eric Sandeen wrote:
> uuidd(8) man page had a typo, and a couple of stale defaults
> documented.
>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
>
> ---
>
> Index: e2fsprogs-1.40.4/misc/uuidd.8.in
> ===================================================================
> --- e2fsprogs-1.40.4.orig/misc/uuidd.8.in
> +++ 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.
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
prev parent reply other threads:[~2008-01-09 16:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 16:06 [PATCH] Fix up uuidd man page Eric Sandeen
2008-01-09 16:45 ` Eric Sandeen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4784FA0D.7010600@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox