--- projects/libstatgrab/docs/libstatgrab/statgrab.xml	2004/05/05 10:41:42	1.11
+++ projects/libstatgrab/docs/libstatgrab/statgrab.xml	2004/07/18 20:48:57	1.12
@@ -6,8 +6,8 @@
 <refentry id="statgrab">
 
   <refentryinfo>
-    <date>$Date: 2004/05/05 10:41:42 $</date>
-    <releaseinfo>$Id: statgrab.xml,v 1.11 2004/05/05 10:41:42 tdb Exp $</releaseinfo>
+    <date>$Date: 2004/07/18 20:48:57 $</date>
+    <releaseinfo>$Id: statgrab.xml,v 1.12 2004/07/18 20:48:57 ats Exp $</releaseinfo>
   </refentryinfo>
 
   <refmeta>
@@ -43,6 +43,10 @@
         <void/>
       </funcprototype>
       <funcprototype>
+        <funcdef>int<function>sg_get_error_errno</function></funcdef>
+        <void/>
+      </funcprototype>
+      <funcprototype>
         <funcdef>const char *<function>sg_str_error</function></funcdef>
         <paramdef>sg_error <parameter>code</parameter></paramdef>
       </funcprototype>
@@ -161,9 +165,14 @@
       The first, <function>sg_get_error</function> returns an sg_error code
       which relates to the last error generated by libstatgrab. This can be
       converted to a string by calling <function>sg_str_error</function>
-      giving the sg_error code as an argument. Finally, an optional
+      giving the sg_error code as an argument. An optional
       argument may be set when the error was generated. This can be
-      accessed by calling <function>sg_get_error_arg</function>.
+      accessed by calling <function>sg_get_error_arg</function>;
+      <constant>NULL</constant> will be returned if no argument has
+      been set. Some errors will also record the value of the system
+      errno variable when the error occurred; this can be retrieved by
+      calling <function>sg_get_error_errno</function>, which will
+      return <constant>0</constant> if no valid errno has been recorded.
     </para>
     <para>
       It is the intended practice that whenever a libstatgrab function is