On 9/16/19 7:14 AM, Paul Menzel wrote:
In his talk*Linux kernel fastboot on the way* at this years Linux
Plumbers Conference [1][2], Feng Tang (CCed) has the notes below on
the slide for userspace/systemd.
• Systemd is ~1.5MB - the loading time for emmc is 100ms> • Can we use a small
lightwe
Hi folks,
It's been a while since systemd-bootchart moved to it's own git tree, so
it was a good time to get some changes out. I've tagged and released
v231 (systemd-bootchart will continue to independently number releases
incrementally), Here is a short summary of the changes:
* Switch on
On 01/04/2017 11:57 PM, Eswaran Vinothkumar (BEG-PT/PJ-IOT1) wrote:
> Hello systemd developers,
>
> I am currently analyzing the boot time of an embedded product. Systemd is
> used as the init system. I am trying to get the details about CPU load and
> I/O utilization from the systemd-bootchart.
On 04/11/2017 06:08 AM, Lennart Poettering wrote:
> On Tue, 11.04.17 13:41, Samuel Williams (space.ship.travel...@gmail.com)
> wrote:
>> - If a daemon fails to start up, trying to kill it.. may not be the
>> best option. It's probably a matter of the systemctl service file
>> detecting that a roll
On 04/13/2017 02:48 AM, Lennart Poettering wrote:
> On Wed, 12.04.17 21:09, Michael Biebl (mbi...@gmail.com) wrote:
>
>> 2017-04-12 20:24 GMT+02:00 Tomasz Torcz :
>>> On Wed, Apr 12, 2017 at 11:01:04AM -0700, Auke Kok wrote:
>>>> The right (or, better) solution I
On 07/10/2017 08:23 PM, Ian Pilcher wrote:
> I'm playing using systemd-networkd (rather than the legacy network
> service) on my Banana Pi CentOS 7 firewall. (See the "Bouncing
> interface once chrony is synced" thread for background.)
>
> I have "DHCP=yes" in the [Network] section of my WAN inte
On 09/25/2017 10:45 PM, Daniel Wang wrote:
> I have a number of timers that all look something like the following:
> The boilerplate for such small things is killing me. Is there a good
> technique to replace them with something simpler?
> Maybe transient timers? What will be the drawbacks of t
On 07/18/2018 03:26 PM, Juanjo Presa wrote:
> I wonder which ways are to run last systemd versions? nowadays Im
> running Centos 7 with systemd facebook backports
> (https://github.com/facebookincubator/rpm-backports). But maybe you guys
> have another way, NixOs? Archlinux?
You could always check
On Mon, May 16, 2016 at 04:24:25AM +0200, Michael Biebl wrote:
> 1,5M usr/bin/systemd-analyze
>
> What's up with systemd-analyze?
It shouldn't be part of a base package, it's not even a diagnostic tool, more
like a performance measurement type of thing.
I don't think size is of a concern for it.
Once system itself is running in a security domain for SMACK,
it will fail to start countless tasks due to missing privileges
for mounted and created directory structures. For /run and shm
specifically, we grant all tasks access.
---
src/core/mount-setup.c | 8
1 file changed, 8 insertion
Allows the systemd --system process to change its current
SMACK label to a predefined custom label (usually "system")
at boot time.
This is needed to have a few system-generated folders and
sockets automatically be created with the right SMACK
label. Without that, processes either cannot communica
Once systemd itself is running in a security domain for SMACK,
it will fail to start countless tasks due to missing privileges
for mounted and created directory structures. For /run and shm
specifically, we grant all tasks access.
These 2 mounts are allowed to fail, which will happen if the
system
Allows the systemd --system process to change its current
SMACK label to a predefined custom label (usually "system")
at boot time.
This is needed to have a few system-generated folders and
sockets automatically be created with the right SMACK
label. Without that, processes either cannot communica
n a kernel that does not have SMACK enabled either,
so there is no need to #ifdef any of this code out.
For more information about SMACK, please see Documentation/Smack.txt
in the kernel source code.
Signed-off-by: Auke Kok
---
man/systemd.socket.xml| 29
n a kernel that does not have SMACK enabled either,
so there is no need to #ifdef any of this code out.
For more information about SMACK, please see Documentation/Smack.txt
in the kernel source code.
Signed-off-by: Auke Kok
---
man/systemd.socket.xml| 29
ernel that does not have SMACK enabled either, so there is no need
to #ifdef any of this code out.
For more information about SMACK, please see Documentation/Smack.txt
in the kernel source code.
v3 of this patch changes the config options to be CamelCased.
Signed-off-by: Auke Kok
Cc: ca
---
src/bootchart/bootchart.c | 5 ++---
src/bootchart/log.c | 10 --
2 files changed, 6 insertions(+), 9 deletions(-)
diff --git a/src/bootchart/bootchart.c b/src/bootchart/bootchart.c
index 7bcfd98..37d8fbe 100644
--- a/src/bootchart/bootchart.c
+++ b/src/bootchart/bootchart.c
@@
---
src/bootchart/log.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/src/bootchart/log.c b/src/bootchart/log.c
index c697121..ff70e2d 100644
--- a/src/bootchart/log.c
+++ b/src/bootchart/log.c
@@ -39,11 +39,11 @@ DIR *proc;
double gettime_ns(void)
{
-struct
---
src/bootchart/bootchart.c | 21 +++--
src/bootchart/log.c | 5 +++--
2 files changed, 14 insertions(+), 12 deletions(-)
diff --git a/src/bootchart/bootchart.c b/src/bootchart/bootchart.c
index 3d77bab..7bcfd98 100644
--- a/src/bootchart/bootchart.c
+++ b/src/bootchart/b
Contrary to it's own packaging guidelines, these symlinks are created
in /etc/. While technically not a problem, this makes it harder
for folks installing from git that want to override these settings
(either masking or otherwise).
Moving the links to $(systemunitdir) resolves.
---
Makefile.am |
Without this patch, I'm seeing cgroup paths for user sessions with
both the user name, and the uid created, which can't be intended.
Spotted through user-session-units use.
---
src/login/logind-user.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/login/logind-user.c b/sr
Readahead has all sorts of bad side effects depending on your
storage media. On rotating disks, it may be degrading startup
performance if enough requests are queued spanning linearly
over all blocks early at boot, and mount, blkid and friends
want to insert reads to the start of these block device
Cc: chengwei.y...@intel.com
Cc: lenn...@poettering.net
---
src/core/manager.c | 11 ---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/src/core/manager.c b/src/core/manager.c
index f16621a..592f332 100644
--- a/src/core/manager.c
+++ b/src/core/manager.c
@@ -509,9 +509,14 @@
The PAM helper thread needs to capture the death signal from the
parent, but is prohibited from doing so since when the child dies
as normal user, the kernel won't allow it to send a TERM to the
PAM helper thread which is running as root.
This causes the PAM threads to never exit, accumulating aft
is code is not new - it's partially taken from sreadahead (formerly
maintained by Arjan van der Ven and me, and was originally written
by me), and adapted with the right bits to parse the systemd
readahead pack files, which are slightly different in format.
Signed-off-by: Auke Kok
-
VERSION used in all the code
to provide a quick way to assure all these programs are always
synchronized. v3 fixes the integer math.
Signed-off-by: Auke Kok
---
Makefile.am | 10 ++-
src/readahead/readahead-analyze.c | 141 +
src/read
The MeeGo distribution is still a supported distribution, but
will probably not see an updated version of systemd anymore.
Most of the development is focussing on Tizen now, and the
generic support for building --with-distro=other is more than
adequate enough.
This patch removes the support as a
These printf specifiers allow us to refer to $HOME and $USER
in unit files. These are particularly helpful in instanced
units that have "User=" set, and in systemd --user domains.
The specifiers will return the pw_name and pw_dir fields
if the unit file has a User= field.
If the unit file does no
Change the default WorkingDirectory to $HOME in case running as
USER_MANAGER. We assume that HOME is set by default for all
user managers, so looking up pw_dir doesn't make much sense.
Mount, socket and service units are affected, as these all
can execute programs and thus the working directory ma
Become the reaper for all children part of the user session.
Tested with several forking services.
Keep a local #define for the prctl value around because not many
will have updated kernel-headers for a while - Add TODO entry
to mark a good point in time to remove it.
---
TODO| 2 ++
Add specifier expansion to Path and String conditions.
Specifier expansion for conditions will help create instance
and user session units by allowing us to template conditions
based on the instance or user session parameters.
An example would be a system-wide user session service file
that condi
31 matches
Mail list logo
