*** This bug is a duplicate of bug 649591 ***
https://bugs.launchpad.net/bugs/649591
I believe this bug should be considered a duplicate of bug 649591 which
was found, filed, fixed, and released today. Thank you Scott Moser for
getting the attention of Colin Watson.
Since that bug is already
I just tested Sika's patch and it works.
--
mountall eats 100% cpu in fstab
https://bugs.launchpad.net/bugs/574044
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
https://lists.ub
Update status as there's a patch.
** Changed in: mountall (Ubuntu)
Status: New => In Progress
--
mountall eats 100% cpu in fstab
https://bugs.launchpad.net/bugs/574044
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
Any news on this bug? Has anybody looked at my patch?
--
mountall eats 100% cpu in fstab
https://bugs.launchpad.net/bugs/574044
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
htt
** Tags added: patch
--
mountall eats 100% cpu in fstab
https://bugs.launchpad.net/bugs/574044
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
https://lists.ubuntu.com/mailman/lis
Hi!
I'm affected by this bug too.
I've written a patch which should fix the problem.
Tested on my install and it seems to work.
Can someone please test/review/commit it please?
Thanks!
** Patch added: "Fix infinite loop in cut_options"
http://launchpadlibrarian.net/52648784/patch_mountall.patch
The "nobootwait" option is one that mountall strips. Since that option
is not at the end of the list, you are falling foul of this bug. If you
move that option to the end of your options list, you will work around
but bug and you will be able to boot.
Does anybody know how to get attention for thi
I'm seeing this with some NFS mounts I have defined as:
fileserver:/media/storage/1 /media/storage/1nfs
nobootwait,users,bg,defaults0 0
fileserver:/media/storage/2 /media/storage/2nfs
nobootwait,users,bg,defaults0 0
fileserver:/media/storage/3
