Hi,
I have a log-server (syslog-ng) collecting logs from my servers.
Everything works for standard logs: clients forward them to server
where they are filtered (based on facility or application) and
splitted into a few files (for each client).
The problem is with portage logs: I can not find any
On Sat, 2009-08-22 at 10:39 +0200, Jarry wrote:
Hi,
I have a log-server (syslog-ng) collecting logs from my servers.
Everything works for standard logs: clients forward them to server
where they are filtered (based on facility or application) and
splitted into a few files (for each client).
Albert Hopkins wrote:
On Sat, 2009-08-22 at 10:39 +0200, Jarry wrote:
The problem is with portage logs: I can not find any pattern
I could use to filter them out.
I'm not sure what you are trying to filter out. Portage logs are
relatively machine-readable (e.g. qlop).
syslog-ng in client
On Saturday 22 August 2009 13:25:12 Jarry wrote:
The first quite natural filter-rule is to split logs according
to client-IP (or hostname). The second level is to split logs
according to application. I do not want to have logs from kernel,
sshd, apache, ntp, portage, ftp, dns, mixed together
On Saturday 22 August 2009, Jarry wrote:
Hi,
I have a log-server (syslog-ng) collecting logs from my servers.
Everything works for standard logs: clients forward them to server
where they are filtered (based on facility or application) and
splitted into a few files (for each client).
The
Robin Atwood wrote:
1. In /etc/conf.d/local.start add a line
tail -F /var/log/emerge.log | awk '{$1=;print | logger -t emerge -p
local5.info}'
Thanks. First I'll try to figure out what this line actually means! :-)
Jarry
--
___
On Saturday 22 August 2009, Jarry wrote:
Robin Atwood wrote:
1. In /etc/conf.d/local.start add a line
tail -F /var/log/emerge.log | awk '{$1=;print | logger -t emerge -p
local5.info}'
Thanks. First I'll try to figure out what this line actually means! :-)
This was devised by Mike Hunt
7 matches
Mail list logo
