mightymax / # /etc/init.d/apache2 restart * Reloading apache2... * Stopping apache2... [ ok ] * Starting apache2... [ ok ] apache2: illegal option -- k
A couple of things... The docs bundled with apache2 say to use 'apache2ctl' to stop, start, and restart apache2, and not 'apache2' as the /etc/init.d/apache2 script does. And it '/etc/init.d/apache2' restart isn't broken, apache2 does start, just it spits out the above error.
at least on 2.0.44 i dont get an error. seems ok this side; closing.
mightymax root # emerge apache -p These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] net-www/apache-2.0.43-r1 mightymax root # /etc/init.d/apache2 restart * Reloading apache2... * Stopping apache2... [ ok ] * Starting apache2... [ ok ] apache2: illegal option -- k Usage: /usr/sbin/apache2 [-D name] [-d directory] [-f file] [-C "directive"] [-c "directive"] [-k start|restart|graceful|stop] [-v] [-V] [-h] [-l] [-L] [-t] Options: -D name : define a name for use in <IfDefine name> directives -d directory : specify an alternate initial ServerRoot -f file : specify an alternate ServerConfigFile -C "directive" : process directive before reading config files -c "directive" : process directive after reading config files -e level : show startup errors of level (see LogLevel) -E file : log startup errors to file -v : show version number -V : show compile settings -h : list available command line options (this page) -l : list compiled in modules -L : list available configuration directives -t -D DUMP_VHOSTS : show parsed settings (currently only vhost settings) -t : run syntax check for config files [ !! ]
are you blind? I said 2.0.44, so you come back with a report on 2.0.43? open your eyes buddy.
Okay, perhaps I should have explained it a bit better... I just did 'emerge sync'. With ARCH="~x86" So 2.0.43 is the stable version... buddy.
2.0.44 is in portage. lol. i suppose if you cant figure out how to "see" this, email me, and I'll provide directions on how to use the "cd" and "ls" commands so that you can find it.
funny boy... anyway, the 2.044 is now the 'emerge apache' default, so it's only a valid issue for the 2.043 ebuild, if that's going to survive much longer. but you should be less sarcastic and condescending, you could almost be a debian developer.
