El 08/11/14 a las 21:39, Ruben Safir escribió:
A) It says the socket is taken in systemd jaargon
The apache package does not use systemd socket activation in anyway..it probably tells you "the address is in use" by returning you the result of strerror(errno)..
B) The logs are dlete...
I deleted the damn logs on purpose but it was right, there was a mystory httpd process running after I killed the process.
So I tried to killall hhttpd that just caused a regeneration
killing httpd will do jack..process is not named that way.. it is named httpd2-$mpm where $mpm is either prefork, worker or event (the latter is the one you should be using)
systemctl stop httpd.service
NOTHING - not even feedback
what does systemctl status httpd.service says ?
I'm sure there is some ration reason and calming answer to why when I'm killing apache that systemd restarts it without my permision.
The apache systemd unit does use the restart on failure feature.
and there has to be some other calming nice reason why even through systemctl, that it doesn't give any feedback or nor kill the httpd server.
Yes, if the service stops with success it will not tell you anything. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org