PRs for manpage 'amd(8)'
This is an experimental report containing PRs for manpage 'amd(8)' as of Fri Apr 18 07:36:06 2014 UTC. See notes.
PRs for manpage 'amd(8)':
|o||2013/08/27||kern/181590||[vm] [panic] amd(8) related vm_page_unwire panics|
|o||2011/07/11||kern/158802||fs||amd(8) ICMP storm and unkillable process.|
|o||2010/06/09||bin/147715||amd(8): am-utils hangs when mountd on remote host is not running|
|o||2009/01/30||bin/131143||[patch] amd(8) causes annoying "embedded slash in map name" message|
|o||2008/05/23||bin/123932||amd(8) core dumps while load high|
|o||2008/03/28||bin/122172||fs||[fs]: amd(8) automount daemon dies on 6.3-STABLE i386, fine on amd6|
|o||2006/09/27||bin/103712||amd(8): Automounter is apparently not passing flags to mount_msdosfs with fs type:=pcfs|
|o||2004/08/11||bin/70297||amd(8) request to make amd timeouts per-mount local|
|o||2003/08/07||bin/55349||amd(8) mixes up symlinks in its virtual filesystem.|
GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '<name>(<section>)' to the Synopsis field. Consider this a prototype of a better search function.
Please give feedback on this report to linimon@FreeBSD.org. Thanks.
Bugs can be in one of several states:
- o - open
- A problem report has been submitted, no sanity checking performed.
- a - analyzed
- The problem is understood and a solution is being sought.
- f - feedback
- Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution.
- p - patched
- A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open.
- r - repocopy
- The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion.
- s - suspended
- The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended.
- c - closed
- A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned.