Re: Systemd support in 2.4

[Jan Kaluža]

On 12/06/2014 01:40 PM, Jeff Trawick wrote:

On Fri, Dec 5, 2014 at 6:59 AM, Jan Kaluža mailto:jkal...@redhat.com>> wrote:

On 12/02/2014 02:08 PM, Jeff Trawick wrote:

On Wed, Sep 17, 2014 at 9:22 AM, Jeff Trawick mailto:traw...@gmail.com>
>> wrote:

 On Mon, Sep 15, 2014 at 2:00 AM, Jan Kaluža
mailto:jkal...@redhat.com>
 >> wrote:

 On 09/14/2014 01:21 PM, Martynas Bendorius wrote:

 Hello,

 Is there any special reason why mod_systemd and
mod_journald
 (available
 in trunk) are not backported to 2.4 yet?


 Hi,

 I think mod_systemd could be proposed for 2.4 branch
(maybe even
 with the changes adding socket activation), but for
 mod_journald, we would have to backport "modular
logging", which
 breaks the API/ABI and therefore I'm afraid that won't
happen in
 2.4 branch :(.


 I have an old patch somewhere that doesn't break the
API/ABI, and
 accommodates such differences as syslog being built-in in
2.4.x.  I
 didn't realize that anybody besides me actually cared.

 I'll try to find time to see how it fits in 2.4.x-HEAD.


I've simply attached it from its state one year ago, not having
time to
play with it.  I don't think it is necessary to break the ABI.
syslog
support remains part of core logging instead of in a module.


I've created my version of the patch based on yours. It includes
also more recent commits from trunk related to errorlog providers.
Can you try it? I presume you have done that backport, because you
are running that somewhere :).


Once upon a time...  What remains in my possession is a test module I
wrote for testing the interface (attached).

Anyway, is this feature from ap_errorlog_provider lost intentionally?

+/** Checks syntax of ErrorLog directive argument.
+ * @param cmd The config directive
+ * @param arg ErrorLog directive argument (or the empty string if
+ * no argument was provided)
+ * @return Error message or NULL on success
+ * @remark The argument will be stored in the error_fname field
+ * of server_rec for access later.
+ */
+const char * (*parse_errorlog_arg)(cmd_parms *cmd, const char *arg);

(and code to call it in set_errorlog)



Thanks, I've missed that one when backporting. I've also checked that 
now my patch is the same as yours :).


Regards,
Jan Kaluza



Regards,
Jan Kaluza


 Jan Kaluza


 As we have a lot of distributions already using
systemd by
 default
 (CentOS/RHEL 7, Fedora, Arch Linux, CoreOS,
openSUSE), and
 more of them
 are going to use systemd by default (Debian 8 (Jessie),
 Ubuntu), it
 requires manual patching of apache for the support of
 systemd/journald.

 Thank you!




--
Born in Roswell... married an alien...
http://emptyhammock.com/



Index: docs/manual/mod/core.xml
===
--- docs/manual/mod/core.xml	(revision 1643223)
+++ docs/manual/mod/core.xml	(working copy)
@@ -1315,6 +1315,9 @@
 
 ErrorLog syslog:user
 
+Additional modules can provide their own ErrorLog providers. The syntax
+is similar to syslog example above.
+
 SECURITY: See the security tips
 document for details on why your security could be compromised
Index: include/http_core.h
===
--- include/http_core.h	(revision 1643223)
+++ include/http_core.h	(working copy)
@@ -835,8 +835,54 @@
 
 /** message format */
 const char *format;
+/** 1 if logging using provider, 0 otherwise */
+int using_provider;
 } ap_errorlog_info;
 
