Difference between revisions of "Systemd FAQ"

From ArchWiki
Jump to: navigation, search
(There we go.)
m (Just made sure people do chmod +ax to their scripts before flooding the forums "OMGZZZ 1T DOENT WOKRS" posts)
(4 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 +
{{Lowercase title}}
 
[[Category:Daemons and system services]]
 
[[Category:Daemons and system services]]
 
[[Category:Boot process]]
 
[[Category:Boot process]]
 +
[[es:Systemd FAQ]]
 +
[[it:Systemd FAQ]]
 
[[zh-CN:Systemd FAQ]]
 
[[zh-CN:Systemd FAQ]]
 
== FAQ ==
 
== FAQ ==
Line 75: Line 78:
  
 
{{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 105: Line 108:
 
  # 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 129: Line 132:
 
|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 16:41, 1 February 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