Difference between revisions of "Systemd FAQ"

From ArchWiki
Jump to: navigation, search
(Created page with "== FAQ == For an up-to-date list of known issues, look at the upstream [http://cgit.freedesktop.org/systemd/systemd/tree/TODO TODO]. {{FAQ |question=Why do I get log message...")
 
m (Be more clear about changing the allocated number of auto-spawning gettys)
(12 intermediate revisions by 8 users not shown)
Line 1: Line 1:
 +
{{Lowercase title}}
 +
[[Category:Daemons and system services]]
 +
[[Category:Boot process]]
 +
[[es:Systemd FAQ]]
 +
[[it:Systemd FAQ]]
 +
[[zh-CN:Systemd FAQ]]
 
== FAQ ==
 
== FAQ ==
  
Line 12: Line 18:
  
 
  # ln -sf /usr/lib/systemd/system/getty@.service /etc/systemd/system/getty.target.wants/getty@tty9.service
 
  # ln -sf /usr/lib/systemd/system/getty@.service /etc/systemd/system/getty.target.wants/getty@tty9.service
# systemctl daemon-reload
 
 
  # systemctl start getty@tty9.service
 
  # systemctl start getty@tty9.service
  
 
To remove a getty, simply remove the getty symlinks you want to get rid of in the {{ic|/etc/systemd/system/getty.target.wants/}} directory:
 
To remove a getty, simply remove the getty symlinks you want to get rid of in the {{ic|/etc/systemd/system/getty.target.wants/}} directory:
  
  # rm /etc/systemd/system/getty.target.wants/getty@tty5.service /etc/systemd/system/getty.target.wants/getty@tty6.service
+
  # rm /etc/systemd/system/getty.target.wants/getty@{tty5,tty6}.service
# systemctl daemon-reload
+
 
  # systemctl stop getty@tty5.service getty@tty6.service
 
  # systemctl stop getty@tty5.service getty@tty6.service
  
Users may also change the number of gettys by editing {{ic|/etc/systemd/logind.conf}} and changing the value of {{ic|NAutoVTs}}. By doing it this way, the on-demand spawning will be preserved, whereas the above method will simply have the gettys running from boot.
 
 
systemd does not use the {{ic|/etc/inittab}} file.
 
systemd does not use the {{ic|/etc/inittab}} file.
  
{{Note|As of systemd 30, only one getty will be launched by default. If you switch to another tty, a getty will be launched there (socket-activation style). You can still force additional agetty processes to start using the above methods.}}}}
+
{{Note|As of systemd 30, only one getty will be launched by default. If you switch to another tty, a getty will be launched there (socket-activation style). You can still force additional agetty processes to start using the above methods.}}
 +
 
 +