+#define AP_ERRORLOG_PROVIDER_GROUP "error_log_writer"
+#define AP_ERRORLOG_PROVIDER_VERSION "0"
+#define AP_ERRORLOG_DEFAULT_PROVIDER "file"
+
+/** add APR_EOL_STR to the end of log message */
+#define AP_ERRORLOG_PROVIDER_ADD_EOL_STR   1
+
+typedef struct ap_errorlog_provider ap_errorlog_provider;
+
+struct ap_errorlog_provider {
+/** Initializes the error log writer.
+ * @param p The pool to create any storage from
+ * @param s Server for which the logger is initialized
+ * @return Pointer to handle passed later to writer() function
+ * @note On success, the provider must return non-NULL, even if
+ * the handle is not necessary when the writer() function is
+ * called.  On failure, the provider should log a startup er

Re: Systemd support in 2.4

[Jeff Trawick]

On Fri, Dec 5, 2014 at 6:59 AM, Jan Kaluža  wrote:

> On 12/02/2014 02:08 PM, Jeff Trawick wrote:
>
>> On Wed, Sep 17, 2014 at 9:22 AM, Jeff Trawick > > wrote:
>>
>> On Mon, Sep 15, 2014 at 2:00 AM, Jan Kaluža > > wrote:
>>
>> On 09/14/2014 01:21 PM, Martynas Bendorius wrote:
>>
>> Hello,
>>
>> Is there any special reason why mod_systemd and mod_journald
>> (available
>> in trunk) are not backported to 2.4 yet?
>>
>>
>> Hi,
>>
>> I think mod_systemd could be proposed for 2.4 branch (maybe even
>> with the changes adding socket activation), but for
>> mod_journald, we would have to backport "modular logging", which
>> breaks the API/ABI and therefore I'm afraid that won't happen in
>> 2.4 branch :(.
>>
>>
>> I have an old patch somewhere that doesn't break the API/ABI, and
>> accommodates such differences as syslog being built-in in 2.4.x.  I
>> didn't realize that anybody besides me actually cared.
>>
>> I'll try to find time to see how it fits in 2.4.x-HEAD.
>>
>>
>> I've simply attached it from its state one year ago, not having time to
>> play with it.  I don't think it is necessary to break the ABI.  syslog
>> support remains part of core logging instead of in a module.
>>
>
> I've created my version of the patch based on yours. It includes also more
> recent commits from trunk related to errorlog providers. Can you try it? I
> presume you have done that backport, because you are running that somewhere
> :).
>

Once upon a time...  What remains in my possession is a test module I wrote
for testing the interface (attached).

Anyway, is this feature from ap_errorlog_provider lost intentionally?

+/** Checks syntax of ErrorLog directive argument.
+ * @param cmd The config directive
+ * @param arg ErrorLog directive argument (or the empty string if
+ * no argument was provided)
+ * @return Error message or NULL on success
+ * @remark The argument will be stored in the error_fname field
+ * of server_rec for access later.
+ */
+const char * (*parse_errorlog_arg)(cmd_parms *cmd, const char *arg);

(and code to call it in set_errorlog)



> Regards,
> Jan Kaluza
>
>
>  Jan Kaluza
>>
>>
>> As we have a lot of distributions already using systemd by
>> default
>> (CentOS/RHEL 7, Fedora, Arch Linux, CoreOS, openSUSE), and
>> more of them
>> are going to use systemd by default (Debian 8 (Jessie),
>> Ubuntu), it
>> requires manual patching of apache for the support of
>> systemd/journald.
>>
>> Thank you!
>>
>>


-- 
Born in Roswell... married an alien...
http://emptyhammock.com/
#include "apr_strings.h"

#include "ap_provider.h"
#include "http_core.h"
#include "http_log.h"

static void *elprov_error_log_init(apr_pool_t *p, server_rec *s)
{
apr_file_t *f;
apr_status_t rv;
const char *basename = "logfile.txt";

if (s->error_fname) {
basename = apr_pstrcat(p, basename, ".", s->error_fname, NULL);
}

rv = apr_file_open(&f, 
   apr_pstrcat(p,
   getenv("HOME"),
   "/",
   basename,
   NULL),
   APR_WRITE | APR_APPEND | APR_CREATE,
   APR_OS_DEFAULT, p);
if (rv != APR_SUCCESS) {
ap_log_error(APLOG_MARK, APLOG_ERR | APLOG_STARTUP, rv, s,
 "mod_elprov: Error opening log file");
return NULL;
}

return f;
}

static apr_status_t elprov_error_log(const ap_errorlog_info *info,
 void *handle, const char *errstr,
 apr_size_t len)
{
return apr_file_write((apr_file_t *)handle, errstr, &len);
}

static const char *elprov_error_log_parse(cmd_parms *cmd, const char *arg)
{
/* no configuration is valid */
if (strlen(arg) 
&& (ap_strchr_c(arg, '/') || ap_strchr_c(arg, '\\'))) {
return
  apr_pstrcat(cmd->pool,
  "elprov error log provider does not accept args "
  "which contain slashes (\"",
  arg,
  "\")",
  NULL);
}
return NULL;
}

static ap_errorlog_provider elprov_provider = {
elprov_error_log_init,
elprov_error_log,
elprov_error_log_parse,
AP_ERRORLOG_PROVIDER_ADD_EOL_STR
};

static void elprov_register_hooks(apr_pool_t *p)
{
ap_register_provider(p, AP_ERRORLOG_PROVIDER_GROUP, "elprov",
 AP_ERRORLOG_PROVIDER_VERSION, &elprov_provider);
}

AP_DECLARE_MODULE(elprov) =
{
STANDARD20_MODULE_STUFF,
NULL,
NULL,
NULL,
NULL,
NULL,
elprov_register_hooks,
};

Re: Systemd support in 2.4

[Jan Kaluža]

On 12/02/2014 02:08 PM, Jeff Trawick wrote:

On Wed, Sep 17, 2014 at 9:22 AM, Jeff Trawick mailto:traw...@gmail.com>> wrote:

On Mon, Sep 15, 2014 at 2:00 AM, Jan Kaluža mailto:jkal...@redhat.com>> wrote:

On 09/14/2014 01:21 PM, Martynas Bendorius wrote:

Hello,

Is there any special reason why mod_systemd and mod_journald
(available
in trunk) are not backported to 2.4 yet?


Hi,

I think mod_systemd could be proposed for 2.4 branch (maybe even
with the changes adding socket activation), but for
mod_journald, we would have to backport "modular logging", which
breaks the API/ABI and therefore I'm afraid that won't happen in
2.4 branch :(.


I have an old patch somewhere that doesn't break the API/ABI, and
accommodates such differences as syslog being built-in in 2.4.x.  I
didn't realize that anybody besides me actually cared.

I'll try to find time to see how it fits in 2.4.x-HEAD.


I've simply attached it from its state one year ago, not having time to
play with it.  I don't think it is necessary to break the ABI.  syslog
support remains part of core logging instead of in a module.


I've created my version of the patch based on yours. It includes also 
more recent commits from trunk related to errorlog providers. Can you 
try it? I presume you have done that backport, because you are running 
that somewhere :).


Regards,
Jan Kaluza


Jan Kaluza


As we have a lot of distributions already using systemd by
default
(CentOS/RHEL 7, Fedora, Arch Linux, CoreOS, openSUSE), and
more of them
are going to use systemd by default (Debian 8 (Jessie),
Ubuntu), it
requires manual patching of apache for the support of
systemd/journald.

Thank you!





--
Born in Roswell... married an alien...
http://emptyhammock.com/



Index: docs/manual/mod/core.xml
===
--- docs/manual/mod/core.xml	(revision 1643223)
+++ docs/manual/mod/core.xml	(working copy)
@@ -1315,6 +1315,9 @@
 
 ErrorLog syslog:user
 
+Additional modules can provide their own ErrorLog providers. The syntax
+is similar to syslog example above.
+
 SECURITY: See the security tips
 document for details on why your security could be compromised
Index: include/http_core.h
===
--- include/http_core.h	(revision 1643223)
+++ include/http_core.h	(working copy)
@@ -835,8 +835,44 @@
 
 /** message format */
 const char *format;
+/** 1 if logging using provider, 0 otherwise */
+int using_provider;
 } ap_errorlog_info;
 
