[HOME] [NSRG] [インフラ] [fml4] [fml8] [北海道] [おすすめの本] Powered by NetBSD and [nuinui.net] .

Recipes

1. show fml error log of yesterday.
2. See old logs.
3. Centralize log messages.
4. extract specific log messages in monitoring.
5. extrace the specific log messages with coping it.
6. Expire old log files.

1. show fml error log of yesterday.

daily.pl of fml4 is not implemented yet.

Currently use grep to parse the log file.

2. See old logs.

fml8 appends log messages continuously into the log file at $ml_home_directory by default. All log messages exist in it.

On the other hand, Unix log expires. So you cannot trace too lod messages.

Please tune parameters of expiration tools e.g. newsyslog which program differs from unix variants to variants to save log messages in at least 3 months.

3. Centralize log messages.

Unix uses syslog mechanism. To redirect all messages to /var/log/messages, set the following:

[/etc/syslog.conf]

*.*		/var/log/messages

Also, fml8 can use syslog mechanism.

[/var/spool/ml/elena/config.cf]

log_type	=	syslog

To use these configuration, all messages are centralized to /var/log/messages file.

4. extract specific log messages in monitoring.

% tail -F /var/spool/ml/elena/log | grep 'PATTERN'

5. extrace the specific log messages with coping it.

% tail -F /var/spool/ml/elena/log | grep 'PATTERN' | tee FILE

6. Expire old log files.

Newsyslog mechanism provided by fml4 is not implemented.

[HOME] [NSRG] [インフラ] [fml4] [fml8] [北海道] [おすすめの本] Powered by NetBSD and [nuinui.net] .
Copyright (C) 1993-2017 Ken'ichi Fukamachi mail:< fukachan at fml.org >