From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Hilst Selli Subject: Re: Show application performance/errors from pseudo file Date: Fri, 17 Oct 2014 16:00:23 -0300 Message-ID: <54416747.2010108@gmail.com> References: <5440216C.3010207@gmail.com> <54416714.6080100@gmail.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=5jpV8cxcd8+SQSW1zHA3V+AX+Ibw8nHqZuK/KyX0x+w=; b=YKGZtWiH9mkDTNG9mwWGR3k5L6OuZg8Y7E6HoZeSZSwwG8xhsrWpYjN6hDiiOYFiFC Ok8nm/JGg/PJwW7rT2CrgKVPt7zvzbEL25jm+gMZH/FFXM6W4rpkhp2OM8GBHm8o1yyY GjuXsRdEwg9Dpec8kl14cSv7Wu3aglDouLAz/5PxywyIsLuKo+EN/mB8bCB9xyhyWrVs 4WXmLZ1kUwBAKhxQy3NhX++3nF+DRO9L9+XXxDNj9hUZiU5SnV2b4eH/dG6Yg/a9O78t 9Y4VCqK02mfR/fuBFo7KHCWFxNcG1bXDVtvcksG+R7AXaE0jRiHxxXKZlkoAVxgPEPz3 YlEg== In-Reply-To: <54416714.6080100@gmail.com> Sender: linux-c-programming-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: "linux-c-programming@vger.kernel.org" On 10/17/2014 03:59 PM, Daniel Hilst Selli wrote: > On 10/16/2014 05:31 PM, Yichao Yu wrote: >> Resend as plain text. >> >> On Thu, Oct 16, 2014 at 4:01 PM, Yichao Yu wrote: >>> >>> >>> On Thu, Oct 16, 2014 at 3:50 PM, Daniel Hilst Selli >>> wrote: >>>> >>>> I'm writing a new application and would be nice to have a pseudo file >>>> showing its status, just the way that procfs does with kernel. >>>> I'm looking for sugestions, I want to `cat' files contents and have >>>> something similar to /proc/meminfo >>>> >>>> First I think using named pipes, but, AFAIK, pipes would retain data >>>> writed until someone read it, what I thought is a kind of read >>>> hook that only show data when asked for. Here are a few requisites, >>>> >>>> - Don't retain data >>>> - Don't generate disk I/O >>>> - Vanish when application stops >>>> - Work with a simple cat or something similar.. >>> >>> >>> You should have a look at fuse[1]. >>> >>> [1] http://fuse.sourceforge.net/ >>> >>>> >>>> >>>> With that in mind I think about using unix domain sockets.. it seems to >>>> fit all requisites, for >>>> the fourth requisite I could use netcat, that is almost cat, >>>> >>>> Cheers >>>> -- >>>> To unsubscribe from this list: send the line "unsubscribe >>>> linux-c-programming" in >>>> the body of a message to majordomo@vger.kernel.org >>>> More majordomo info at http://vger.kernel.org/majordomo-info.html >>> >>> > > Seems god, a little overkill for so simple stuff but adds nice features, I'm taking > a look on further options.. > > Cheers good*