One last thing:
On 08/19/2011 12:55 PM, Adam Stokes wrote:
This allows 3 ways to test for configuration
status
1) If file exists then in the least the execution
was issued
2) If file exists and contents of file report an
error, then process failed with at least 1 execution
3) If file exists and contents contain a success
message, then binary was executed and successfully
completed.
Signed-off-by: Adam Stokes<astokes(a)fedoraproject.org>
---
src/include/matahari/sysconfig.h | 16 ++++++++++------
src/lib/sysconfig.c | 32 ++++++++++++--------------------
src/lib/sysconfig_linux.c | 15 ++++++++++-----
src/sysconfig/sysconfig-qmf.cpp | 27 +++++++++++++--------------
src/tests/mh_api_sysconfig.h | 4 ++--
5 files changed, 47 insertions(+), 47 deletions(-)
diff --git a/src/include/matahari/sysconfig.h b/src/include/matahari/sysconfig.h
index 0390528..5767274 100644
--- a/src/include/matahari/sysconfig.h
+++ b/src/include/matahari/sysconfig.h
@@ -77,21 +77,23 @@ mh_sysconfig_query(const char *query, uint32_t flags, const char
*scheme);
* Set system as configured
*
* \param[in] key config item to define
+ * \param[in] contents specifies success/fail with error where applicable
*
- * \return TRUE if applying key to config succeeds
+ * \return STATUS of spawned process return code
*/
-extern gboolean
-mh_sysconfig_set_configured(const char *key);
+extern char *
+mh_sysconfig_set_configured(const char *key, const char *contents);
Does anything use this char * return value? If not, I would change it
back to a success/fail int.
--
Russell Bryant