Linux LVM users
 help / color / mirror / Atom feed
From: Steven Lembark <lembark@wrkhors.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Writing forward compatible applications using /proc
Date: Sun, 12 Aug 2001 14:13:48 -0500	[thread overview]
Message-ID: <21550000.997643628@dizzy> (raw)
In-Reply-To: <20010812200701.A657@btconnect.com>



> You should also be able to get all the information you need from the
> tools.

Problem with this is (a) having for fork/exec the tool at each
iteration and (b) having to capture/parse stdout/stderr and
check exit/signal status for each call.  Just the error checking
and validating stderr vs. stdout can double the code size for
getting data.

Another way out (which the /proc file system was intended to
avoid) is to put an add'l device file in the VG directory
(e.g., "./status") which delivers a struct or block text
with the same info as /proc has now.  Net result is that a
simple read or fgets will pull in the necessary info w/o
all the extra error checking.


--
Steven Lembark                                               2930 W. Palmer
Workhorse Computing                                       Chicago, IL 60647
                                                            +1 800 762 1582

  reply	other threads:[~2001-08-12 19:13 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-12  3:57 [linux-lvm] Writing forward compatible applications using /proc Jason Tackaberry
2001-08-12 13:54 ` José Luis Domingo López
2001-08-12 15:38   ` Jason Tackaberry
2001-08-12 18:39     ` José Luis Domingo López
2001-08-12 16:39   ` Steven Lembark
2001-08-13  1:55     ` Paul Jakma
2001-08-12 17:10   ` Eric M. Hopper
2001-08-12 22:21     ` José Luis Domingo López
2001-08-12 20:46       ` Ragnar Kjørstad
2001-08-12 22:35     ` Wichert Akkerman
2001-08-12 20:21   ` toon
2001-08-12 19:07 ` Joe Thornber
2001-08-12 19:13   ` Steven Lembark [this message]
2001-08-12 19:26     ` Joe Thornber
2001-08-12 19:51   ` Jason Tackaberry
2001-08-12 20:16   ` Ragnar Kjørstad
2001-08-13  9:08     ` Joe Thornber
2001-08-13 11:27       ` Wichert Akkerman
2001-08-13 12:48         ` Terje Kvernes
2001-08-13 23:49       ` Ragnar Kjørstad
2001-08-14 13:36         ` Heinz J . Mauelshagen
2001-08-14  0:31       ` Nathan Scott
2001-08-14 13:33         ` Heinz J . Mauelshagen
2001-08-13 15:13     ` Alasdair G Kergon
2001-08-13 17:58       ` Jason Tackaberry
2001-08-13 19:44       ` Michael Tokarev
2001-08-13 19:49         ` Wichert Akkerman
2001-08-13 20:18           ` Goetz Bock
2001-08-13 20:47             ` Joe Thornber
2001-08-13 20:31           ` Joe Thornber
2001-08-14  3:04   ` Mark van Walraven
2001-08-14  8:14     ` Joe Thornber
2001-08-14 17:50       ` Ragnar Kjørstad
2001-08-15  8:58         ` Heinz J . Mauelshagen
2001-08-13  9:10 ` Terje Kvernes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=21550000.997643628@dizzy \
    --to=lembark@wrkhors.com \
    --cc=linux-lvm@sistina.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox