1 |
Whoops... I'm sorry... I took another look and misunderstood what multilog |
2 |
is doing here... How difficult would it for me to stop using multilog and |
3 |
use the "old style" logging for smb, etc with their own old fashioned |
4 |
files under /var/log? |
5 |
|
6 |
|
7 |
On Wed, 11 Jul 2001 18:56:57 -0500 |
8 |
"Bruce A. Locke" <blocke@××××××.org> wrote: |
9 |
|
10 |
> |
11 |
> I've been playing around with the daemon tools package recently. |
12 |
> Supervise is nice and would be handy in a server setting but I can't |
13 |
> figure out why anyone would want multilog over a syslog or syslog |
14 |
> replacement. The resulting log files have to be filtered to be |
15 |
readable, |
16 |
> they are _not_ being put into /var/log with the syslog.d stuff, etc, the |
17 |
> filenames are not very human readable, there are multiple processes |
18 |
> involved (including the gluelog hack). Seems like I'm loosing ease of |
19 |
> use, the ability to forward logs, a standard log location, etc in |
20 |
exchange |
21 |
> for a poorly documented monstrocity :) What is the advantages of |
22 |
> multilog? Perhaps I'm missing something :) |
23 |
> |
24 |
> Would it be possible to get a syslog USE keyword or equiv and have the |
25 |
> supervise run scripts we create have support for it? That way if the |
26 |
use |
27 |
> keyword is set then people can use syslog or a syslog replacement like |
28 |
> syslog-ng and people who happen to like multilog can continue using it. |
29 |
> |
30 |
> Just a thought... any comments? |
31 |
> |
32 |
> --------------------------------------------------------------------- |
33 |
> Bruce A. Locke |
34 |
> blocke@××××××.org |
35 |
> |
36 |
> |
37 |
> _______________________________________________ |
38 |
> gentoo-dev mailing list |
39 |
> gentoo-dev@××××××××××.org |
40 |
> http://cvs.gentoo.org/mailman/listinfo/gentoo-dev |
41 |
> |
42 |
|
43 |
|
44 |
|
45 |
--------------------------------------------------------------------- |
46 |
Bruce A. Locke |
47 |
blocke@××××××.org |