syslogd.3:

- added a BUGS section
	- added info regarding syslogmt and vsyslogmt
sprintmt.3:
	- fixed a typo

usr.man/man3/sprintmt.3

@@ -1,6 +1,6 @@
 .\" Man page by Devin Reade.
 .\"
-.\" $Id: sprintmt.3,v 1.1 1998/10/25 17:15:51 gdr-ftp Exp $
+.\" $Id: sprintmt.3,v 1.2 1999/01/06 03:44:45 gdr-ftp Exp $
 .\"
 .TH SPRINTMT 3 "24 October 1998" GNO "Library Routines"
 .SH NAME
@@ -32,7 +32,7 @@ is copied into the user supplied
 .IR buffer .
 At most, 
 .IR bufferlen -1
-characters will be written 
+characters will be written to
 .IR buffer .
 .LP
 These routines have a much more limited set of format specifiers than 

usr.man/man3/syslog.3

@@ -31,7 +31,7 @@
 .\"
 .\"     @(#)syslog.3	8.1 (Berkeley) 6/4/93
 .\"
-.TH SYSLOG 3 "28 January 1997" GNO "Library Routines"
+.TH SYSLOG 3 "4 January 1999" GNO "Library Routines"
 .SH NAME
 .BR syslog ,
 .BR vsyslog ,
@@ -113,6 +113,22 @@ or
 The full list of format specifiers is given in the
 .BR sprintmt (3)
 manual page.
+Note that
+.BR syslogmt
+and
+.BR vsyslogmt
+will
+.I not
+log to 
+.BR syslogd (8)
+unless 
+.BR openlog
+has been called.  Since
+.BR openlog
+is not itself thread safe, the call to
+.BR openlog
+must be made before the process forks if any children will be using these 
+routines.
 These two routines are GNO-specific and therefore non-portable.
 .LP
 The message is tagged with
@@ -299,6 +315,16 @@ are thread safe; the remainder are not.
 should be called in the parent thread before creating the child threads.
 This will ensure that any generated messages are properly tagged with
 .IR ident .
+.SH BUGS
+The current implementation does not take into account the possibility that 
+.BR syslogd (8) 
+may be killed and restarted.  If this happens, all logging from the current
+process will stop until a call is made to 
+.BR closelog
+followed by
+.BR openlog ,
+which is of course not thread safe.
+This could be handled better.
 .SH SEE ALSO
 .BR logger (1),
 .BR sprintmt (3),