<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Mar 5, 2013, at 10:21 PM, Mirco Tischler <<a href="mailto:mt-ml@gmx.de">mt-ml@gmx.de</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">2013/3/5 Holger Winkelmann <span dir="ltr"><<a href="mailto:hw@travelping.com" target="_blank">hw@travelping.com</a>></span><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Hi David,<br> <div class="im"><br> On Mar 5, 2013, at 9:52 PM, David Strauss <<a href="mailto:david@davidstrauss.net">david@davidstrauss.net</a>> wrote:<br> <br> > On Mon, Mar 4, 2013 at 11:16 PM, Holger Winkelmann <<a href="mailto:hw@travelping.com">hw@travelping.com</a>> wrote:<br> >> Or is there a special journal socket to write to?<br> ><br> > Yes, and the Python module's use of the C library wraps all of that.<br> ><br> > Auke is also correct that you can write to stderr/stdout from a<br> > service running in systemd. That does not support structured logging,<br> > though.<br> <br> </div>Thats what I expected anyway, so for our logging purposes I would like to have structured<br> logging…<br> <br> So thanks for the Info, I'll wait for the Documentation of the raw format (or we check the C<br> implementation) for the time being we use the C-Lib.<br> <div class="im"><br> ><br> > --<br> > David Strauss<br> > | <a href="mailto:david@davidstrauss.net">david@davidstrauss.net</a><br> > | <a href="tel:%2B1%20512%20577%205827" value="+15125775827">+1 512 577 5827</a> [mobile]<br> <br> </div>--<br> Holger Winkelmann<br> Managing Director<br> <br></blockquote><div>Out of curiosity, what are your reasons to avoid the C library? And I personally don't ever expect the raw format to be documented - I see it as an implementation detail, not part of any kind of API</div></div></blockquote><div><br></div><div>Depends how you see an API, We have a messaging passing background (we are Erlang programmer here) and for us the message over the socket is seen as the API. and the C-lib wraps this for the C Language.</div><div><br></div><div>To use the C-API we need to write a NIF function for Erlang where the c part needs to be cross compiled for all different architectures. Writing the format native to the socket will avoid this.</div><div><br></div><div>Another example: Just recently we had a project partner being in Java-Land was not allowed by management to use any Native Library.</div><div><br></div><div>Holger</div><blockquote type="cite"><div class="gmail_quote"> <div><br></div><div>Mirco</div></div> </blockquote></div><br><div apple-content-edited="true"> <span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px; "><div>--</div><div>Holger Winkelmann</div></span> </div> <br></body></html>