|FROM ||Ruben Safir
|SUBJECT ||Subject: [NYLXS - HANGOUT] httpd won't go away
|From owner-hangout-outgoing-at-mrbrklyn.com Sat Nov 8 19:44:02 2014
Received: by mrbrklyn.com (Postfix)
id 053B5161143; Sat, 8 Nov 2014 19:44:02 -0500 (EST)
Received: by mrbrklyn.com (Postfix, from userid 28)
id E9ECA161158; Sat, 8 Nov 2014 19:44:01 -0500 (EST)
Received: from mailbackend.panix.com (mailbackend.panix.com [18.104.22.168])
by mrbrklyn.com (Postfix) with ESMTP id 51737161143
for ; Sat, 8 Nov 2014 19:43:59 -0500 (EST)
Received: from panix2.panix.com (panix2.panix.com [22.214.171.124])
by mailbackend.panix.com (Postfix) with ESMTP id BCF94139BD
for ; Sat, 8 Nov 2014 19:43:56 -0500 (EST)
Received: by panix2.panix.com (Postfix, from userid 20529)
id 89D7933C79; Sat, 8 Nov 2014 19:43:56 -0500 (EST)
Date: Sat, 8 Nov 2014 19:43:56 -0500
From: Ruben Safir
Subject: [NYLXS - HANGOUT] httpd won't go away
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.5.23 (2014-03-12)
I was trying to debug an apache application and I NEED to see the output
from modperl to stderr which goes straight to the error logs.
I couldn't find the output no matter where I looked
So I'm trying to stop and start apache and when I do, apache won't start
A) It says the socket is taken in systemd jaargon
B) The logs are delete...
I deleted the damn logs on purpose but it was right, there was a mystery
httpd process running after I killed the process.
So I tried to killall hhttpd
that just caused a regeneration
systemctl stop httpd.service
NOTHING - not even feedback
Pull the F***ing plug
Yeah that still works.
I'm sure there is some rational reason and calming answer as to why when I'm
killing apache that systemd restarts it without my permision.
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
for me, I'm moving to Jupiter 1. It is safer there.