Skip site navigation (1)Skip section navigation (2)

Site Navigation

PRs for tag 'jail'

This is an experimental report containing PRs for tag 'jail' as of 5-25-2012. GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '[<tagname>]' to the Synopsis field. Consider this a prototype of a better search function.

This report is generated statically.

Please give feedback on this report to linimon@FreeBSD.org. Thanks.


PRs for tag 'jail':
SSubmittedTrackerResp.Description
o2011/08/19kern/159918jail[jail] inter-jail communication failure
o2011/04/22kern/156584bz[jail] ipv4 packet is not forward to v4-mapped binding in jail
o2011/04/01kern/156111jail[jail] procstat -b not supported in jail
o2011/01/23conf/154246jail[jail] [patch] Bad symlink created if devfs mount point does not exist on jail startup
o2010/11/21conf/152465simon[jail] [patch] devfs is mounted in jails without rules if devfs.rules can't be parsed
o2010/07/29conf/149050jail[jail] rcorder ``nojail'' too coarse for Jail+VNET
o2010/04/06kern/145444secteam[jail] sysinstall and sade can access host's disks from within a jail
o2010/01/19conf/142973rc[jail] [patch] Strange counter init value in jail rc
s2010/01/19conf/142972jail[jail] [patch] Support JAILv2 and vnet in rc.d/jail
o2009/04/01kern/133265jail[jail] is there a solution how to run nfs client in jail environment?
o2008/06/03conf/124248rc[jail] [patch] add support for nice value for rc.d/jail + rc.conf
o2008/01/20kern/119842jail[smbfs] [jail] "Bad address" with smbfs inside a jail
o2006/06/28bin/99566jail[jail] [patch] fstat(1) according to specified jid
o2005/03/13bin/78763pjd[patch] [jail] Added jail support to ps(1)
o2003/02/19kern/48471pjd[jail] [patch] [request] private IPC for every jail
o2001/12/14bin/32828jail[jail] w(1) incorrectly handles stale utmp slots with jail
s1999/09/27kern/13997rwatson[jail] [patch] RLIMIT_NPROC works unadequately for jails
17 problems total.

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.