/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
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
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
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
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
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
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 +
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.or
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
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
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
-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
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
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
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
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
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
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.co
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 incorrec
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
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 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
. 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
notic
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
24 matches
Mail list logo
