MESSAGE
DATE | 2014-11-08 |
FROM | Ruben Safir
|
SUBJECT | Fwd: [NYLXS - HANGOUT] httpd won't go away
|
From owner-hangout-outgoing-at-mrbrklyn.com Sat Nov 8 22:10:01 2014 Return-Path: X-Original-To: archive-at-mrbrklyn.com Delivered-To: archive-at-mrbrklyn.com Received: by mrbrklyn.com (Postfix) id 7500C161160; Sat, 8 Nov 2014 22:10:00 -0500 (EST) Delivered-To: hangout-outgoing-at-mrbrklyn.com Received: by mrbrklyn.com (Postfix, from userid 28) id 4CE1D161169; Sat, 8 Nov 2014 22:10:00 -0500 (EST) Delivered-To: hangout-at-nylxs.com Received: from mailbackend.panix.com (mailbackend.panix.com [166.84.1.89]) by mrbrklyn.com (Postfix) with ESMTP id 82B75161160 for ; Sat, 8 Nov 2014 22:09:59 -0500 (EST) Received: from [10.0.0.42] (unknown [96.57.23.82]) by mailbackend.panix.com (Postfix) with ESMTP id 5FB7013F58 for ; Sat, 8 Nov 2014 22:09:59 -0500 (EST) Message-ID: <545EDB2B.7000102-at-panix.com> Date: Sat, 08 Nov 2014 22:10:35 -0500 From: Ruben Safir User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.0 MIME-Version: 1.0 To: Hangout Subject: Fwd: [NYLXS - HANGOUT] httpd won't go away References: <20141109004356.GA19870-at-panix.com> In-Reply-To: <20141109004356.GA19870-at-panix.com> X-Forwarded-Message-Id: <20141109004356.GA19870-at-panix.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: owner-hangout-at-mrbrklyn.com Precedence: bulk Reply-To: hangout-at-mrbrklyn.com
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 because
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 httpd 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 server.
for me, I'm moving to Jupiter 1. It is safer there.
|
|