[smf-discuss] Return codes from the mid-level library functions

2009-04-06 Thread David Bustos
Quoth Gary Mills on Fri, Apr 03, 2009 at 07:42:25PM -0700: > > All error codes should be documented. > > I agree. I've certainly seen problems arise when library functions or system > calls > return unexpected error codes. In this case, the full list of return codes > appears > in scf_error(3S

[smf-discuss] Return codes from the mid-level library functions

2009-04-03 Thread Gary Mills
> Quoth Gary Mills on Thu, Mar 26, 2009 at 05:52:50PM > -0700: > > I've done a review of the return codes from these > functions, based on the code and the man > > pages. Although it's not exhaustive, I can see > already that in unusual circumstances they > > can return codes that are not documen

[smf-discuss] Return codes from the mid-level library functions

2009-04-03 Thread David Bustos
Quoth Gary Mills on Thu, Mar 26, 2009 at 05:52:50PM -0700: > I'm investigating one of the bite-sized bugs, specifically 6383235 for > smf_maintain_instance > and related library functions. It suggests that some of the return codes > from these functions > can be aggregated because they don't mak

[smf-discuss] Return codes from the mid-level library functions

2009-03-26 Thread Gary Mills
I'm investigating one of the bite-sized bugs, specifically 6383235 for smf_maintain_instance and related library functions. It suggests that some of the return codes from these functions can be aggregated because they don't make sense to the caller. I've done a review of the return codes from t