- Timestamp:
- 01/21/2024 07:32:55 AM (5 months ago)
- Branches:
- 12.1, ken/TL2024, lazarus, plabs/newcss, rahul/power-profiles-daemon, trunk, xry111/llvm18
- Children:
- 6fa3e04
- Parents:
- 0b50bdd1
- git-author:
- Xi Ruoyao <xry111@…> (01/20/2024 12:59:51 AM)
- git-committer:
- Xi Ruoyao <xry111@…> (01/21/2024 07:32:55 AM)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
general/sysutils/systemd.xml
r0b50bdd1 r0daaeef2 362 362 EOF</userinput></screen> 363 363 364 <!-- For some unknown reason if I don't do this, the per-user systemd 365 manager fails to start with "Trying to run as user instance, 366 but $XDG_RUNTIME_DIR is not set." This command is enough to 367 fix the issue, and it also seems logical to start using the newly 368 rebuilt systemd right away (like "exec bash -‐login" in LFS), 369 so just add it. --> 370 <para> 371 As the &root; user, replace the running <command>systemd</command> 372 manager (the <command>init</command> process) with the 373 <command>systemd</command> executable newly built and installed: 374 </para> 375 376 <screen role='root'><userinput>systemctl daemon-reexec</userinput></screen> 377 378 <important> 379 <para> 380 Now ensure <xref linkend='shadow'/> has been already rebuilt with 381 <xref linkend='linux-pam'/> support first, then logout, and login 382 again. This ensures the running login session registered with 383 <command>systemd-logind</command> and a per-user systemd instance 384 running for each user owning a login session. Many BLFS packages 385 listing Systemd as a dependency needs the 386 <command>systemd-logind</command> integration and/or a running 387 per-user systemd instance. 388 </para> 389 </important> 390 364 391 <warning> 365 392 <para>
Note:
See TracChangeset
for help on using the changeset viewer.