From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <longtb5@viettel.com.vn>
Received: from mailfilter01.viettel.com.vn (mailfilter01.viettel.com.vn
 [125.235.240.53]) by dpdk.org (Postfix) with ESMTP id 16CEF2965
 for <users@dpdk.org>; Tue, 17 Jul 2018 14:37:32 +0200 (CEST)
X-IronPort-AV: E=Sophos;i="5.51,365,1526317200"; d="scan'208";a="81355582"
Received: from 125.235.240.44.adsl.viettel.vn (HELO mta1.viettel.com.vn)
 ([125.235.240.44])
 by mailfilter01.viettel.com.vn with ESMTP; 17 Jul 2018 19:37:31 +0700
Received: from localhost (localhost [127.0.0.1])
 by mta1.viettel.com.vn (Postfix) with ESMTP id 538586135FC
 for <users@dpdk.org>; Tue, 17 Jul 2018 19:37:19 +0700 (ICT)
Received: from mta1.viettel.com.vn ([127.0.0.1])
 by localhost (mta1.viettel.com.vn [127.0.0.1]) (amavisd-new, port 10032)
 with ESMTP id uNs6nanBgHtU for <users@dpdk.org>;
 Tue, 17 Jul 2018 19:37:19 +0700 (ICT)
Received: from localhost (localhost [127.0.0.1])
 by mta1.viettel.com.vn (Postfix) with ESMTP id 2EB2F6135FB
 for <users@dpdk.org>; Tue, 17 Jul 2018 19:37:19 +0700 (ICT)
X-Virus-Scanned: amavisd-new at 
Received: from mta1.viettel.com.vn ([127.0.0.1])
 by localhost (mta1.viettel.com.vn [127.0.0.1]) (amavisd-new, port 10026)
 with ESMTP id tCFpSYpQf_-u for <users@dpdk.org>;
 Tue, 17 Jul 2018 19:37:19 +0700 (ICT)
Received: from ANMLONGTB5 (unknown [27.68.241.28])
 by mta1.viettel.com.vn (Postfix) with ESMTPSA id EEFD66135F9
 for <users@dpdk.org>; Tue, 17 Jul 2018 19:37:18 +0700 (ICT)
To: <users@dpdk.org>
References: 
In-Reply-To: 
Message-ID: <002801d41dcb$d67649f0$8362ddd0$@viettel.com.vn>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdQdgtoTn7zyF0a8TziIv6fOSUv24wASJPrQ
Content-Language: en-us
MilterAction: FORWARD
Date: Tue, 17 Jul 2018 19:37:19 +0700 (ICT)
From: longtb5@viettel.com.vn
Subject: Re: [dpdk-users] Logging with syslog
X-BeenThere: users@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK usage discussions <users.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/users>,
 <mailto:users-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/users/>
List-Post: <mailto:users@dpdk.org>
List-Help: <mailto:users-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/users>,
 <mailto:users-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jul 2018 12:37:33 -0000

Hi,

As it turns out, implementing a custom logstream with fopencookie() is
rather trivial. Sample code can be found online (google dpdk fopencookie)
and inside EAL source code as well. 

> -----Original Message-----
> From: Bao Long Tran [mailto:longtb5@viettel.com.vn]
> Sent: Tuesday, July 17, 2018 11:17 AM
> To: 'users@dpdk.org' <users@dpdk.org>
> Subject: Logging with syslog
> 
> Hi,
> 
> I'm trying to improve the logging system for my application. From my
> understanding, the default log_stream is fopencookie()'d to enable sending
> logs to syslog as well. However, for my use case, logs should always be
sent
> to syslog, but not always written to stdout as it would clog up my command
> line interface (I'm using rte_cmdline).
> 
> Is there a way to achieve this with available DPDK logging utilities via
some
> kind of configuration? Or must I manually create another log_stream with
> fopencookie()?
> 
> Thanks and best regards,
> -BL