+#define AP_ERRORLOG_PROVIDER_GROUP "error_log_writer"
+#define AP_ERRORLOG_PROVIDER_VERSION "0"
+#define AP_ERRORLOG_DEFAULT_PROVIDER "file"
+
+/** add APR_EOL_STR to the end of log message */
+#define AP_ERRORLOG_PROVIDER_ADD_EOL_STR   1
+
+typedef struct ap_errorlog_provider ap_errorlog_provider;
+
+struct ap_errorlog_provider {
+/** Initializes the error log writer.
+ * @param p The pool to create any storage from
+ * @param s Server for which the logger is initialized
+ * @return Pointer to handle passed later to writer() function
+ * @note On success, the provider must return non-NULL, even if
+ * the handle is not necessary when the writer() function is
+ * called.  On failure, the provider should log a startup error
+ * message and return NULL to abort httpd startup.
+ */
+void * (*init)(apr_pool_t *p, server_rec *s);
+
+/** Logs the error message to external error log.
+ * @param info Context of the error message
+ * @param handle Handle created by init() function
+ * @param errstr Error message
+ * @param len Length of the error message
+ */
+apr_status_t (*writer)(const ap_errorlog_info *info, void *handle,
+   const char *errstr, apr_size_t len);
+
+/** a combination of the AP_ERRORLOG_PROVIDER_* flags */
+unsigned int flags;
+};
+
 /**
  * callback function prototype for a external errorlog handler
  * @note To avoid unbounded memory usage, these functions must not allocate
Index: include/httpd.h
===
--- include/httpd.h	(revision 1643223)
+++ include/httpd.h	(working copy)
@@ -1248,6 +1248,10 @@
 apr_file_t *error_log;
 /** The log level configuration */
 struct ap_logconf log;
