On Tue, Mar 16, 2010 at 8:30 PM, William A. Rowe Jr. <wr...@rowe-clan.net> wrote: > On 3/16/2010 2:24 PM, Noirin Shirley wrote: >> On Tue, Mar 16, 2010 at 8:05 PM, William A. Rowe Jr. >> <wr...@rowe-clan.net> wrote: >>> On 3/16/2010 12:37 PM, Noirin Shirley wrote: >>>> >>>> In some places, we use httpd, but that leads to some horrible >>>> confusion between the product and the command. >>> >>> I guess I'm not seeing the disconnect. If a reader cannot parse httpd >>> as shorthand "the Apache HTTP Server program", then we have more serious >>> issues in helping them become a web server administrator. >> >> The problem is that httpd is used as shorthand for "the Apache HTTP >> Server" *and* as a reference to a specific binary/process/command, and >> we assume that people can work out the difference, because, y'know, >> Bill knows the difference, and Roy does, so obviously, all the rest of >> us should too. > > Actually; > > the command is usually apachectl ;-)
Unfortunately "usually" isn't the same as "always", and that only adds to the confusion. I know that you know what you're talking about when you say httpd, in any context. But a user coming to our docs sees the same word used as a process name, and as a product name, and then as a command, and then they're told they shouldn't use that command, ... Not everyone can be VP of the project. The docs are meant to make it easier for the people who *aren't* VP to use our software. Noirin
