Difference between revisions of "Autostarting"

From ArchWiki
Jump to: navigation, search
(Graphical)
(all shell-specific info merged to Bash and Zsh)
Line 12: Line 12:
 
''runit'' is a mature init system which offers process supervision, parallel startup, per-user service trees, granular cgroup manipulation, flexible dependency system, and boot times that don't incur the penalty of dbus. The root-level services are symlinks in {{ic|/service}} with the actual service directories in {{ic|/etc/sv}}. See the [[Runit]] page for more information.
 
''runit'' is a mature init system which offers process supervision, parallel startup, per-user service trees, granular cgroup manipulation, flexible dependency system, and boot times that don't incur the penalty of dbus. The root-level services are symlinks in {{ic|/service}} with the actual service directories in {{ic|/etc/sv}}. See the [[Runit]] page for more information.
  
== Shell: BASH ==
+
== Shells ==
  
To autostart programs in console or upon longin, you can use shell startup files/directories. Read the documentation for your shell, or its ArchWiki article, e.g. [[Bash]] or [[Zsh]]. Complete startup sequence for bash is explained in the "INVOCATION" section of [http://linux.die.net/man/1/bash "man 1 bash"]. When an interactive shell that is not a login shell is started, bash reads and executes commands from {{ic|~/.bashrc}}
+
To autostart programs in console or upon login, you can use shell startup files/directories. Read the documentation for your shell, or its ArchWiki article, e.g. [[Bash#Configuration file sourcing order at startup]] or [[Zsh#Autostarting applications]].
 +
 
 +
See also [[Wikipedia:Unix shell#Configuration files for shells]].
  
 
=== /etc/profile ===
 
=== /etc/profile ===
  
{{ic|/etc/profile}} is sourced by all Bourne-compatible shells upon login: it sets up an environment upon login and application-specific ({{ic|/etc/profile.d/*.sh}}) settings.
+
{{ic|/etc/profile}} is sourced by all Bourne-compatible shells upon login: it sets up an environment upon login and application-specific settings by sourcing any readable {{ic|/etc/profile.d/*.sh}} scripts.
 
+
Each time {{ic|/etc/profile}} is executed, it sources {{ic|/etc/profile.d/*.sh}} and {{ic|/etc/bash.bashrc}} if they are readable. After reading {{ic|/etc/profile}}, it looks for {{ic|~/.bash_profile}}, {{ic|~/.bash_login}}, and {{ic|~/.profile}}, in that order, and reads and executes commands from the first one that exists and is readable. When a login shell exits, bash reads and executes commands from the files {{ic|~/.bash_logout}} and {{ic|/etc/bash.bash_logout}}, if the files exists.
+
 
+
=== /etc/bash.bashrc ===
+
 
+
If not running interactively, it just returns. Or {{ic|/usr/share/bash-completion/bash_completion}} is sourced.
+
 
+
=== ~/.bash_profile ===
+
 
+
{{ic|~/.bashrc}} is sourced
+
 
+
== Other Shells ==
+
*{{ic|STARTUP/SHUTDOWN FILES}} section of {{ic|man zsh}}
+
*[[Wikipedia:Unix_shell#Configuration files for shells]]
+
  
 
== Graphical ==
 
== Graphical ==

Revision as of 08:20, 11 July 2013

This article links to various methods to launch scripts or applications automatically when some particular event is taking place, like system startup or shutdown, shell login or logout and so on.

Daemons

You can easily start your scripts or applications as daemons, see Daemon.

Systemd

systemd is the default init framework, replacing initscripts. The services which are started by systemd can be found in the subfolders of /etc/systemd/system/. Services can be enabled using the systemctl command. For more information about systemd and how to write autostart scripts for it, see at systemd.

Runit

runit is a mature init system which offers process supervision, parallel startup, per-user service trees, granular cgroup manipulation, flexible dependency system, and boot times that don't incur the penalty of dbus. The root-level services are symlinks in /service with the actual service directories in /etc/sv. See the Runit page for more information.

Shells

To autostart programs in console or upon login, you can use shell startup files/directories. Read the documentation for your shell, or its ArchWiki article, e.g. Bash#Configuration file sourcing order at startup or Zsh#Autostarting applications.

See also Wikipedia:Unix shell#Configuration files for shells.

/etc/profile

/etc/profile is sourced by all Bourne-compatible shells upon login: it sets up an environment upon login and application-specific settings by sourcing any readable /etc/profile.d/*.sh scripts.

Graphical

You can autostart programs automatically when you login into your Window Manager or Desktop Environment.

X session startup

See ~/.xinitrc and ~/.xprofile and /etc/xprofile.

X Desktop Group

  • /etc/xdg/autostart: The folder contains *.desktop files, which will be executed everytime an X session starts.
  • $XDG_CONFIG_HOME/autostart/: In this folder are .desktop files. These files determine which programs are loaded for which desktop environment. For an explanation of the desktop file standard refer to Desktop Entry Specification.

GNOME, KDE, Xfce

GNOME, KDE and Xfce all have a dedicated GUI for autostart settings, see the respective articles.

You can also directly put .desktop files in ~/.config/autostart/

KDE (Legacy)

KDE also has a specific folder: ~/.kde/Autostart or ~/.kde4/Autostart

LXDE

If your LXDE is installed according to ArchWiki's guide, Openbox is the default window manager for LXDE. The autostart files specified in the Openbox will be executed therefore.

  • /etc/xdg/lxsession/LXDE/autostart: global autostart file
  • ~/.config/autostart: *.desktop files or make a symlink to *.desktop files in /usr/share/applications/
  • ~/.config/lxsession/LXDE/autostart: not a shell script. Every line is a program to execute.

See LXDE#Autostart_Programs.

Fluxbox

See Fluxbox#Autostarting Applications.

Openbox

  • /etc/xdg/openbox/autostart: system-wide
  • ~/.config/openbox/autostart: user-specific

See Openbox#Startup programs.

Network

Hibernation & Resume