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

Site Navigation

PRs for tag 'libutil'

This is an experimental report containing PRs for tag 'libutil' as of 4-19-2014. 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 'libutil':
SSubmittedTrackerResp.Description
o2013/04/07kern/177698[libutil] [patch] sshd sets the user's MAC label at the same time it attempts to set the login class, which can cause the latter to fail if mac_biba is used.
o2012/08/30kern/171192[libutil] [request] pidfile_read should be made a public interface
o2005/08/11kern/84797[libutil] [patch] State engine in the libutils properties_read is not safe over incremental reads
s2002/05/20kern/38347[libutil] [patch] [request] new library function abs2rel and rel2abs.
o2002/03/11kern/35774[libutil] logwtmp: Suboptimal auditing possibilities for network access
5 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.