Peter Jeremy wrote:...snip... Regarding syslogd, I've considered adding support to batch/buffer writes to workaround a problem that I consider rather important: syslogd is not started early enough in the boot so it's not available to log msgs from other applications. In particular I hit this because wpa_supplicant logs via syslog but when it's started at boot syslogd isn't available and since wpa_supplicant operates in a chroot'd environment it cannot defer connecting until syslogd has started up so nothing is ever logged. I think we want syslogd to start very early and deal with the case where the local filesystem is not present. My plan was to buffer msgs and then flush them at a later time. But this might also be used to buffer log activity so local disk activity is staged (e.g. for the laptop or embedded use). Maybe someone else has a better idea but I think we need to do something soon. Sam _______________________________________________ firstname.lastname@example.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "email@example.com"