On Tue, Apr 17, 2007 at 03:34:45PM +0200, Michael Biebl wrote: > > Other users with similar problems might find the report if it's listed > > with network-manager but they certainly won't find it under quota. > > I don't understand this logic. This error only happens when you have a > setup which uses quota and it's the quota process that hangs. > So, the first thing people will be looking for (as did John), is a > problem with quota.
Sorry, I should have explained better. I was talking about the other problems arising from the network device being downed before a lot of servers and before network filesystems are unmounted. IMO this is way more severe than quota hanging. > > If this is the only solution, fine, but it has to be documented IMO. > > Who said it's the only solution? Oops, please remove the word "only" from my statement. > > But I don't think it makes sense to discuss this detail because more > > severe problems seem to arise from this setup. > > Well, then it probably it should be documented within the quota package, > that it can't deal with network outages. Oh come on. I was talking about the bigger picture. Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]