From: Walt H <waltabbyh@comcast.net>
To: "Stefan (metze) Metzmacher" <metze@metzemix.de>
Cc: Jan Hudec <bulb@ucw.cz>, Chris Wedgwood <cw@f00f.org>,
"Stephen C. Tweedie" <sct@redhat.com>,
viro@math.psu.edu, linux-fsdevel@vger.kernel.org,
akpm@zip.com.au, Andreas Dilger <adilger@clusterfs.com>,
ext2-devel@lists.sourceforge.net,
jfs-discussion@www-124.southbury.usf.ibm.com,
linux-xfs@oss.sgi.com,
Alexander Bokovoy <a.bokovoy@sam-solutions.net>
Subject: Re: default quota limits in linux (via quotactl())
Date: Tue, 28 Jan 2003 07:18:42 -0800 [thread overview]
Message-ID: <3E369F52.7050901@comcast.net> (raw)
In-Reply-To: <5.2.0.9.2.20030128142729.0218f398@post.webmailer.de>
I believe that the hotplug stuff does this. When a new hotpluggable pci,
usb etc... device is plugged into the system, it triggers /sbin/hotplug
to run to look for the appropriate kernel module to provide a driver.
-Walt
Stefan (metze) Metzmacher wrote:
> At 13:37 28.01.2003 +0100, Jan Hudec wrote:
>
>> On Tue, Jan 28, 2003 at 03:20:34AM -0800, Chris Wedgwood wrote:
>> > On Tue, Jan 28, 2003 at 11:57:47AM +0100, Jan Hudec wrote:
>> >
>> > > So you can only setquota for the users that actualy log in
>> >
>> > the API allows you to set quota for any valid uid/gid
>>
>> Yes, it does. But since there is many more valid users than those
>> actualy using the system, you don't want to... And a logged in user is
>> sure valid, so no problem there, right?
>>
>> > > Well, it get's complicated, but you still can setquota in the local
>> > > delivery process... I know it get's a bit complicated...
>> >
>> > sure, this is a perfectly legitimate argument and a fairly reasonable
>> > solution to this case
>>
>> If it finaly got too complicated, you could add a simple code to kernel,
>> that would run_usermodehelper and provide a user mode program to fix
>> things up. That might even get a chance of being accepted. (And it would
>> be more flexible since it can get the default quota from LDAP etc...)
>
>
> is there an example( another place in the kernel where the kernel
> callback a userspace tool)
>
> can you point me to the place (the function) where the quota
> entry/object will be created for new users,
> so this should be the location where the userspace tool should be
> callback...
>
> that would be a cool solution, witch I could accept too:-)
>
>
>
>
> metze
> -----------------------------------------------------------------------------
>
> Stefan "metze" Metzmacher <metze@metzemix.de>
>
next prev parent reply other threads:[~2003-01-28 15:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-27 14:41 default quota limits in linux (via quotactl()) Stefan (metze) Metzmacher
2003-01-27 16:22 ` Stephen C. Tweedie
2003-01-28 6:43 ` Stefan (metze) Metzmacher
2003-01-28 6:54 ` Stefan (metze) Metzmacher
2003-01-28 9:32 ` Jan Hudec
[not found] ` <20030128094014.GA23257@f00f.org>
2003-01-28 9:46 ` Jan Hudec
[not found] ` <20030128101310.GA23320@f00f.org>
2003-01-28 10:57 ` Jan Hudec
[not found] ` <20030128112034.GA23731@f00f.org>
2003-01-28 12:37 ` Jan Hudec
2003-01-28 13:32 ` Stefan (metze) Metzmacher
2003-01-28 15:18 ` Walt H [this message]
2003-01-28 15:27 ` Stefan Metzmacher
2003-01-29 16:34 ` Juan Quintela
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=3E369F52.7050901@comcast.net \
--to=waltabbyh@comcast.net \
--cc=a.bokovoy@sam-solutions.net \
--cc=adilger@clusterfs.com \
--cc=akpm@zip.com.au \
--cc=bulb@ucw.cz \
--cc=cw@f00f.org \
--cc=ext2-devel@lists.sourceforge.net \
--cc=jfs-discussion@www-124.southbury.usf.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=metze@metzemix.de \
--cc=sct@redhat.com \
--cc=viro@math.psu.edu \
/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