On Tue, 10 Jul 2001, Jim Breton wrote:
> 
> Restarting syslogd makes everything work fine again, until the next time
> it happens.

Note that restarting syslogd might make it work fine again, but many
daemons will now have a disconnected logging socket and will never
syslog again.  See PR#8065 and PR#11087.

You still practically have to reboot after you restart syslogd.

Here's my current work-around  :-)

Index: etc/rc.d/syslogd
===================================================================
RCS file: /cvs/NetBSD/src/etc/rc.d/syslogd,v
retrieving revision 1.1.1.3
diff -c -r1.1.1.3 syslogd
*** etc/rc.d/syslogd	2001/03/25 06:16:59	1.1.1.3
--- etc/rc.d/syslogd	2001/07/11 05:59:32
***************
*** 14,19 ****
--- 14,21 ----
  pidfile="/var/run/${name}.pid"
  required_files="/etc/syslog.conf"
  start_precmd="syslogd_precmd"
+ stop_precmd="syslogd_warn"
+ restart_cmd="syslogd_restart"
  extra_commands="reload"
  
  syslogd_precmd()
***************
*** 34,39 ****
--- 36,53 ----
  	fi
  
  	return 0
+ }
+ 
+ syslogd_warn()
+ {
+ 	echo "WARNING: $name should not be restarted; use '$0 reload' instead." 1>&2
+ 	return 0
+ }
+ 
+ syslogd_restart()
+ {
+ 	syslogd_warn
+ 	return 1
  }
  
  load_rc_config $name


-- 
							Greg A. Woods

+1 416 218-0098      VE3TCP      <gwoods@acm.org>     <woods@robohack.ca>
Planix, Inc. <woods@planix.com>;   Secrets of the Weird <woods@weird.com>