From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <shaklee3@gmail.com>
Received: from mail-vk0-f47.google.com (mail-vk0-f47.google.com
 [209.85.213.47]) by dpdk.org (Postfix) with ESMTP id 427362935
 for <users@dpdk.org>; Wed, 29 Jun 2016 18:21:32 +0200 (CEST)
Received: by mail-vk0-f47.google.com with SMTP id m127so13348673vkb.3
 for <users@dpdk.org>; Wed, 29 Jun 2016 09:21:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:from:date:message-id:subject:to;
 bh=4EwmjRpDjs/VWNuWjEQBJ/WkldDoyhKqr2f0Plh8br4=;
 b=iywgRw1YeWlE4VpTZCmHI3hfvnGipYuf3PEXXZMltByyz01u3hYgYyZAeVwaFJx51w
 4tVtHU5JYQwWxaF0d83W2euvnKhsnO1tzFRdg+5Y3D+X/R2d0mX+Nlz4+Sj5ksfmOo8R
 Vkl7oML1uLFQ/7y9Y/7avWvzkO0bvnyd/YVHOsYccMf+Cu4CNk+3H5i6ypvArGCQIPRl
 gPZ3PdbMtTOP079dUh03B7OyTJ4ggUCLiaFjekSQJY9BGjjdr9ZLZt07ft49Bzfg9gzF
 pit+IpexetwAGzP3ajhBkWILEa8RtTqMlH/YNE7fLy/NCZB7nue2Wd4Pp/MLPgBVr27y
 dLDw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
 bh=4EwmjRpDjs/VWNuWjEQBJ/WkldDoyhKqr2f0Plh8br4=;
 b=k43TvgovbyUikGlN/8zQXlzSebTja5dXsaW0n83wfwfKQkz/WI4teV768VCKKLuHqX
 lsvHzeOWwa/luZh8w88s5eIhf1WXcTS9RE4c5Fq+/LR1bPxv/CCm8kqwsIo0WSDREMKa
 6c7aDnAK0kkIZYdVqiqzWhMnuWYifRizdMcZv9j5/LPNipHAJ2JQZYlmb4OBmJhnHi0o
 9979TFIV927FV7sF+8W9KaHJ0PH/aSHVY233Tt8wC5q7snu5VrKrulcMcFltPJs5OJIh
 uBH7nnVwNSYmiYbUhq8oMqNJwAPwD4pfn6624EN/K0mNtmjGUvDJeTnAzE8hQovKSBeg
 tYTA==
X-Gm-Message-State: ALyK8tLFh7iQavG4+5bCXOps/17/zoHZd6vEu9AICak4O+q0QebI8FB9S+PbHrffW+E2DTHwZRHHL1cl3lASZA==
X-Received: by 10.176.64.199 with SMTP id i65mr4184892uad.41.1467217291675;
 Wed, 29 Jun 2016 09:21:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.159.37.183 with HTTP; Wed, 29 Jun 2016 09:21:31 -0700 (PDT)
From: Cliff Burdick <shaklee3@gmail.com>
Date: Wed, 29 Jun 2016 09:21:31 -0700
Message-ID: <CA+Gp1nZmXU4iC1_GKwvys8CEDiiiq+g-ECjgzrKGA-oOHVZjFw@mail.gmail.com>
To: users <users@dpdk.org>
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [dpdk-users] Capture EAL Output For Logging
X-BeenThere: users@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: usage discussions <users.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/users>,
 <mailto:users-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/users/>
List-Post: <mailto:users@dpdk.org>
List-Help: <mailto:users-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/users>,
 <mailto:users-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jun 2016 16:21:32 -0000

Hi, if I have my own logging mechanism, is there a way to capture the EAL
output, especially on startup? The best way I can think of is to open a
pipe to a child process that reads from stdout, and logs from there, but
that seems like somewhat of a hack. I've seen patches that seem like they
may be useful here:

http://dpdk.org/ml/archives/dev/2013-May/000139.html

But I believe this just lets you change the syslog facility while the
console messages still go out. I would like to silence EAL to the console
completely, and instead send each line to my custom logger. Has anyone does
this?