We've also seen this bug (looping through automounted user home
directories leads to errors after about the first 100 mounts).
Surprisingly, this seems to be related to automount defaulting to using
tcp instead of udp for its nfs mounts (nfs documentation claims udp is
the default, but with autofs
Amending my prior comment: I stand by the two suggested work-arounds,
but retract my theory that the problem has to do with how many TCP
sockets are in TIME_WAIT.
If you google autofs TIME_WAIT and autofs nfs bindresvport address
already in use and autofs can't read superblock (the latter two
Pedro: Is there any way to get this fix into ubuntu-updates (not ubuntu-
security) for Hardy 8.04 LTS? Although not a security issue, it is a
significant enduser annoyance issue (the number of duplicate bug reports
attests to that), and Hardy 8.04 is marked LTS indicating that it
should be okay to
Ian Taylor asked:
Is this really a bug?
It's not a bug insofar as functionality is concerned: the quota numbers are
reported correctly, quotas are enforced correctly. It
is simply confusing to user1 that when they issue quota they
are misled into believing someone else's quota is being
Same bug exists in 8.04 Hardy LTS.
--
quota only displays the first automounted file-system
https://bugs.launchpad.net/bugs/120490
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Hi Kees,
Thanks for your prompt attention. Just to clarify my possible
misunderstanding, does Status: New = Invalid mean this won't get
fixed in Hardy?
Hardy is supposed to be an LTS release and we plan to stick with it
for a couple years, so this being already fixed in the development
release
Kees wrote:
[...] This bug seems relatively minor
I respectfully disagree. Users expect a stable system to be, umm,
stable. When applications randomly quit and cause data loss, this is
hardly stable. Novice users concerned about security might blindly
install chkrootkit based on a friend's tip,
My claim that this bug fix is the only change from Debian 0.47-1.1 to
0.47-2 was based on the Debian Changelog for 0.47-2. I didn't examine
the source, and apologize if my report was misleading.
At any rate, thank you Francois for providing the diff, and thank you
Kees for your attention and
