[systemd-devel] My last post went as unprocessed
My last post went as unprocessed. I checked my membership and it is current ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] My last post went as unprocessed
OK this post went through, so I am replying with the original text that was unprocessed: On my Angstrom distribution the sshd service is controlled by the file /lib/systemd/system/sshd@.service. What is the significance of the @ in the service name? This may be buried in documentation, but is very difficult to search for. My apologies if it is obvious. Best regards, Dave. Sorry for any confusion, but I am confused ;) On 13-07-11 02:46 PM, David Lambert wrote: My last post went as unprocessed. I checked my membership and it is current ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] My last post went as unprocessed
Thanks for your quick reply. I also notice a - preceding the target for ExecStart target. How does this work and where is it documented. Again very difficult to search :-[ Dave. [Unit] Description=OpenSSH Per-Connection Daemon After=sshdgenkeys.service [Service] ExecStart=-/usr/sbin/sshd -i ExecReload=/bin/kill -HUP $MAINPID StandardInput=socket StandardError=syslog On 13-07-11 03:08 PM, Zbigniew Jędrzejewski-Szmek wrote: On Thu, Jul 11, 2013 at 02:58:26PM -0500, David Lambert wrote: On my Angstrom distribution the sshd service is controlled by the file /lib/systemd/system/sshd@.service. What is the significance of the @ in the service name? @ means that it's a template unit. A separate instance of the sshd@.service unit will be created for each connections, called sshd@connection-1-details.service, sshd@connection-2-details.service, etc. Zbyszek This may be buried in documentation, but is very difficult to search for. My apologies if it is obvious. It's described in systemd.unit(5), but not very verbosely. Zbyszek ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Feature wish - auto-complete
As I am lazy I would love to see the auto-complete feature implemented in systemd CLI. Dave. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Feature wish - auto-complete
On 13-06-18 08:58 AM, killermoehre wrote: Am 18.06.2013 15:44, schrieb David Lambert: As I am lazy I would love to see the auto-complete feature implemented in systemd CLI. Dave. Hi Dave, Well, I have autocompletion for systemctl, journalctl, loginctl, *ctl, etc. Are you sure bash-completion is installed and enabled? Regards I can auto complete the primary commands such as systemctl, etc. However, I would do not see auto completing further in the command line, such as: systemctl status partofmyservicenametab etc. I am running systemd on Angstrom: systemctl --version systemd 196 angstrom +PAM -LIBWRAP -AUDIT -SELINUX +IMA +SYSVINIT -LIBCRYPTSETUP +GCRYPT +ACL +XZ Dave. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] journald.conf vs systemd.journald.conf
Thanks Lennart. That makes a lot of sense. Unfortunately MaxLevelStore etc. does not appear to work on my system, although ImportKernel=no does. My journald.conf is attached, and my version of systemd is: root@argus-base:~# systemctl --version systemd 44 angstrom +PAM +LIBWRAP -AUDIT -SELINUX +IMA +SYSVINIT -LIBCRYPTSETUP Any ideas? Is this a version issue? TIA, Dave. root@argus-base:~# On 10/02/2012 08:23 AM, Lennart Poettering wrote: On Tue, 02.10.12 09:55, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote: I find that being able to turn off kernel chatter using ImportKernel=no, was a very useful feature especially on embedded systems with limited resources (and buggy kernel drivers ;-) ) Yeah, doesn't seem to be possible ATM. In general we really want only those configurations that are really necessary and the primary solution for a specific usecase. That's why we dropped ImportKernel=. If you want to lower the amount of chatter you get then I'd recommend using stuff like MaxLevelStore= to simply store less data on disk. Lennart # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU General Public License as published by # the Free Software Foundation; either version 2 of the License, or # (at your option) any later version. # # See system-journald.conf(5) for details [Journal] Storage=volatile #Compress=yes #RateLimitInterval=10s #RateLimitBurst=200 #SystemMaxUse= #SystemKeepFree= #SystemMaxFileSize= #SystemMinFileSize= RuntimeMaxUse=1M #RuntimeKeepFree= #RuntimeMaxFileSize= #RuntimeMinFileSize= ForwardToSyslog=no #ForwardToKMsg=no #ForwardToConsole=no ImportKernel=no MaxLevelKMsg=4 MaxLevelConsole=4 MaxLevelStore=4 MaxLevelSyslog=4 ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] journald.conf vs systemd.journald.conf
Looks like it is a version issue, so no bug report. While on the subject; is systemd tolerant to deprecated options, or will it fail? If tolerant, I can make a config file common to all versions, if not, is there a way of conditionalizing within the config file? Best, Dave. On 10/02/2012 10:45 AM, Lennart Poettering wrote: On Tue, 02.10.12 10:33, David Lambert (d...@lambsys.com) wrote: Thanks Lennart. That makes a lot of sense. Unfortunately MaxLevelStore etc. does not appear to work on my system, although ImportKernel=no does. My journald.conf is attached, and my version of systemd is: root@argus-base:~# systemctl --version systemd 44 angstrom +PAM +LIBWRAP -AUDIT -SELINUX +IMA +SYSVINIT -LIBCRYPTSETUP Any ideas? Is this a version issue? Might be. Please try a newer systemd version. If it doesn't work there, please file a bug. Thanks! Lennart ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] journald.conf vs systemd.journald.conf
I just noticed that it that journald.conf seems to have replaced systemd.journald.conf; am I correct? Also, looking at the man page for journald.conf it seems that some keywords such as ImportKernel have been removed or moved elsewhere? My documentation resource is http://www.freedesktop.org/software/systemd/man/. Is this correct? If not please point me in the right direction. I find that being able to turn off kernel chatter using ImportKernel=no, was a very useful feature especially on embedded systems with limited resources (and buggy kernel drivers ;-) ) Best regards, Dave. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] System power control
I am developing a battery backed up cape for a Beaglebone project which
uses systemd under Angstrom. In order to conserve battery life, I would
like to signal my battery control hardware via a GPIO when system
shutdown is complete and all file systems have been dismounted. Is there
a hook in systemd which will allow me to call a small user helper
program at this point. Looking at the shutdown.c source, I see the
following code:
if (access(/run/initramfs/shutdown, X_OK) == 0) {
if (prepare_new_root() = 0
pivot_to_new_root() = 0) {
execv(/shutdown, argv);
log_error(Failed to execute shutdown binary: %m);
}
}
Is the intention of this code to provide such a hook? Can I cheat by
creating /run/initramfs/ just prior to shutdown and copy a small
shutdown executable of my own here. This sounds like it may work, but
seems like a terrible hack. I feel that there should be a more elegant
way to achieve this goal.
Thanks for any advice.
Dave.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] System power control
On 08/12/2012 06:09 PM, Lennart Poettering wrote:
On Sun, 12.08.12 17:55, David Lambert (d...@lambsys.com) wrote:
I am developing a battery backed up cape for a Beaglebone project
which uses systemd under Angstrom. In order to conserve battery
life, I would like to signal my battery control hardware via a GPIO
when system shutdown is complete and all file systems have been
dismounted. Is there a hook in systemd which will allow me to call
a small user helper program at this point. Looking at the shutdown.c
source, I see the following code:
if (access(/run/initramfs/shutdown, X_OK) == 0) {
if (prepare_new_root() = 0
pivot_to_new_root() = 0) {
execv(/shutdown, argv);
log_error(Failed to execute shutdown binary: %m);
}
}
Is the intention of this code to provide such a hook? Can I cheat by
creating /run/initramfs/ just prior to shutdown and copy a small
shutdown executable of my own here. This sounds like it may work,
but seems like a terrible hack. I feel that there should be a more
elegant way to achieve this goal.
No, that's for the initrd to undo the storage setup it did at boot.
If you look a tiny bit above the code you quoted you will find the right
way to do this: right before shutdown we execute all executables from
/usr/lib/systemd/system-shutdown/. Just drop int your stuff thre, mark
it executable, and you are done.
This is documented in systemd-halt.service(8) in more detail.
Note that using this for powering down things is a racy and unsafe
though. Some things maintained by the kernel are only synced to disk
when the actual kernel system call reboot(2) is invoked. That means that
you should be careful only to shut off power after that system call has
been entered and finished this syncing bit. Effectively this means that
you need to do your power down logic in the kernel, as this cannot be
done safely and race-freely from usersapce.
Hope this is helpful.
Lennart
Thanks again Lennart. One thing that got me confused is that on my
system (Angstrom) the /usr/lib/systemd/... has been replaced by
/lib/systemd/... :-(
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd-journalctl Failed to iterate through journal: Cannot allocate memory
Lennart, Thanks for your timely and informative replies. All is much clearer now that I have found the documentation :-[ Dave. On 04/02/2012 09:49 AM, Lennart Poettering wrote: On Fri, 30.03.12 11:55, David Lambert (d...@lambsys.com) wrote: Lennart, 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. 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 sub-system stores its data? /var/run is simply an alias for /run on modern systems. If you reduce the number of journal files you are unlikely to hit the address space limit, as described in the earlier mail. It's documented in systemd-journald.conf(5). Lennart ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd-journalctl Failed to iterate through journal: Cannot allocate memory
Lennart, 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. 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 sub-system stores its data? Best regards, Dave. On 03/29/2012 03:42 PM, David Lambert wrote: Thanks Lennart, it looks like your guess was spot on! See attached trace. Any suggestions on how to narrow this down further? On 03/29/2012 09:38 AM, Lennart Poettering wrote: Hmm, my guess is that we might have too many mem maps open? Can you check strace? Anything suspicious there? Lennart ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] systemd-journalctl Failed to iterate through journal: Cannot allocate memory
I am getting the message: Failed to iterate through journal: Cannot allocate memory when attempting to run systemd-journalctl. Although I am running an embedded system (Android on Beaglebone) I appear to have plenty of resources as witnessed by free and df: total used free sharedbuffers cached Mem:254024 145168 108856 0 29264 60876 -/+ buffers/cache: 55028 198996 Swap:0 0 0 Filesystem 1K-blocksUsed Available Use% Mounted on rootfs 7678396 1582904 5710336 22% / /dev/root7678396 1582904 5710336 22% / devtmpfs 126900 0126900 0% /dev tmpfs 127012 0127012 0% /dev/shm tmpfs 1270121576125436 2% /run tmpfs 127012 0127012 0% /sys/fs/cgroup tmpfs 1270121576125436 2% /var/run tmpfs 127012 0127012 0% /media tmpfs 1270121576125436 2% /var/lock tmpfs 127012 12127000 1% /tmp The output of status commands appears to be normal, and my /etc/systemd/systemd-journald.conf contains: # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU General Public License as published by # the Free Software Foundation; either version 2 of the License, or # (at your option) any later version. # # See system-journald.conf(5) for details [Journal] #Compress=yes #RateLimitInterval=10s #RateLimitBurst=200 #SystemMaxUse= #SystemKeepFree= #SystemMaxFileSize= #SystemMinFileSize= RuntimeMaxUse=1M #RuntimeKeepFree= #RuntimeMaxFileSize= #RuntimeMinFileSize= ForwardToSyslog=no #ForwardToKMsg=no ForwardToConsole=yes #ImportKernel=yes ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd-journal
Thanks Lennart. I was running v40. Upgrading to v44 seems to have fixed my issue. Dave. On 03/21/2012 09:18 PM, Lennart Poettering wrote: On Wed, 21.03.12 20:47, David Lambert (d...@lambsys.com) wrote: I am still having problems with being unable to control the growth the systemd journal log files, despite various attempts at imposing limits in systemd-journald.conf (attached). As I am running on an extremely resource limited embedded system, I would like to know if there is any other way to control or disable systemd-journal. [Journal] RuntimeMaxUse=1M This is the only option you should use (assuming you want volatile logging only), leave all others commented. If you want persistant logging use SystemMaxUse=1M instead and create the dir /var/log/journal. Also, you need v44 for this to work correctly. There's currently no way to turn off journald entirely, but it's on the TODO list. When that's done you can tell journald to output to kmsg (via systemd_journal.forward_to_kmsg=yes on the kernel cmdline) and turn both the volatile and the persistant journal files off. Lennart ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] systemd-journal
I am still having problems with being unable to control the growth the systemd journal log files, despite various attempts at imposing limits in systemd-journald.conf (attached). As I am running on an extremely resource limited embedded system, I would like to know if there is any other way to control or disable systemd-journal. Regards, Dave. # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU General Public License as published by # the Free Software Foundation; either version 2 of the License, or # (at your option) any later version. # # See system-journald.conf(5) for details [Journal] #Compress=yes #RateLimitInterval=10s #RateLimitBurst=200 SystemMaxUse=100K #SystemKeepFree= SystemMaxFileSize=200K #SystemMinFileSize= RuntimeMaxUse=1M #RuntimeKeepFree= RuntimeMaxFileSize=300K #RuntimeMinFileSize= ForwardToSyslog=no #ForwardToKMsg=no #ForwardToConsole=no #ImportKernel=yes ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd39: journald segfault brings down some user services
On 03/09/2012 02:46 AM, Koen Kooi wrote: I can confirm the large filesizes, even with xz compression enabled. What's the best way to debug this? regards, Koen I first noticed this with a service that was Python program I was developing. It was continually crashing and restarting itself, thus emitting stack dumps to the log. Adding limits to the systemd-journald.conf appeared to work at first, but once the limit had been reached the log file size first reduced to ~68k, then proceeded to ignore all limits. See my previous post for details. Dave. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] System journal file size problem
Please excuse this repost, but i think the context has changed. I originally posted this problem as a lack of understanding of the documentation for systemd-journald.conf. Now, however, I believe that it is a problem where at least some of the limits in systemd-journald.conf are being incorrectly handled, resulting in a runaway system.journal file. Regards, Dave. On 02/29/2012 07:26 AM, Lennart Poettering wrote: You can put limits on the log size however, for example via SystemMaxUse=64M or SystemKeepFree=500M or suchlike. Further experimentation seems to indicate that the first time a limit is reached, the system trims the log file back, BUT subsequently it appears to ignore all limits: root@argus2:~# du -s /run/log/journal/bd4dce8541064e29b00e90f7234b3287/system.journal -h 252K/run/log/journal/bd4dce8541064e29b00e90f7234b3287/system.journal root@argus2:~# du -s /run/log/journal/bd4dce8541064e29b00e90f7234b3287/system.journal -h 256K/run/log/journal/bd4dce8541064e29b00e90f7234b3287/system.journal root@argus2:~# du -s /run/log/journal/bd4dce8541064e29b00e90f7234b3287/system.journal -h 296K/run/log/journal/bd4dce8541064e29b00e90f7234b3287/system.journal root@argus2:~# du -s /run/log/journal/bd4dce8541064e29b00e90f7234b3287/system.journal -h 300K/run/log/journal/bd4dce8541064e29b00e90f7234b3287/system.journal root@argus2:~# du -s /run/log/journal/bd4dce8541064e29b00e90f7234b3287/system.journal -h 68K/run/log/journal/bd4dce8541064e29b00e90f7234b3287/system.journal journal file trimmed as expected root@argus2:~# du -s /run/log/journal/bd4dce8541064e29b00e90f7234b3287/system.journal -h 76K/run/log/journal/bd4dce8541064e29b00e90f7234b3287/system.journal root@argus2:~# du -s /run/log/journal/bd4dce8541064e29b00e90f7234b3287/system.journal -h 76K/run/log/journal/bd4dce8541064e29b00e90f7234b3287/system.journal root@argus2:~# du -s /run/log/journal/bd4dce8541064e29b00e90f7234b3287/system.journal -h 88K/run/log/journal/bd4dce8541064e29b00e90f7234b3287/system.journal root@argus2:~# du -s /run/log/journal/bd4dce8541064e29b00e90f7234b3287/system.journal -h 100K/run/log/journal/bd4dce8541064e29b00e90f7234b3287/system.journal root@argus2:~# du -s /run/log/journal/bd4dce8541064e29b00e90f7234b3287/system.journal -h 132K/run/log/journal/bd4dce8541064e29b00e90f7234b3287/system.journal root@argus2:~# du -s /run/log/journal/bd4dce8541064e29b00e90f7234b3287/system.journal -h 140K/run/log/journal/bd4dce8541064e29b00e90f7234b3287/system.journal root@argus2:~# du -s /run/log/journal/bd4dce8541064e29b00e90f7234b3287/system.journal -h 160K/run/log/journal/bd4dce8541064e29b00e90f7234b3287/system.journal root@argus2:~# du -s /run/log/journal/bd4dce8541064e29b00e90f7234b3287/system.journal -h 272K/run/log/journal/bd4dce8541064e29b00e90f7234b3287/system.journal root@argus2:~# du -s /run/log/journal/bd4dce8541064e29b00e90f7234b3287/system.journal -h 288K/run/log/journal/bd4dce8541064e29b00e90f7234b3287/system.journal root@argus2:~# du -s /run/log/journal/bd4dce8541064e29b00e90f7234b3287/system.journal -h 336K/run/log/journal/bd4dce8541064e29b00e90f7234b3287/system.journal root@argus2:~# du -s /run/log/journal/bd4dce8541064e29b00e90f7234b3287/system.journal -h 612K /run/log/journal/bd4dce8541064e29b00e90f7234b3287/system.journaljournal file continues to grow .. ... root@argus2:~# du -s /run/log/journal/bd4dce8541064e29b00e90f7234b3287/system.journal -h 1.3M /run/log/journal/bd4dce8541064e29b00e90f7234b3287/system.journaland grow until all memory is exhausted :( Configuration file is: root@argus2:~# cat /etc/systemd/systemd-journald.conf # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU General Public License as published by # the Free Software Foundation; either version 2 of the License, or # (at your option) any later version. # # See system-journald.conf(5) for details [Journal] #Compress=yes #RateLimitInterval=10s #RateLimitBurst=200 SystemMaxUse=100K #SystemKeepFree= SystemMaxFileSize=200K #SystemMinFileSize= RuntimeMaxUse=1M #RuntimeKeepFree= RuntimeMaxFileSize=300K #RuntimeMinFileSize= ForwardToSyslog=no #ForwardToKMsg=no #ForwardToConsole=no #ImportKernel=yes ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd39: journald segfault brings down some user services
On 03/08/2012 03:07 PM, Warpme wrote: I haven't set any limits in journal.conf - so maybe I should set them. Unfortunately there is no man for this file (or I miss something) - so I prefer to first understand it then next modify content.. Please see my earler post on guessing the journald.conf settings and large file sizes. Maybe we have a common problem here? Dave. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Documentation question
On 02/29/2012 07:26 AM, Lennart Poettering wrote: You can put limits on the log size however, for example via SystemMaxUse=64M or SystemKeepFree=500M or suchlike. I am still getting large logs even when I set SystemMaxUse=1M, as shown below. Do I also need to set SystemMaxFileSize? root@argus2:~# du -sh /run/log/journal/bd4dce8541064e29b00e90f7234b3287/system.journal 14M/run/log/journal/bd4dce8541064e29b00e90f7234b3287/system.journal root@argus2:~# cat /etc/systemd/systemd-journald.conf # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU General Public License as published by # the Free Software Foundation; either version 2 of the License, or # (at your option) any later version. # # See system-journald.conf(5) for details [Journal] #Compress=yes #RateLimitInterval=10s #RateLimitBurst=200 SystemMaxUse=1M #SystemKeepFree= #SystemMaxFileSize= #SystemMinFileSize= #RuntimeMaxUse= #RuntimeKeepFree= #RuntimeMaxFileSize= #RuntimeMinFileSize= ForwardToSyslog=no #ForwardToKMsg=no #ForwardToConsole=no #ImportKernel=yes ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Documentation question
On 02/28/2012 10:09 PM, Mathieu Bridon wrote: Do you have the folder /var/log/journal on your system? If it exists, systemd-journald will write logs there, otherwise it will write them to /run/journal And since /run is mounted as tmpfs, that could explain the memory usage you are seeing? Thanks Mathieu - that was the issue! Two more questions, however: 1) What is the preferred method for turning off logging, or at least redirecting it to /dev/null? I have an embedded system with very limited resources. 2) What is the best resource for systemd documentation? For example, I still have not found a man page for systemd-journald.conf Dave. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Documentation question
Please excuse if this is trivial, but I am a systemd newbie. I am running systemd on Angstrom/Beaglebone. After a couple of days I notice that the process systemd-journald had grown and was ultimately killed by the kernel's OOM handler. I investigated the systemd-journald.conf file which stated: # See system-journald.conf(5) for details I presume that this is a reference to a man page, but I have downloaded systemd-43 and cannot find this documentation. I would appreciate any links to this documentation and/or any suggestions as to where the problem nay lie. Best, Dave. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Documentation question
I have got a little further in diagnosing this memory leak of systemd-journal. It appears to worsen when I have a process that emits data to stdout. I presume that systemd-journal is attempting to put this somewhere but failing, and consequently is buffering it in its own process. Where is this logging supposed to go, and can I redirect it to somewhere benign such as /dev/null? Dave. On 02/28/2012 02:51 PM, David Lambert wrote: Please excuse if this is trivial, but I am a systemd newbie. I am running systemd on Angstrom/Beaglebone. After a couple of days I notice that the process systemd-journald had grown and was ultimately killed by the kernel's OOM handler. I investigated the systemd-journald.conf file which stated: # See system-journald.conf(5) for details I presume that this is a reference to a man page, but I have downloaded systemd-43 and cannot find this documentation. I would appreciate any links to this documentation and/or any suggestions as to where the problem nay lie. Best, Dave. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
