Feature #2044
documentation: -f <fcgiapp> vs. -- <fcgiapp> [args]
| Status: | Fixed | Start date: | 2009-07-30 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 100% | |
| Category: | - | |||
| Target version: | 1.6.3 |
Description
In the man page the difference between launching spawn-fcgi with »-f "path arg1 arg2 ..."« and »-- path arg1 arg2 ...« are explained.
However, the help shown by »spawn-fcgi -h« does not mention the difference.
Suggestions:
- Change the output of »spawn-fcgi -h« to the following or something similar:
-f <path> filename of the fcgi-application (deprecated; ignored
if <fcgiapp> is given; needs /bin/sh which might not be
available in a chroot; should be avoided if shell expansion
is not needed)
- Mention missing shell expansion in the man page (not everybody knows how exec() works).
Associated revisions
Add deprecated and /bin/sh info for -f option; wrap syntax output (fixes #2044)
History
#1 Updated by stbuehler almost 4 years ago
I don't think the "-h" help needs to contain every detail; it should be just a short overview of available options.
#2 Updated by hspath almost 4 years ago
How about appending just "deprecated; needs /bin/sh" or "deprecated, see man page"? Currently it seems like it's just another way of invoking spawn-fcgi with no other implications.
#3 Updated by stbuehler over 3 years ago
- Target version set to 1.6.3
#4 Updated by stbuehler over 3 years ago
- Status changed from New to Fixed
- % Done changed from 0 to 100
Applied in changeset r53.
Also available in: Atom