On Mon, 27 May 2002, Sascha Schumann wrote:
> > -0.9. Whoever said we were deprecating them? I thought the plan was that > > apachectl would continue to accept 'start|stop|restart' and would pass > > them as 'httpd -k $ARGV' to Apache. That is what apachectl does > > currently. Yes, you *could* say apachectl -k start with the new code and > > it would work (I see no problem with that), but where in there are we > > deprecating the old way? It sounds like just a convenience that -k works, > > not that it's the new preferred method. Getting rid of 'apachectl start' > > and friends seems pointless to me, and it will irritate countless admins > > to change it after so many years for no reason. Part of the point of the refactoring of apachectl was to get rid of two major problems: - Having two different sets of arguments for httpd and apachectl is confusing and difficult to document - How do you pass additional command line arguments through apachectl? What will "apachectl -f /etc/httpd.conf start -D ReverseProxy" do? I believe the answer depends on the order of the arguments, which is truly nasty. So yes, -k should be the new preferred method. > > It would also defeat the current use of apachectl in the init > process. > > # ln -s `which apachectl` /etc/rc.d/rc3.d/S30apache Hmmm, I hadn't remembered that issue. That's a good point. What about if we document "-k" as the preferred method, but leave the other method available and do echo "Executing httpd -k start" so that it is clear what is going on? Joshua.
