From mboxrd@z Thu Jan 1 00:00:00 1970 From: Walt H Subject: Re: default quota limits in linux (via quotactl()) Date: Tue, 28 Jan 2003 07:18:42 -0800 Sender: linux-xfs-bounce@oss.sgi.com Message-ID: <3E369F52.7050901@comcast.net> References: <20030128112034.GA23731@f00f.org> <5.2.0.9.2.20030127150905.0217e170@post.strato.de> <5.2.0.9.2.20030127150905.0217e170@post.strato.de> <5.2.0.9.2.20030128074810.0218c4f8@post.webmailer.de> <20030128093250.GM28513@vagabond> <20030128094014.GA23257@f00f.org> <20030128094619.GO28513@vagabond> <20030128101310.GA23320@f00f.org> <20030128105747.GR28513@vagabond> <20030128112034.GA23731@f00f.org> <5.2.0.9.2.20030128142729.0218f398@post.webmailer.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Jan Hudec , Chris Wedgwood , "Stephen C. Tweedie" , viro@math.psu.edu, linux-fsdevel@vger.kernel.org, akpm@zip.com.au, Andreas Dilger , ext2-devel@lists.sourceforge.net, jfs-discussion@www-124.southbury.usf.ibm.com, linux-xfs@oss.sgi.com, Alexander Bokovoy Return-path: To: "Stefan (metze) Metzmacher" In-Reply-To: <5.2.0.9.2.20030128142729.0218f398@post.webmailer.de> Errors-to: linux-xfs-bounce@oss.sgi.com List-Id: linux-fsdevel.vger.kernel.org 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 >