LINUX.ORG.RU

История изменений

Исправление peregrine, (текущая версия) :

man journald.conf

да, так тоже можно )

И там чуть-ли не в самом начале написано то что написал superuser.

OPTIONS

       Storage=
       Storage=
           Controls where to store journal data. One of "volatile", "persistent", "auto" and
           "none". If "volatile", journal log data will be stored only in memory, i.e. below the
           /run/log/journal hierarchy (which is created if needed). If "persistent", data will be
           stored preferably on disk, i.e. below the /var/log/journal hierarchy (which is created
           if needed), with a fallback to /run/log/journal (which is created if needed), during
           early boot and if the disk is not writable.  "auto" is similar to "persistent" but the
           directory /var/log/journal is not created if needed, so that its existence controls
           where log data goes.  "none" turns off all storage, all log data received will be
           dropped. Forwarding to other targets, such as the console, the kernel log buffer, or a
           syslog socket will still work however. Defaults to "auto" in the default journal
           namespace, and "persistent" in all others.

PS

Про ln сами прочитайте, это ДЗ.

Исходная версия peregrine, :

man journald.conf

да, так тоже можно )

И там чуть-ли не в самом начале написано то что написал superuser.

OPTIONS

       Storage=
       Storage=
           Controls where to store journal data. One of "volatile", "persistent", "auto" and
           "none". If "volatile", journal log data will be stored only in memory, i.e. below the
           /run/log/journal hierarchy (which is created if needed). If "persistent", data will be
           stored preferably on disk, i.e. below the /var/log/journal hierarchy (which is created
           if needed), with a fallback to /run/log/journal (which is created if needed), during
           early boot and if the disk is not writable.  "auto" is similar to "persistent" but the
           directory /var/log/journal is not created if needed, so that its existence controls
           where log data goes.  "none" turns off all storage, all log data received will be
           dropped. Forwarding to other targets, such as the console, the kernel log buffer, or a
           syslog socket will still work however. Defaults to "auto" in the default journal
           namespace, and "persistent" in all others.