Users may also change the number of gettys that may be auto-spawned by editing {{ic|/etc/systemd/logind.conf}} and changing the value of {{ic|NAutoVTs}}. By doing it this way, the on-demand spawning will be preserved, whereas the above method will simply have the gettys running from boot.}}
  
 
{{FAQ
 
{{FAQ
Line 34: Line 39:
 
{{FAQ
 
{{FAQ
 
|question=How do I avoid clearing the console after boot?
 
|question=How do I avoid clearing the console after boot?
|answer=Create a custom {{ic|getty@tty1.service}} file by copying {{ic|/usr/lib/systemd/system/getty@.service}} to {{ic|/etc/systemd/system/getty.target.wants/getty@tty1.service}} and change {{ic|TTYVTDisallocate}} to {{ic|no}}.}}
+
|answer=Create a custom {{ic|getty@tty1.service}} file by copying {{ic|/usr/lib/systemd/system/getty@.service}} to {{ic|/etc/systemd/system/getty@tty1.service}} and change {{ic|TTYVTDisallocate}} to {{ic|no}}.}}
  
 
{{FAQ
 
{{FAQ
Line 42: Line 47:
 
This is a partial list of required/recommended options, there might be more:
 
This is a partial list of required/recommended options, there might be more:
  
 +
{{bc|1='''General setup'''
 +
CONFIG_FHANDLE=y
 
  CONFIG_AUDIT=y (recommended)
 
  CONFIG_AUDIT=y (recommended)
  CONFIG_AUDIT_LOGINUID_IMMUTABLE=y (not required, may break sysvinit compat)
+
  CONFIG_AUDIT_LOGINUID_IMMUTABLE=y (not required, may break sysvinit compatibility)
 
  CONFIG_CGROUPS=y
 
  CONFIG_CGROUPS=y
 +
'''-> Namespaces support'''
 +
    CONFIG_NET_NS=y (for private network)
 +
'''Networking support -> Networking options'''
 
  CONFIG_IPV6=[y<nowiki>|</nowiki>m] (highly recommended)
 
  CONFIG_IPV6=[y<nowiki>|</nowiki>m] (highly recommended)
  CONFIG_UEVENT_HELPER_PATH=""
+
'''Device Drivers'''
CONFIG_DEVTMPFS=y
+
  '''-> Generic Driver Options'''
CONFIG_DEVTMPFS_MOUNT=y (required if you don't use an initramfs)
+
    CONFIG_UEVENT_HELPER_PATH=""
  CONFIG_RTC_DRV_CMOS=y (highly recommended)
+
    CONFIG_DEVTMPFS=y
 +
    CONFIG_DEVTMPFS_MOUNT=y (required if you don't use an initramfs)
 +
  '''-> Real Time Clock'''
 +
    CONFIG_RTC_DRV_CMOS=y (highly recommended)
 +
'''File systems'''
 
  CONFIG_FANOTIFY=y (required for readahead)
 
  CONFIG_FANOTIFY=y (required for readahead)
 
  CONFIG_AUTOFS4_FS=[y<nowiki>|</nowiki>m]
 
  CONFIG_AUTOFS4_FS=[y<nowiki>|</nowiki>m]
  CONFIG_TMPFS_POSIX_ACL=y (recommended, if you want to use pam_systemd.so)
+
  '''-> Pseudo filesystems'''
CONFIG_NAMESPACES=y (for Private*=yes)
+
    CONFIG_TMPFS_POSIX_ACL=y (recommended, if you want to use pam_systemd.so)}}}}
CONFIG_NET_NS=y (for PrivateNetwork=yes)
+
CONFIG_FHANDLE=y}}
+
  
 
{{FAQ
 
{{FAQ
Line 67: Line 79:
  
 
{{FAQ
 
{{FAQ
|question=My computer shuts down, but the power stays on.
+
|question=My computer shuts down, but the power stays on
 
|answer=Use:
 
|answer=Use:
  
Line 97: Line 109:
 
  # systemctl enable ''myscript''.service
 
  # systemctl enable ''myscript''.service
  
This example assumes you want your script to start up when the target multi-user is launched.
+
This example assumes you want your script to start up when the target multi-user is launched. Also do chmod 755 to your script to enable execute permissions if you haven't done so already.
  
  
Line 121: Line 133:
 
|answer=This happens when using {{ic|systemctl enable}} and the symlink it tries to create in {{ic|/etc/systemd/system/}} already exists. Typically this happens when switching from one display manager to another one (for instance GDM to KDM, which can be enabled with {{ic|gdm.service}} and {{ic|kdm.service}}, respectively) and the corresponding symlink {{ic|/etc/systemd/system/display-manager.service}} already exists.
 
|answer=This happens when using {{ic|systemctl enable}} and the symlink it tries to create in {{ic|/etc/systemd/system/}} already exists. Typically this happens when switching from one display manager to another one (for instance GDM to KDM, which can be enabled with {{ic|gdm.service}} and {{ic|kdm.service}}, respectively) and the corresponding symlink {{ic|/etc/systemd/system/display-manager.service}} already exists.
  
To solve this problem, use {{ic|systemctl -f enable}} to overwrite an existing symlink.}}
+
To solve this problem, either first disable the relevent display manager before enabling the new one, or use {{ic|systemctl -f enable}} to overwrite an existing symlink.}}

Revision as of 21:27, 1 June 2013

FAQ

For an up-to-date list of known issues, look at the upstream TODO.

Template:FAQ

Template:FAQ

Template:FAQ

Template:FAQ

Template:FAQ

Template:FAQ

Template:FAQ

Template:FAQ

Template:FAQ

Template:FAQ

Template:FAQ