You are not logged in.
I'm creating an ISO by using Archiso tool and I see that the process taking more time during the first boot is the "Rebuild Dynamic Linker Cache" and its start job reaches several minutes (around 10 min). It should be used to create "/etc/ld.so.cache".
Is there a way to prevent the start of this job on a created Arch ISO?
Last edited by D3vil0p3r (2023-09-18 19:08:36)
Offline
That is the /usr/lib/systemd/system/ldconfig.service running .
# SPDX-License-Identifier: LGPL-2.1-or-later
#
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
[Unit]
Description=Rebuild Dynamic Linker Cache
Documentation=man:ldconfig(8)
ConditionNeedsUpdate=|/etc
ConditionFileNotEmpty=|!/etc/ld.so.cache
DefaultDependencies=no
After=local-fs.target
Before=sysinit.target systemd-update-done.service
Conflicts=shutdown.target initrd-switch-root.target
Before=shutdown.target initrd-switch-root.target
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/sbin/ldconfig -X
Maybe add a copy of your local /etc/ld.so.cache to the iso ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
I was thinking to add a copy of my /etc/ld.so.cache but, in case I rebuild the ISO by Archiso in order to get the same ISO with the most updated packages, it means that I need to replace ld.so.cache manually with the new one related to this just created updated ISO?
Offline
See ldconfig.8 the -r option. You could also chroot in then generate it. You could also try masking ldconfig.service and see how the performance compares.
Your related thread https://bbs.archlinux.org/viewtopic.php?id=288497
Offline