+/** External error log writer provider */
+struct ap_errorlog_provider *errorlog_provider;
+/** Handle to be passed to external log provider's logging method */
+void *errorlog_provider_handle;
 
 /* Module-specific configuration for server, and defaults... */
 
Index: server/core.c
===
--- server/core.c	(revisio

Re: Systemd support in 2.4

[Jeff Trawick]

On Wed, Sep 17, 2014 at 9:22 AM, Jeff Trawick  wrote:

> On Mon, Sep 15, 2014 at 2:00 AM, Jan Kaluža  wrote:
>
>> On 09/14/2014 01:21 PM, Martynas Bendorius wrote:
>>
>>> Hello,
>>>
>>> Is there any special reason why mod_systemd and mod_journald (available
>>> in trunk) are not backported to 2.4 yet?
>>>
>>
>> Hi,
>>
>> I think mod_systemd could be proposed for 2.4 branch (maybe even with the
>> changes adding socket activation), but for mod_journald, we would have to
>> backport "modular logging", which breaks the API/ABI and therefore I'm
>> afraid that won't happen in 2.4 branch :(.
>>
>>
> I have an old patch somewhere that doesn't break the API/ABI, and
> accommodates such differences as syslog being built-in in 2.4.x.  I didn't
> realize that anybody besides me actually cared.
>
> I'll try to find time to see how it fits in 2.4.x-HEAD.
>

I've simply attached it from its state one year ago, not having time to
play with it.  I don't think it is necessary to break the ABI.  syslog
support remains part of core logging instead of in a module.


>
>
>
>> Jan Kaluza
>>
>>
>>  As we have a lot of distributions already using systemd by default
>>> (CentOS/RHEL 7, Fedora, Arch Linux, CoreOS, openSUSE), and more of them
>>> are going to use systemd by default (Debian 8 (Jessie), Ubuntu), it
>>> requires manual patching of apache for the support of systemd/journald.
>>>
>>> Thank you!
>>>
>>>
>>
>
>
> --
Born in Roswell... married an alien...
http://emptyhammock.com/
Index: docs/manual/mod/core.xml
===
--- docs/manual/mod/core.xml(revision 1545470)
+++ docs/manual/mod/core.xml(working copy)
@@ -1293,10 +1293,10 @@
 more information.
 
 Using syslog instead of a filename enables logging
-via syslogd(8) if the system supports it. The default is to use
-syslog facility local7, but you can override this by
-using the syslog:facility syntax where
-facility can be one of the names usually documented in
+via syslogd(8) if the system supports it and if mod_syslog
+is loaded. The default is to use syslog facility local7,
+but you can override this by using the 
syslog:facility
+syntax where facility can be one of the names usually 
documented in
 syslog(1).  The facility is effectively global, and if it is changed
 in individual virtual hosts, the final facility specified affects the
 entire server.
@@ -1303,6 +1303,9 @@
 
 ErrorLog syslog:user
 
+Additional modules can provide their own ErrorLog providers. The syntax
+is similar to syslog example above.
+
 SECURITY: See the security tips
 document for details on why your security could be compromised
Index: docs/manual/mod
===
--- docs/manual/mod (revision 1545470)
+++ docs/manual/mod (working copy)

Property changes on: docs/manual/mod
___
Modified: svn:mergeinfo
   Merged /httpd/httpd/trunk/docs/manual/mod:r1525597
Index: docs/manual
===
--- docs/manual (revision 1545470)
+++ docs/manual (working copy)

Property changes on: docs/manual
___
Modified: svn:mergeinfo
   Merged /httpd/httpd/trunk/docs/manual:r1525597
Index: include/http_core.h
===
--- include/http_core.h (revision 1545470)
+++ include/http_core.h (working copy)
@@ -826,8 +826,55 @@
 
 /** message format */
 const char *format;
+
+/** 1 if logging using provider, 0 otherwise */
+int using_provider;
 } ap_errorlog_info;
 
