A better method than daisy-chaining logging files?

From: Dewayne Geraghty <dewayne.geraghty_at_heuristicsystems.com.au>
Date: Fri, 31 May 2019 15:24:42 +1000

I'm still working the Apache problem, and I'm using s6-log to manage the
logs.

I just attempted to link an apache24 instance to its log files via a
bundle, which isn't acceptable to s6-rc-compile.

The approach attempted was to chain:
1. apache24 (longrun) and is a producer-for apache24-log
2. apache24-log (bundle) is a consumer-for apache24, with contents, the
following, two longrun's for logging)
3. apache24-access-log (longrun) & apache24-error-log (longrun)

Is it envisaged that s6-rc would enable something like this in the
future, or will the following method remain:

1. apache24 (longrun) and is a producer-for apache24-access-log
-. apache24-log (bundle) [ only for admin, though largely redundant ]
2. apache24-access-log (longrun) consumer-for apache24, producer-for
apache24-error-log
3. apache24-error-log (longrun) consumer-for apache24-access-log

The link between items 2 and 3 is fictional as is the absence of a
connection between 1 and 3.

Ideally having:
apache24 as producer-for (both) apache24-access-log and
apache24-error-log might be another option as it reflects reality. But
this also isn't acceptable to the s6-rc-compile.

This is a very simplified example as I have 6 sites to manage, and its
seems wrong to complicate the setup with artificial links with s6-rc?

I'm very interested to understand the reasoning.

Kind regards, Dewayne
Received on Fri May 31 2019 - 05:24:42 UTC