Gary Winiger writes: > I'm sponsoring this case for Paul Roberts and the Audit Project team. > It incompatibly modifies the Evolving auditconfig(1M) and Committed > auditon(2) interfaces to reflect the present implementation. > It requests a Patch release binding and permission to remove the > non-functioning interfaces in a patch even if the replacement functionality > is not present in the same Patch.
It'd help a bit to have an evaluation in CR 6185615; I'm missing some background in reading this case. Why not make auditconfig set the new p_fsize parameter in response to the -setfsize keyword, or alternatively have audit_binfile read the parameter on start-up from some common location into which -setfsize writes? I assume there's some sort of timing problem involved, but I'm not sure what it is. It seems a little odd that our response to a broken public interface, with three external customers filing service requests plus internal reports of trouble, and with three escalations, would be to document the brokenness in a patch. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
