On 10/5/05, <b class="gmail_sendername">Roberto Nibali</b> &lt;<a href="mailto:ratz@drugphish.ch">ratz@drugphish.ch</a>&gt; wrote:<br>
<div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">&gt; You mean the process ID embedded (sometimes) in the program name (when<br>&gt; that field is present)?
<br><br>It's part of the identification when you use the LOG_PID option in<br>openlog(). It's not a required option but nevertheless a proper formated<br>syslog message should contain it.</blockquote><div><br>
That's what I meant, it's not always there, but when the program name
field is there, often the PID is embedded there as well. Sorry, thought
that was clear.<br>
</div><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">What is a good reason to have this? If you specify $MSG you will get the<br>programme name and pid logged, provided it was specified in openlog().
</blockquote><div><br>
Same reason for having the date, or the program name,&nbsp; or any
other part of the message available as a macro - so you can format it
yourself. <br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Is that not what you guys were looking for?</blockquote><div><br>
No, having a $PID macro is what we're looking for.<br>
</div><br></div>