From: Junio C Hamano <gitster@pobox.com>
To: Jari Aalto <jari.aalto@cante.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Explain in --pid-file that using --inetd implies it automatically
Date: Wed, 29 Aug 2007 01:17:17 -0700 [thread overview]
Message-ID: <7vabsasqk2.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <ejhm3gs6.fsf@cante.net> (Jari Aalto's message of "Wed, 29 Aug 2007 11:07:37 +0300")
Jari Aalto <jari.aalto@cante.net> writes:
> diff --git a/Documentation/git-daemon.txt b/Documentation/git-daemon.txt
> index f902161..687deb2 100644
> --- a/Documentation/git-daemon.txt
> +++ b/Documentation/git-daemon.txt
> @@ -124,7 +124,8 @@ OPTIONS
> Detach from the shell. Implies --syslog.
>
> --pid-file=file::
> - Save the process id in 'file'.
> + Save the process id in 'file'. When `--inetd` is in use, this
> + option is not needed.
Is it "is not needed"? I think you meant to say "is ignored",
IOW, no pid file is written.
Which unfortunately makes the title of your patch wrong as
well X-<.
I am not seriously suggesting to apply the following patch at
this point, but I think this is what we should have done from
the beginning.
diff --git a/daemon.c b/daemon.c
index 9cf22fe..a7b7990 100644
--- a/daemon.c
+++ b/daemon.c
@@ -1143,8 +1143,8 @@ int main(int argc, char **argv)
usage(daemon_usage);
}
- if (inetd_mode && (group_name || user_name))
- die("--user and --group are incompatible with --inetd");
+ if (inetd_mode && (group_name || user_name || pid_file))
+ die("--user, --group and --pid-file are incompatible with --inetd");
if (inetd_mode && (listen_port || listen_addr))
die("--listen= and --port= are incompatible with --inetd");
next prev parent reply other threads:[~2007-08-29 8:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 8:07 [PATCH] Explain in --pid-file that using --inetd implies it automatically Jari Aalto
2007-08-29 8:17 ` Junio C Hamano [this message]
2007-08-29 10:24 ` Jari Aalto
2007-08-29 10:23 ` Junio C Hamano
2007-08-29 10:33 ` [PATCH] git-daemon(1): assorted improvements Junio C Hamano
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=7vabsasqk2.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jari.aalto@cante.net \
/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;
as well as URLs for NNTP newsgroup(s).