From: ST <smntov@gmail.com>
To: Marat Khalili <mkh@rqc.ru>
Cc: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>,
linux-btrfs@vger.kernel.org
Subject: Re: Several questions regarding btrfs
Date: Thu, 02 Nov 2017 18:28:59 +0200 [thread overview]
Message-ID: <1509640139.1662.147.camel@gmail.com> (raw)
In-Reply-To: <E7316F3D-708C-4D5E-AB4B-F54B0B8471C1@rqc.ru>
On Thu, 2017-11-02 at 19:16 +0300, Marat Khalili wrote:
> > Could somebody among developers please elaborate on this issue - is
> checking quota going always to be done by root? If so - btrfs might be
> a no-go for our use case...
>
> Not a developer, but sysadmin here: what prevents you from either
> creating suid executable for this or configuring sudoers to let users
> call specific commands they need?
1. If designers have decided to limit access to that info only to root -
they must have their reasons to do so, and letting everybody do that is
probably contrary to those reasons.
2. I want to limit access to sftp, so there will be no custom commands
to execute...
3. sftp clients (especially those for windows) can determine quota - and
they do it probably in some standard way - which doesn't seem to be
compatible with btrfs...
next prev parent reply other threads:[~2017-11-02 16:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 16:23 Several questions regarding btrfs ST
2017-10-31 17:45 ` Austin S. Hemmelgarn
2017-10-31 18:51 ` Andrei Borzenkov
2017-10-31 19:07 ` Austin S. Hemmelgarn
2017-10-31 20:06 ` ST
2017-11-01 12:01 ` Austin S. Hemmelgarn
2017-11-01 14:05 ` ST
2017-11-01 15:31 ` Lukas Pirl
2017-11-01 17:20 ` Austin S. Hemmelgarn
2017-11-02 9:09 ` ST
2017-11-02 11:01 ` Austin S. Hemmelgarn
2017-11-02 15:59 ` ST
[not found] ` <E7316F3D-708C-4D5E-AB4B-F54B0B8471C1@rqc.ru>
2017-11-02 16:28 ` ST [this message]
2017-11-02 17:13 ` Austin S. Hemmelgarn
2017-11-02 17:32 ` Andrei Borzenkov
2017-11-01 17:52 ` Andrei Borzenkov
2017-11-01 18:28 ` Austin S. Hemmelgarn
2017-11-01 12:15 ` Duncan
-- strict thread matches above, loose matches on Subject: below --
2017-10-31 16:29 ST
2017-11-06 21:48 ` waxhead
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=1509640139.1662.147.camel@gmail.com \
--to=smntov@gmail.com \
--cc=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mkh@rqc.ru \
/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.