First create a new directory named getty@tty1.service.d under /etc/systemd/system:

+

[http://cgit.freedesktop.org/systemd/systemd/tree/NEWS#n655 Since systemd 198] unit files may now be extended via drop-in files without having to edit/override the unit files themselves, to learn more about this feature, consult [http://www.freedesktop.org/software/systemd/man/systemd.unit.html systemd.unit(5)] and search for ''Along with a unit file foo.service a directory foo.service.d/ may exist.''

+

+

There are two types of consoles virtual and serial ones. In most cases you would want to setup up autologin on virtual console, the one which device name is ''ttyN'', where ''N'' is a number. The configuration of the autologin for the serial consoles will be slightly different. Device names of the serial consoles look like ''ttySN'', where ''N'' is a number.

+

+

For the virtual console proceed with the following steps, the case with serial console is dealt with at the bottom of this page.

+

+

Create a new directory named {{ic|getty@tty1.service.d}} under {{ic|/etc/systemd/system}}:

# mkdir /etc/systemd/system/getty@tty1.service.d

# mkdir /etc/systemd/system/getty@tty1.service.d

−

Then create a new file named autologin.conf and add it into the directory:

+

Then create a new file named {{ic|autologin.conf}} and add it into the directory:

{{Tip|The option {{ic|1=Type=simple}} will delay the execution of agetty until all jobs (state change requests to units) are completed. On the other hand it may cause systemd boot-up messages to pollute the login prompt. This option is more useful when [[Start X at Login|starting X automatically]]. See {{ic|man systemd.service}} for more info.}}

+

{{Tip|The option {{ic|1=Type=idle}} will delay the execution of agetty until all jobs (state change requests to units) are completed. On the other hand it may cause systemd boot-up messages to pollute the login prompt. This option is more useful when [[Start X at Login|starting X automatically]]. See {{ic|man systemd.service}} for more info.}}

−

If wanting to use 'Type=simple', then your autologin.conf should look like this:

+

By default, {{ic|getty@.service}} uses {{ic|1=Type=idle}}. If you want to use {{ic|1=Type=simple}}, then your {{ic|autologin.conf}} should look like this:

This article describes how to automatically log in to a virtual console at the end of the boot process. This article only covers console log-ins; methods for starting an X server are described in Start X at Login.

Contents

Installation

Use drop-in feature of systemd for getty autologin

Since systemd 198 unit files may now be extended via drop-in files without having to edit/override the unit files themselves, to learn more about this feature, consult systemd.unit(5) and search for Along with a unit file foo.service a directory foo.service.d/ may exist.

There are two types of consoles virtual and serial ones. In most cases you would want to setup up autologin on virtual console, the one which device name is ttyN, where N is a number. The configuration of the autologin for the serial consoles will be slightly different. Device names of the serial consoles look like ttySN, where N is a number.

For the virtual console proceed with the following steps, the case with serial console is dealt with at the bottom of this page.

Create a new directory named getty@tty1.service.d under /etc/systemd/system:

# mkdir /etc/systemd/system/getty@tty1.service.d

Then create a new file named autologin.conf and add it into the directory:

Tip: The option Type=idle will delay the execution of agetty until all jobs (state change requests to units) are completed. On the other hand it may cause systemd boot-up messages to pollute the login prompt. This option is more useful when starting X automatically. See man systemd.service for more info.

By default, getty@.service uses Type=idle. If you want to use Type=simple, then your autologin.conf should look like this: