<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#ffffff">
    Lennart,<br>
    &nbsp;&nbsp;&nbsp; I think I found another clue. I noticed that the directory
    /var/log/journal was being used in addition to /var/run/log/journal.
    I do not want persistent logging, so I removed /var/log/journal.
    When I did this, systemd-journalctl appeared to work correctly.<br>
    &nbsp;&nbsp;&nbsp; Obviously I am mis-understanding (and mis-using) the journaling
    features of systemd. Could you please point me to any overview of
    where and how the journaling&nbsp; sub-system stores its data?<br>
    <br>
    Best regards,<br>
    <br>
    Dave.<br>
    <br>
    <br>
    On 03/29/2012 03:42 PM, David Lambert wrote:
    <blockquote cite="mid:4F74C94F.5020408@lambsys.com" type="cite">Thanks
      Lennart, it looks like your guess was spot on! See attached trace.
      Any suggestions on how to narrow this down further?
      <br>
      <br>
      On 03/29/2012 09:38 AM, Lennart Poettering wrote:
      <br>
      <blockquote type="cite">
        <br>
        Hmm, my guess is that we might have too many mem maps open? Can
        you
        <br>
        check strace? Anything suspicious there?
        <br>
        <br>
        Lennart
        <br>
        <br>
      </blockquote>
      <br>
      <pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
systemd-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:systemd-devel@lists.freedesktop.org">systemd-devel@lists.freedesktop.org</a>
<a class="moz-txt-link-freetext" href="http://lists.freedesktop.org/mailman/listinfo/systemd-devel">http://lists.freedesktop.org/mailman/listinfo/systemd-devel</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>