On So, 10.09.23 11:45, CARLOS VILLANUEVA Y SIMON ([email protected]) wrote:
> Hello all,
>
> Recently, while updating a code that was using libudev to a more modern
> API, sd-device, I could not find some of the functions that are defined at
> sd-device.h (
> https://github.com/systemd/systemd/bl
Hello all,
Recently, while updating a code that was using libudev to a more modern
API, sd-device, I could not find some of the functions that are defined at
sd-device.h (
https://github.com/systemd/systemd/blob/main/src/systemd/sd-device.h) at
the man pages (
https://www.freedesktop.org/software/
On 03/03/2012 11:29 AM, David Lambert wrote:
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, th
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@argus
On Wed, 29.02.12 06:00, David Lambert ([email protected]) wrote:
>
> 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 sinc
On Tue, 28.02.12 14:51, David Lambert ([email protected]) 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 OO
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?
Than
On Tue, 2012-02-28 at 21:19 -0600, David Lambert wrote:
> 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, a
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 th
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
10 matches
Mail list logo
