10 messages in ru.sysoev.nginxRe: logging into script| From | Sent On | Attachments |
|---|---|---|
| Dennis J. | Jan 13, 2010 9:12 pm | |
| 任晓磊 | Jan 13, 2010 9:13 pm | |
| Peter Leonov | Jan 13, 2010 10:02 pm | |
| Juergen Gotteswinter | Jan 14, 2010 12:10 am | |
| Kruglov Eugenie | Jan 14, 2010 12:36 am | |
| Dennis J. | Jan 14, 2010 4:51 am | |
| Igor Sysoev | Jan 14, 2010 5:51 am | |
| Dennis J. | Jan 14, 2010 6:48 am | |
| Maxim Dounin | Jan 14, 2010 7:03 am | |
| Valery Kholodkov | Jan 14, 2010 9:01 am |
| Subject: | Re: logging into script | |
|---|---|---|
| From: | Dennis J. (denn...@conversis.de) | |
| Date: | Jan 14, 2010 4:51:36 am | |
| List: | ru.sysoev.nginx | |
Why is logging into a pipe considered a waste of CPU? The log parser throws away some data, aggregates the rest and then writes it to a remote database. The "tail -f" approach would waste lokal disk i/o by writing data unnecessarily to disk which i would then have to read again with the script. Why is this considered more efficient than handing the data directly over to a script?
Regards, Dennis
On 01/14/2010 07:03 AM, Peter Leonov wrote:
This thread might be of help: http://nginx.org/pipermail/nginx/2009-June/013042.html
Ny the way "tail -F" is the only recommended way to do the near real-time log
parsing with nginx.
On 14.01.2010, at 8:12, Dennis J. wrote:
Hi,
Is there a nginx equivalent to apaches CustomLog directive with the "|" prefix
so it logs into stdin of another program/script? I need to do real-time
processing of the access log data and I'm wondering how I can accomplish this
once I switch to nginx.
Regards, Dennis
_______________________________________________ nginx mailing list ngi...@nginx.org http://nginx.org/mailman/listinfo/nginx
_______________________________________________ nginx mailing list ngi...@nginx.org http://nginx.org/mailman/listinfo/nginx