<br><font size=2 face="sans-serif">> this tusc trace basically proves
that syslog-ng is NOT in pad_size mode,</font>
<br><font size=2 face="sans-serif">> if it were it would issue exactly
2048 byte sized reads whereas it does</font>
<br><font size=2 face="sans-serif">> about 8k reads (probably your log_msg_size
is set to 8192), the default.</font>
<br>
<br><font size=2 face="sans-serif">> So for some reason it doesn't process
the pad_size() argument.</font>
<br>
<br><font size=2 face="sans-serif">Well, I have tried to put debugging
statements in suitable places in </font>
<br><font size=2 face="sans-serif">the code, but I've learnt nothing about
why it is not being set.</font>
<br>
<br><font size=2 face="sans-serif">Should I be looking at the logproto->padding-size
or the logreader-></font>
<br><font size=2 face="sans-serif">options->padding option? Do
they refer to different things?</font>
<br>
<br><font size=2 face="sans-serif">Ideally I'd like to print it out at
the configuration parsing step,</font>
<br><font size=2 face="sans-serif">but I can make neither head nor tail
of all the bison/yacc/flex </font>
<br><font size=2 face="sans-serif">stuff that it uses, and can't figure
out where to put any debugging</font>
<br><font size=2 face="sans-serif">statements or breakpoints to determine
what's going on.</font>
<br>
<br><font size=2 face="sans-serif">If you could please post a known good
configuration file for HP-UX it</font>
<br><font size=2 face="sans-serif">would help me eliminate anything funny
in the one I'm using, which looks</font>
<br><font size=2 face="sans-serif">fine to the naked eye...</font>
<br>
<br><font size=2 face="sans-serif">Regards,</font>
<br>
<br><font size=2 face="sans-serif">Scott<br>
<br>
<br>
<br>
</font>