> I'm not saying, that quota is at fault here. I reassigned the bug mostly
So why did you reassign the bug to quota? > because it's imho not a bug in network-manager. network-manager is > simply not conceived for such a use case. 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. > network-manager is intended for highly dynamic network environments, > where networks come and go and where you switch between different networks. > Removing network-manager is probably the best "bug fix" there is atm. > For a static configuration with NFS mounts etc, as Johns' setup, I would > recommend to use plain ifupdown. If this is the only solution, fine, but it has to be documented IMO. > P.S.: What happens if you pull the network plug? Will quota then also > fail to stop? Is this a matter of how the nfs share was mounted (hard or > soft)? Problem is (at least I think it is) that quota stats the mountpoint which then fails because the server does not respond anymore (obviously). But I don't think it makes sense to discuss this detail because more severe problems seem to arise from this setup. 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!