syslog, blocking, and lost messages

[Reginald Perrin]

Hi folks,

We are using busybox within an embedded system (battery operated), and we are 
using busybox's syslogd to record all our messages (application and kernel) to a 
file for diagnostics.  Currently, these are begin written to a non-temporary 
flash location (so not in /var/log).

Recently, we implemented additional power savings modes, including putting the 
processor into sleep more aggressively.  However, we *think* (I can't confirm 
this yet) that syslogd may be dropping some messages, maybe because we are going 
to sleep before all messages are flushed, not sure.

Could somebody please help me understand the internals of syslogd?  Is there any 
way that syslog messages might get dropped in the above scenario?  If so, any 
suggestions to alternative ways to gather this data?

TIA
RP