+#define AP_ERRORLOG_PROVIDER_GROUP "error_log_writer"
+#define AP_ERRORLOG_PROVIDER_VERSION "0"
+#define AP_ERRORLOG_DEFAULT_PROVIDER "file"
+
+/** add APR_EOL_STR to the end of log message */
+#define AP_ERRORLOG_PROVIDER_ADD_EOL_STR   1
+
+typedef struct ap_errorlog_provider ap_errorlog_provider;
+
+struct ap_errorlog_provider {
+/** Initializes the error log writer.
+ * @param p The pool to create any storage from
+ * @param s Server for which the logger is initialized
+ * @return Pointer to handle passed later to writer() function
+ * @note On success, the provider must return non-NULL, even if
+ * the handle is not necessary when the writer() function is
+ * called.  On failure, the provider should log a startup error
+ * message and return NULL to abort httpd startup.
+ */
+void * (*init)(apr_pool_t *p, server_rec *s);
+
+/** Logs the error message to external error log.
+ * @param info Context of the error message
+ * @param handle Handle created by init() function
+ * @param errstr Error message
+ * @param len Length of the error message
+ */
+apr_status_t (*writer)(const ap_errorlog_info *info, void *handle,
+

Re: Systemd support in 2.4

[Jim Jagielski]

Whether we like it or not, systemd is here to stay.

   systemd: The Emacs of Linux init implementations.

*grin*
On Sep 17, 2014, at 9:22 AM, Jeff Trawick  wrote:

> On Mon, Sep 15, 2014 at 2:00 AM, Jan Kaluža  wrote:
> On 09/14/2014 01:21 PM, Martynas Bendorius wrote:
> Hello,
> 
> Is there any special reason why mod_systemd and mod_journald (available
> in trunk) are not backported to 2.4 yet?
> 
> Hi,
> 
> I think mod_systemd could be proposed for 2.4 branch (maybe even with the 
> changes adding socket activation), but for mod_journald, we would have to 
> backport "modular logging", which breaks the API/ABI and therefore I'm afraid 
> that won't happen in 2.4 branch :(.
> 
> 
> I have an old patch somewhere that doesn't break the API/ABI, and 
> accommodates such differences as syslog being built-in in 2.4.x.  I didn't 
> realize that anybody besides me actually cared.
> 
> I'll try to find time to see how it fits in 2.4.x-HEAD.
> 
>  
> Jan Kaluza
> 
> 
> As we have a lot of distributions already using systemd by default
> (CentOS/RHEL 7, Fedora, Arch Linux, CoreOS, openSUSE), and more of them
> are going to use systemd by default (Debian 8 (Jessie), Ubuntu), it
> requires manual patching of apache for the support of systemd/journald.
> 
> Thank you!
> 
> 
> 
> 
> 
> -- 
> Born in Roswell... married an alien...
> http://emptyhammock.com/

Re: Systemd support in 2.4

[Jeff Trawick]

On Mon, Sep 15, 2014 at 2:00 AM, Jan Kaluža  wrote:

> On 09/14/2014 01:21 PM, Martynas Bendorius wrote:
>
>> Hello,
>>
>> Is there any special reason why mod_systemd and mod_journald (available
>> in trunk) are not backported to 2.4 yet?
>>
>
> Hi,
>
> I think mod_systemd could be proposed for 2.4 branch (maybe even with the
> changes adding socket activation), but for mod_journald, we would have to
> backport "modular logging", which breaks the API/ABI and therefore I'm
> afraid that won't happen in 2.4 branch :(.
>
>
I have an old patch somewhere that doesn't break the API/ABI, and
accommodates such differences as syslog being built-in in 2.4.x.  I didn't
realize that anybody besides me actually cared.

I'll try to find time to see how it fits in 2.4.x-HEAD.



> Jan Kaluza
>
>
>  As we have a lot of distributions already using systemd by default
>> (CentOS/RHEL 7, Fedora, Arch Linux, CoreOS, openSUSE), and more of them
>> are going to use systemd by default (Debian 8 (Jessie), Ubuntu), it
>> requires manual patching of apache for the support of systemd/journald.
>>
>> Thank you!
>>
>>
>


-- 
Born in Roswell... married an alien...
http://emptyhammock.com/

Re: Systemd support in 2.4

[Jan Kaluža]

On 09/15/2014 08:00 AM, Jan Kaluža wrote:

On 09/14/2014 01:21 PM, Martynas Bendorius wrote:

Hello,

Is there any special reason why mod_systemd and mod_journald (available
in trunk) are not backported to 2.4 yet?


Hi,

I think mod_systemd could be proposed for 2.4 branch (maybe even with
the changes adding socket activation), but for mod_journald, we would
have to backport "modular logging", which breaks the API/ABI and
therefore I'm afraid that won't happen in 2.4 branch :(.


mod_systemd and socket activation proposed in r1625531.

Jan Kaluza


Jan Kaluza


As we have a lot of distributions already using systemd by default
(CentOS/RHEL 7, Fedora, Arch Linux, CoreOS, openSUSE), and more of them
are going to use systemd by default (Debian 8 (Jessie), Ubuntu), it
requires manual patching of apache for the support of systemd/journald.

Thank you!

Re: Systemd support in 2.4

[Jan Kaluža]

On 09/14/2014 01:21 PM, Martynas Bendorius wrote:

Hello,

Is there any special reason why mod_systemd and mod_journald (available
in trunk) are not backported to 2.4 yet?


Hi,

I think mod_systemd could be proposed for 2.4 branch (maybe even with 
the changes adding socket activation), but for mod_journald, we would 
have to backport "modular logging", which breaks the API/ABI and 
therefore I'm afraid that won't happen in 2.4 branch :(.


Jan Kaluza


As we have a lot of distributions already using systemd by default
(CentOS/RHEL 7, Fedora, Arch Linux, CoreOS, openSUSE), and more of them
are going to use systemd by default (Debian 8 (Jessie), Ubuntu), it
requires manual patching of apache for the support of systemd/journald.

Thank you!

Re: Systemd support in 2.4

[Jan Kaluža]

On 09/14/2014 01:35 PM, Reindl Harald wrote:


Am 14.09.2014 um 13:21 schrieb Martynas Bendorius:

Is there any special reason why mod_systemd and mod_journald (available in 
trunk) are not backported to 2.4 yet?

As we have a lot of distributions already using systemd by default (CentOS/RHEL 
7, Fedora, Arch Linux, CoreOS,
openSUSE), and more of them are going to use systemd by default (Debian 8 
(Jessie), Ubuntu), it requires manual
patching of apache for the support of systemd/journald


in most setups you have access logs for each virtual host for log-analyzers
and sometimes the customer itself has access to this logs - not sure why
you would have that in the systemlogs



I think you can still have access_log per virtualhost with mod_journald, 
but from the performance reasons, I would not advice anyone to store 
access_log with mod_journald.


Jan Kaluza

Re: Systemd support in 2.4

[Martynas Bendorius]

Reindl, thank you for your input :) mod_journald was just an addition to 
this letter, because it's available on RHEL7/CentOS7 and many other 
distros, the main thing in question in mod_systemd, which is really 
useful, and distributions supporting systemd already provide mod_systemd 
by default, even though it's not backported to 2.4 yet.


Best regards,
Martynas Bendorius

On 9/14/14 2:35 PM, Reindl Harald wrote:


Am 14.09.2014 um 13:21 schrieb Martynas Bendorius:

Is there any special reason why mod_systemd and mod_journald (available in 
trunk) are not backported to 2.4 yet?

As we have a lot of distributions already using systemd by default (CentOS/RHEL 
7, Fedora, Arch Linux, CoreOS,
openSUSE), and more of them are going to use systemd by default (Debian 8 
(Jessie), Ubuntu), it requires manual
patching of apache for the support of systemd/journald


in most setups you have access logs for each virtual host for log-analyzers
and sometimes the customer itself has access to this logs - not sure why
you would have that in the systemlogs

Re: Systemd support in 2.4

[Reindl Harald]

Am 14.09.2014 um 13:21 schrieb Martynas Bendorius:
> Is there any special reason why mod_systemd and mod_journald (available in 
> trunk) are not backported to 2.4 yet?
> 
> As we have a lot of distributions already using systemd by default 
> (CentOS/RHEL 7, Fedora, Arch Linux, CoreOS,
> openSUSE), and more of them are going to use systemd by default (Debian 8 
> (Jessie), Ubuntu), it requires manual
> patching of apache for the support of systemd/journald

in most setups you have access logs for each virtual host for log-analyzers
and sometimes the customer itself has access to this logs - not sure why
you would have that in the systemlogs



signature.asc
Description: OpenPGP digital signature

Systemd support in 2.4

[Martynas Bendorius]

Hello,

Is there any special reason why mod_systemd and mod_journald (available 
in trunk) are not backported to 2.4 yet?


As we have a lot of distributions already using systemd by default 
(CentOS/RHEL 7, Fedora, Arch Linux, CoreOS, openSUSE), and more of them 
are going to use systemd by default (Debian 8 (Jessie), Ubuntu), it 
requires manual patching of apache for the support of systemd/journald.


Thank you!

--
Best regards,
Martynas Bendorius