From: "Dieter Stüken" <stueken@conterra.de>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Resend: API for retrieving linux lvm information
Date: Wed, 13 Jul 2005 11:03:20 +0200 [thread overview]
Message-ID: <42D4D8D8.6050203@conterra.de> (raw)
In-Reply-To: <20040907094413.GA6264@agk.surrey.redhat.com>
Alasdair G Kergon wrote:
> These answers are for LVM2.
>
> On Mon, Sep 06, 2004 at 11:04:09PM -0700, Stanley Yue wrote:
>
>>1) Is there any api library for retrieve linux lvm configuration? I.e.
>>querying for all the vg(s), pv(s), lv(s) on the system?
>
> The commands: lvs, pvs, vgs with numerous cmdline flags.
> See lib/report/columns.h for field names
liblvm.a seems handy, to generate lvm command line tools, but I'm missing
a clear differentiation between modifying and non modifying usage.
I'm asking, as I want to develop some lvm information system running
as a web service to provide a quick overview about my lvm configuration
and status. Thus I definitely want to run it as non root. I might use
those nice lvs,pvs,vgs commands, but I don't want to provide them with
a suid-bit, as they are potentially able to modify my lvm. The former
/proc interface was ideal for this purpose, but it seems to be missing for
LVM2. Are there any plans, to provide lvm informations via /proc or /sys
again, or would it be possible to write somehow "restricted" lvm-tools
using liblvm?
Dieter.
--
Dieter St�ken, con terra GmbH, M�nster
stueken@conterra.de
http://www.conterra.de/
(0)251-7474-501
prev parent reply other threads:[~2005-07-13 9:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-07 6:04 [linux-lvm] Resend: API for retrieving linux lvm information Stanley Yue
2004-09-07 9:44 ` Alasdair G Kergon
2004-09-08 1:39 ` Stanley Yue
2004-09-08 9:35 ` Alasdair G Kergon
2004-09-08 23:51 ` Stanley Yue
2005-07-13 9:03 ` Dieter Stüken [this message]
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=42D4D8D8.6050203@conterra.de \
--to=stueken@conterra.de \
--cc=linux-lvm@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.