| 1 |
Hi, |
| 2 |
I have a log-server (syslog-ng) collecting logs from my servers. |
| 3 |
Everything works for standard logs: clients forward them to server |
| 4 |
where they are filtered (based on facility or application) and |
| 5 |
splitted into a few files (for each client). |
| 6 |
|
| 7 |
The problem is with portage logs: I can not find any pattern |
| 8 |
I could use to filter them out. For example, this is small part |
| 9 |
of /var/log/emerge.log: |
| 10 |
|
| 11 |
1250923552: *** emerge sync |
| 12 |
1250923552: === sync |
| 13 |
1250923552: >>> Starting rsync with rsync://140.211.166.165/gentoo-portage |
| 14 |
1250923665: === Sync completed with rsync://140.211.166.165/gentoo-portage |
| 15 |
1250923666: *** terminating. |
| 16 |
1250923760: Started emerge on: Aug 22, 2009 06:49:20 |
| 17 |
1250923760: *** emerge depclean |
| 18 |
1250923760: >>> depclean |
| 19 |
... |
| 20 |
|
| 21 |
Can I somehow force portage to write all its logs (summary.log, |
| 22 |
emerge-fetch.log, emerge.log) in standard syslog format RFC-3164? |
| 23 |
I mean with all that stuff like priority (facility), header |
| 24 |
(timestamp, hostname), application, etc. Even better if portage |
| 25 |
could write its logs to /dev/log... |
| 26 |
|
| 27 |
Jarry |
| 28 |
|
| 29 |
-- |
| 30 |
_______________________________________________________________ |
| 31 |
This mailbox accepts e-mails only from selected mailing-lists! |
| 32 |
Everything else is considered to be spam and therefore deleted. |
Archives