#1 Le 12/05/2026, à 18:46
- bigloof

[RESOLU] Disposer des logs sytèmes sur plusieurs démarrage ?
Bonjour,
Comment configurer les journaux systèmes sur plusieurs démarrage ?
Je n'ai que le dernier démarrage (celui de la session en cours)
journalctl --list-boots
IDX BOOT ID FIRST ENTRY LAST ENTRY
0 490af3f47aaf465486c76e68d10b1053 Tue 2026-05-12 18:03:30 CEST Tue 2026-05-12 18:17:20 CESTUbuntu 24.04.4 LTS \n \l
No LSB modules are available.
Codename: noble
Linux version 6.8.0-111-generic (buildd@lcy02-amd64-088) (x86_64-linux-gnu-gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04.1) 13.3.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #111-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 11 23:16:02 UTC 2026Dernière modification par bigloof (Le 13/05/2026, à 12:19)
Xubuntu 24.04 64 Xfce et autres PC avec des variantes Xubuntu/Kubuntu en 32 et 64 bits / tablettes Android, téléphones Android
Hors ligne
#2 Le 13/05/2026, à 11:02
- geole
Re : [RESOLU] Disposer des logs sytèmes sur plusieurs démarrage ?
²Bonjour.
En standard, il doit y avoir plusieurs boots conservés.
Soit tu as modifié le paramêtrage.
Donne ce retour
cat /etc/systemd/journald.conf Soit le volume collecté est trop important et il y a élimination des fichiers pour ne pas dépasser 4Go de taille.
Donne ces retours.
journalctl --no-pager -b -n 200ls -Rl /var/log/journalDernière modification par geole (Le 13/05/2026, à 11:07)
Les écrans de l'installateur 26.04 https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#3 Le 13/05/2026, à 12:10
- bigloof

Re : [RESOLU] Disposer des logs sytèmes sur plusieurs démarrage ?
MERCI
Je pense avoir trouvé mon problème grâce aux commandes que tu m'as demandé de passer que je laisse pour information à la fin du post.
suite aux commandes passées, j'ai compris que /var/log était monté dans le fichier RAM ...
J'ai modifié le fichier /etc/fstab pour enlever ce montage nécessairement éphémère.
─> df -h /var/log
Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur
tmpfs 5,9G 848K 5,9G 1% /var/log
┌─( didier ) - ( 6.8.0-111-generic ) - ( ~ )cat /etc/systemd/journald.conf
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it under the
# terms of the GNU Lesser General Public License as published by the Free
# Software Foundation; either version 2.1 of the License, or (at your option)
# any later version.
#
# Entries in this file show the compile time defaults. Local configuration
# should be created by either modifying this file (or a copy of it placed in
# /etc/ if the original file is shipped in /usr/), or by creating "drop-ins" in
# the /etc/systemd/journald.conf.d/ directory. The latter is generally
# recommended. Defaults can be restored by simply deleting the main
# configuration file and all drop-ins located in /etc/.
#
# Use 'systemd-analyze cat-config systemd/journald.conf' to display the full config.
#
# See journald.conf(5) for details.
[Journal]
#Storage=auto
#Compress=yes
#Seal=yes
#SplitMode=uid
#SyncIntervalSec=5m
#RateLimitIntervalSec=30s
#RateLimitBurst=10000
#SystemMaxUse=
#SystemKeepFree=
#SystemMaxFileSize=
#SystemMaxFiles=100
#RuntimeMaxUse=
#RuntimeKeepFree=
#RuntimeMaxFileSize=
#RuntimeMaxFiles=100
#MaxRetentionSec=
#MaxFileSec=1month
#ForwardToSyslog=no
#ForwardToKMsg=no
#ForwardToConsole=no
#ForwardToWall=yes
#TTYPath=/dev/console
#MaxLevelStore=debug
#MaxLevelSyslog=debug
#MaxLevelKMsg=notice
#MaxLevelConsole=info
#MaxLevelWall=emerg
#LineMax=48K
#ReadKMsg=yes
#Audit=yes
┌─( didier ) - ( 6.8.0-111-generic ) - ( ~ )
└─> journalctl --no-pager -b -n 200
mai 13 11:44:43 Bureau dbus-daemon[6001]: [session uid=1000 pid=6001] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.23' (uid=1000 pid=6171 comm="xfwm4" label="unconfined")
mai 13 11:44:43 Bureau systemd[5979]: Starting gvfs-daemon.service - Virtual filesystem service...
mai 13 11:44:43 Bureau dbus-daemon[6001]: [session uid=1000 pid=6001] Successfully activated service 'org.gtk.vfs.Daemon'
mai 13 11:44:43 Bureau systemd[5979]: Started gvfs-daemon.service - Virtual filesystem service.
mai 13 11:44:43 Bureau wireplumber[5994]: BlueZ system service is not available
mai 13 11:44:43 Bureau wireplumber[5994]: <WpSiAudioAdapter:0x62036aece970> Object activation aborted: proxy destroyed
mai 13 11:44:43 Bureau wireplumber[5994]: <WpSiAudioAdapter:0x62036aece970> failed to activate item: Object activation aborted: proxy destroyed
mai 13 11:44:43 Bureau dbus-daemon[6001]: [session uid=1000 pid=6001] Activating via systemd: service name='org.freedesktop.impl.portal.PermissionStore' unit='xdg-permission-store.service' requested by ':1.10' (uid=1000 pid=5994 comm="/usr/bin/wireplumber" label="unconfined")
mai 13 11:44:43 Bureau systemd[5979]: Starting xdg-permission-store.service - sandboxed app permission store...
mai 13 11:44:43 Bureau dbus-daemon[6001]: [session uid=1000 pid=6001] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore'
mai 13 11:44:43 Bureau systemd[5979]: Started xdg-permission-store.service - sandboxed app permission store.
mai 13 11:44:43 Bureau wireplumber[5994]: <WpPortalPermissionStorePlugin:0x62036ac17870> Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera
mai 13 11:44:44 Bureau dbus-daemon[6001]: [session uid=1000 pid=6001] Activating via systemd: service name='org.freedesktop.thumbnails.Thumbnailer1' unit='tumblerd.service' requested by ':1.30' (uid=1000 pid=6217 comm="xfdesktop" label="unconfined")
mai 13 11:44:44 Bureau systemd[5979]: Starting tumblerd.service - Thumbnailing service...
mai 13 11:44:44 Bureau systemd[5979]: Starting xfce4-notifyd.service - XFCE notifications service...
mai 13 11:44:44 Bureau spice-vdagent[6269]: vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 does not exist, exiting
mai 13 11:44:44 Bureau dbus-daemon[6001]: [session uid=1000 pid=6001] Successfully activated service 'org.freedesktop.Notifications'
mai 13 11:44:44 Bureau systemd[5979]: Started xfce4-notifyd.service - XFCE notifications service.
mai 13 11:44:44 Bureau NetworkManager[1835]: <info> [1778665484.8754] agent-manager: agent[fbe7f3840ca2ec32,:1.108/org.freedesktop.nm-applet/1000]: agent registered
mai 13 11:44:44 Bureau dbus-daemon[6001]: [session uid=1000 pid=6001] Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service' requested by ':1.34' (uid=1000 pid=6237 comm="/usr/lib/x86_64-linux-gnu/tumbler-1/tumblerd" label="unconfined")
mai 13 11:44:44 Bureau systemd[5979]: Starting gvfs-udisks2-volume-monitor.service - Virtual filesystem service - disk device monitor...
mai 13 11:44:44 Bureau polkitd[1804]: Registered Authentication Agent for unix-session:c2 (system bus name :1.111 [/usr/libexec/polkit-mate-authentication-agent-1], object path /org/mate/PolicyKit1/AuthenticationAgent, locale fr_FR.UTF-8)
mai 13 11:44:45 Bureau dbus-daemon[6001]: [session uid=1000 pid=6001] Activating via systemd: service name='org.ayatana.bamf' unit='bamfdaemon.service' requested by ':1.36' (uid=1000 pid=6246 comm="plank" label="unconfined")
mai 13 11:44:45 Bureau systemd[5979]: Starting bamfdaemon.service - BAMF Application Matcher Framework...
mai 13 11:44:45 Bureau dbus-daemon[6001]: [session uid=1000 pid=6001] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
mai 13 11:44:45 Bureau systemd[5979]: Started gvfs-udisks2-volume-monitor.service - Virtual filesystem service - disk device monitor.
mai 13 11:44:45 Bureau dbus-daemon[6001]: [session uid=1000 pid=6001] Activating via systemd: service name='org.gtk.vfs.GPhoto2VolumeMonitor' unit='gvfs-gphoto2-volume-monitor.service' requested by ':1.34' (uid=1000 pid=6237 comm="/usr/lib/x86_64-linux-gnu/tumbler-1/tumblerd" label="unconfined")
mai 13 11:44:45 Bureau systemd[5979]: Starting gvfs-gphoto2-volume-monitor.service - Virtual filesystem service - digital camera monitor...
mai 13 11:44:45 Bureau dbus-daemon[6001]: [session uid=1000 pid=6001] Successfully activated service 'org.gtk.vfs.GPhoto2VolumeMonitor'
mai 13 11:44:45 Bureau systemd[5979]: Started gvfs-gphoto2-volume-monitor.service - Virtual filesystem service - digital camera monitor.
mai 13 11:44:45 Bureau dbus-daemon[6001]: [session uid=1000 pid=6001] Activating via systemd: service name='org.gtk.vfs.MTPVolumeMonitor' unit='gvfs-mtp-volume-monitor.service' requested by ':1.34' (uid=1000 pid=6237 comm="/usr/lib/x86_64-linux-gnu/tumbler-1/tumblerd" label="unconfined")
mai 13 11:44:45 Bureau systemd[5979]: Starting gvfs-mtp-volume-monitor.service - Virtual filesystem service - Media Transfer Protocol monitor...
mai 13 11:44:45 Bureau dbus-daemon[6001]: [session uid=1000 pid=6001] Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor'
mai 13 11:44:45 Bureau systemd[5979]: Started gvfs-mtp-volume-monitor.service - Virtual filesystem service - Media Transfer Protocol monitor.
mai 13 11:44:45 Bureau dbus-daemon[6001]: [session uid=1000 pid=6001] Activating via systemd: service name='org.gtk.vfs.GoaVolumeMonitor' unit='gvfs-goa-volume-monitor.service' requested by ':1.34' (uid=1000 pid=6237 comm="/usr/lib/x86_64-linux-gnu/tumbler-1/tumblerd" label="unconfined")
mai 13 11:44:45 Bureau dbus-daemon[6001]: [session uid=1000 pid=6001] Successfully activated service 'org.ayatana.bamf'
mai 13 11:44:45 Bureau systemd[5979]: Starting gvfs-goa-volume-monitor.service - Virtual filesystem service - GNOME Online Accounts monitor...
mai 13 11:44:45 Bureau systemd[5979]: Started bamfdaemon.service - BAMF Application Matcher Framework.
mai 13 11:44:45 Bureau dbus-daemon[6001]: [session uid=1000 pid=6001] Successfully activated service 'org.gtk.vfs.GoaVolumeMonitor'
mai 13 11:44:45 Bureau systemd[5979]: Started gvfs-goa-volume-monitor.service - Virtual filesystem service - GNOME Online Accounts monitor.
mai 13 11:44:45 Bureau dbus-daemon[6001]: [session uid=1000 pid=6001] Activating via systemd: service name='org.gtk.vfs.AfcVolumeMonitor' unit='gvfs-afc-volume-monitor.service' requested by ':1.34' (uid=1000 pid=6237 comm="/usr/lib/x86_64-linux-gnu/tumbler-1/tumblerd" label="unconfined")
mai 13 11:44:45 Bureau systemd[5979]: Starting gvfs-afc-volume-monitor.service - Virtual filesystem service - Apple File Conduit monitor...
mai 13 11:44:45 Bureau dbus-daemon[6001]: [session uid=1000 pid=6001] Successfully activated service 'org.gtk.vfs.AfcVolumeMonitor'
mai 13 11:44:45 Bureau systemd[5979]: Started gvfs-afc-volume-monitor.service - Virtual filesystem service - Apple File Conduit monitor.
mai 13 11:44:45 Bureau dbus-daemon[6001]: [session uid=1000 pid=6001] Successfully activated service 'org.freedesktop.thumbnails.Thumbnailer1'
mai 13 11:44:45 Bureau systemd[5979]: Started tumblerd.service - Thumbnailing service.
mai 13 11:44:45 Bureau onedrive[5991]: WARNING: Your onedrive client version is now obsolete and unsupported. Please upgrade your client version.
mai 13 11:44:45 Bureau onedrive[5991]: Current Application Version: 2.4.25
mai 13 11:44:45 Bureau onedrive[5991]: Version Available: 2.5.10
mai 13 11:44:45 Bureau onedrive[5991]: Configuring Global Azure AD Endpoints
mai 13 11:44:45 Bureau dbus-daemon[6001]: [session uid=1000 pid=6001] Activating via systemd: service name='org.freedesktop.portal.Desktop' unit='xdg-desktop-portal.service' requested by ':1.50' (uid=1000 pid=6326 comm="/usr/bin/python3 /usr/bin/displaycal-apply-profile" label="unconfined")
mai 13 11:44:45 Bureau systemd[5979]: Starting xdg-desktop-portal.service - Portal service...
mai 13 11:44:45 Bureau dbus-daemon[6001]: [session uid=1000 pid=6001] Activating via systemd: service name='org.freedesktop.portal.Documents' unit='xdg-document-portal.service' requested by ':1.55' (uid=1000 pid=6481 comm="/usr/libexec/xdg-desktop-portal" label="unconfined")
mai 13 11:44:45 Bureau systemd[5979]: Starting xdg-document-portal.service - flatpak document portal service...
mai 13 11:44:45 Bureau dbus-daemon[6001]: [session uid=1000 pid=6001] Successfully activated service 'org.freedesktop.portal.Documents'
mai 13 11:44:45 Bureau systemd[5979]: Started xdg-document-portal.service - flatpak document portal service.
mai 13 11:44:45 Bureau xdg-document-portal[6486]: Ignoring invalid max threads value 4294967295 > max (100000).
mai 13 11:44:45 Bureau xdg-desktop-por[6481]: Choosing gtk.portal for org.freedesktop.impl.portal.Lockdown as a last-resort fallback
mai 13 11:44:45 Bureau xdg-desktop-por[6481]: The preferred method to match portal implementations to desktop environments is to use the portals.conf(5) configuration file
mai 13 11:44:45 Bureau dbus-daemon[6001]: [session uid=1000 pid=6001] Activating via systemd: service name='org.freedesktop.impl.portal.desktop.gtk' unit='xdg-desktop-portal-gtk.service' requested by ':1.55' (uid=1000 pid=6481 comm="/usr/libexec/xdg-desktop-portal" label="unconfined")
mai 13 11:44:45 Bureau systemd[5979]: Starting xdg-desktop-portal-gtk.service - Portal service (GTK/GNOME implementation)...
mai 13 11:44:45 Bureau dbus-daemon[6001]: [session uid=1000 pid=6001] Successfully activated service 'org.freedesktop.impl.portal.desktop.gtk'
mai 13 11:44:45 Bureau systemd[5979]: Started xdg-desktop-portal-gtk.service - Portal service (GTK/GNOME implementation).
mai 13 11:44:45 Bureau rtkit-daemon[2508]: Supervising 14 threads of 8 processes of 2 users.
mai 13 11:44:45 Bureau rtkit-daemon[2508]: Supervising 14 threads of 8 processes of 2 users.
mai 13 11:44:45 Bureau rtkit-daemon[2508]: Supervising 14 threads of 8 processes of 2 users.
mai 13 11:44:45 Bureau xdg-desktop-por[6481]: No skeleton to export
mai 13 11:44:45 Bureau xdg-desktop-por[6481]: Choosing gtk.portal for org.freedesktop.impl.portal.FileChooser as a last-resort fallback
mai 13 11:44:45 Bureau xdg-desktop-por[6481]: Choosing gtk.portal for org.freedesktop.impl.portal.AppChooser as a last-resort fallback
mai 13 11:44:45 Bureau xdg-desktop-por[6481]: Choosing gtk.portal for org.freedesktop.impl.portal.Print as a last-resort fallback
mai 13 11:44:45 Bureau xdg-desktop-por[6481]: Choosing gtk.portal for org.freedesktop.impl.portal.Notification as a last-resort fallback
mai 13 11:44:45 Bureau xdg-desktop-por[6481]: Choosing gtk.portal for org.freedesktop.impl.portal.Inhibit as a last-resort fallback
mai 13 11:44:45 Bureau xdg-desktop-por[6481]: Choosing gtk.portal for org.freedesktop.impl.portal.Access as a last-resort fallback
mai 13 11:44:45 Bureau xdg-desktop-por[6481]: Choosing gtk.portal for org.freedesktop.impl.portal.Account as a last-resort fallback
mai 13 11:44:45 Bureau xdg-desktop-por[6481]: Choosing gtk.portal for org.freedesktop.impl.portal.Email as a last-resort fallback
mai 13 11:44:45 Bureau xdg-desktop-por[6481]: Choosing gtk.portal for org.freedesktop.impl.portal.DynamicLauncher as a last-resort fallback
mai 13 11:44:45 Bureau dbus-daemon[6001]: [session uid=1000 pid=6001] Successfully activated service 'org.freedesktop.portal.Desktop'
mai 13 11:44:45 Bureau systemd[5979]: Started xdg-desktop-portal.service - Portal service.
mai 13 11:44:46 Bureau onedrive[5991]: Initializing the Synchronization Engine ...
mai 13 11:44:46 Bureau onedrive[5991]: Initializing monitor ...
mai 13 11:44:46 Bureau onedrive[5991]: OneDrive monitor interval (seconds): 300
mai 13 11:44:47 Bureau onedrive[5991]: Starting a sync with OneDrive
mai 13 11:44:47 Bureau onedrive[5991]: Syncing changes and items from OneDrive ...
mai 13 11:44:47 Bureau systemd[1]: tmp-.mount_ShadowJA29eI.mount: Deactivated successfully.
mai 13 11:44:48 Bureau onedrive[5991]: Performing a database consistency and integrity check on locally stored data due to fullscan requirement ...
mai 13 11:44:48 Bureau dbus-daemon[6001]: [session uid=1000 pid=6001] Activating via systemd: service name='ca.desrt.dconf' unit='dconf.service' requested by ':1.36' (uid=1000 pid=6246 comm="plank" label="unconfined")
mai 13 11:44:48 Bureau systemd[5979]: Starting dconf.service - User preferences database...
mai 13 11:44:48 Bureau dbus-daemon[6001]: [session uid=1000 pid=6001] Successfully activated service 'ca.desrt.dconf'
mai 13 11:44:48 Bureau systemd[5979]: Started dconf.service - User preferences database.
mai 13 11:44:48 Bureau dbus-daemon[6001]: [session uid=1000 pid=6001] Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service' requested by ':1.48' (uid=1000 pid=6388 comm="/usr/lib/x86_64-linux-gnu/bamf/bamfdaemon" label="unconfined")
mai 13 11:44:48 Bureau systemd[5979]: Starting gvfs-metadata.service - Virtual filesystem metadata service...
mai 13 11:44:48 Bureau dbus-daemon[6001]: [session uid=1000 pid=6001] Successfully activated service 'org.gtk.vfs.Metadata'
mai 13 11:44:48 Bureau systemd[5979]: Started gvfs-metadata.service - Virtual filesystem metadata service.
mai 13 11:44:48 Bureau gnome-keyring-daemon[5998]: asked to register item /org/freedesktop/secrets/collection/login/79, but it's already registered
mai 13 11:44:48 Bureau gnome-keyring-d[5998]: asked to register item /org/freedesktop/secrets/collection/login/79, but it's already registered
mai 13 11:44:48 Bureau gnome-keyring-daemon[5998]: asked to register item /org/freedesktop/secrets/collection/login/79, but it's already registered
mai 13 11:44:48 Bureau gnome-keyring-d[5998]: asked to register item /org/freedesktop/secrets/collection/login/79, but it's already registered
mai 13 11:44:49 Bureau pkexec[6601]: pam_unix(polkit-1:session): session opened for user root(uid=0) by (uid=1000)
mai 13 11:44:49 Bureau pkexec[6601]: didier: Executing command [USER=root] [TTY=unknown] [CWD=/home/didier] [COMMAND=/usr/lib/update-notifier/package-system-locked]
mai 13 11:44:51 Bureau systemd[1]: tmp-.mount_ShadowXbvnqr.mount: Deactivated successfully.
mai 13 11:44:52 Bureau systemd[1]: Stopping user@113.service - User Manager for UID 113...
mai 13 11:44:52 Bureau systemd[2453]: Activating special unit exit.target...
mai 13 11:44:52 Bureau systemd[2453]: Stopped target default.target - Main User Target.
mai 13 11:44:52 Bureau systemd[2453]: Stopping at-spi-dbus-bus.service - Accessibility services bus...
mai 13 11:44:52 Bureau systemd[2453]: Stopping dbus.service - D-Bus User Message Bus...
mai 13 11:44:52 Bureau systemd[2453]: Stopping filter-chain.service - PipeWire filter chain daemon...
mai 13 11:44:52 Bureau systemd[2453]: Stopping gnome-keyring-daemon.service - GNOME Keyring daemon...
mai 13 11:44:52 Bureau systemd[2453]: Stopping gvfs-daemon.service - Virtual filesystem service...
mai 13 11:44:52 Bureau systemd[2453]: Stopping pipewire-pulse.service - PipeWire PulseAudio...
mai 13 11:44:52 Bureau systemd[2453]: Stopping xdg-permission-store.service - sandboxed app permission store...
mai 13 11:44:52 Bureau systemd[2453]: Stopped at-spi-dbus-bus.service - Accessibility services bus.
mai 13 11:44:52 Bureau systemd[2453]: Stopped gnome-keyring-daemon.service - GNOME Keyring daemon.
mai 13 11:44:52 Bureau systemd[2453]: Stopped xdg-permission-store.service - sandboxed app permission store.
mai 13 11:44:52 Bureau systemd[2453]: Stopped filter-chain.service - PipeWire filter chain daemon.
mai 13 11:44:52 Bureau systemd[2453]: Stopped dbus.service - D-Bus User Message Bus.
mai 13 11:44:52 Bureau systemd[2453]: Stopped pipewire-pulse.service - PipeWire PulseAudio.
mai 13 11:44:52 Bureau systemd[1]: run-user-113-gvfs.mount: Deactivated successfully.
mai 13 11:44:52 Bureau systemd[2453]: Stopped gvfs-daemon.service - Virtual filesystem service.
mai 13 11:44:52 Bureau systemd[2453]: Stopping wireplumber.service - Multimedia Service Session Manager...
mai 13 11:44:52 Bureau wireplumber[2486]: stopped by signal: Complété
mai 13 11:44:52 Bureau wireplumber[2486]: disconnected from pipewire
mai 13 11:44:52 Bureau systemd[2453]: Stopped wireplumber.service - Multimedia Service Session Manager.
mai 13 11:44:52 Bureau systemd[2453]: Stopping pipewire.service - PipeWire Multimedia Service...
mai 13 11:44:52 Bureau systemd[2453]: Stopped pipewire.service - PipeWire Multimedia Service.
mai 13 11:44:52 Bureau systemd[2453]: Removed slice session.slice - User Core Session Slice.
mai 13 11:44:52 Bureau systemd[2453]: Stopped target basic.target - Basic System.
mai 13 11:44:52 Bureau systemd[2453]: Stopped target paths.target - Paths.
mai 13 11:44:52 Bureau systemd[2453]: Stopped target sockets.target - Sockets.
mai 13 11:44:52 Bureau systemd[2453]: Stopped target timers.target - Timers.
mai 13 11:44:52 Bureau systemd[2453]: Stopped launchpadlib-cache-clean.timer - Clean up old files in the Launchpadlib cache.
mai 13 11:44:52 Bureau systemd[2453]: Closed dbus.socket - D-Bus User Message Bus Socket.
mai 13 11:44:52 Bureau systemd[2453]: Closed dirmngr.socket - GnuPG network certificate management daemon.
mai 13 11:44:52 Bureau systemd[2453]: Closed gcr-ssh-agent.socket - GCR ssh-agent wrapper.
mai 13 11:44:52 Bureau systemd[2453]: Closed gnome-keyring-daemon.socket - GNOME Keyring daemon.
mai 13 11:44:52 Bureau systemd[2453]: Closed gpg-agent-browser.socket - GnuPG cryptographic agent and passphrase cache (access for web browsers).
mai 13 11:44:52 Bureau systemd[2453]: Closed gpg-agent-extra.socket - GnuPG cryptographic agent and passphrase cache (restricted).
mai 13 11:44:52 Bureau systemd[2453]: Stopping gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation)...
mai 13 11:44:52 Bureau systemd[2453]: Closed gpg-agent.socket - GnuPG cryptographic agent and passphrase cache.
mai 13 11:44:52 Bureau systemd[2453]: Closed keyboxd.socket - GnuPG public key management service.
mai 13 11:44:52 Bureau systemd[2453]: Closed pipewire-pulse.socket - PipeWire PulseAudio.
mai 13 11:44:52 Bureau systemd[2453]: Closed pipewire.socket - PipeWire Multimedia System Sockets.
mai 13 11:44:52 Bureau systemd[2453]: Closed pk-debconf-helper.socket - debconf communication socket.
mai 13 11:44:52 Bureau systemd[2453]: Closed snapd.session-agent.socket - REST API socket for snapd user session agent.
mai 13 11:44:52 Bureau systemd[2453]: Closed speech-dispatcher.socket - Speech Dispatcher Socket.
mai 13 11:44:52 Bureau systemd[2453]: Closed gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation).
mai 13 11:44:52 Bureau systemd[2453]: Removed slice app.slice - User Application Slice.
mai 13 11:44:52 Bureau systemd[2453]: Reached target shutdown.target - Shutdown.
mai 13 11:44:52 Bureau systemd[2453]: Finished systemd-exit.service - Exit the Session.
mai 13 11:44:52 Bureau systemd[2453]: Reached target exit.target - Exit the Session.
mai 13 11:44:52 Bureau (sd-pam)[2454]: pam_unix(systemd-user:session): session closed for user lightdm
mai 13 11:44:52 Bureau systemd[1]: user@113.service: Deactivated successfully.
mai 13 11:44:52 Bureau systemd[1]: Stopped user@113.service - User Manager for UID 113.
mai 13 11:44:52 Bureau systemd[1]: user@113.service: Consumed 2.171s CPU time, 67.4M memory peak, 0B memory swap peak.
mai 13 11:44:52 Bureau systemd[1]: Stopping user-runtime-dir@113.service - User Runtime Directory /run/user/113...
mai 13 11:44:52 Bureau systemd[1]: run-user-113.mount: Deactivated successfully.
mai 13 11:44:52 Bureau systemd[1]: user-runtime-dir@113.service: Deactivated successfully.
mai 13 11:44:52 Bureau systemd[1]: Stopped user-runtime-dir@113.service - User Runtime Directory /run/user/113.
mai 13 11:44:52 Bureau systemd[1]: Removed slice user-113.slice - User Slice of UID 113.
mai 13 11:44:52 Bureau systemd[1]: user-113.slice: Consumed 6.290s CPU time, 140.9M memory peak, 0B memory swap peak.
mai 13 11:44:52 Bureau systemd[5979]: Started snap.canonical-livepatch.canonical-livepatch-a27a5566-eea9-4a0f-85e0-bba7c87445c8.scope.
mai 13 11:44:52 Bureau systemd[5979]: Started snap.canonical-livepatch.canonical-livepatch-535953e3-5764-43d8-b437-3ab54f9083a4.scope.
mai 13 11:44:52 Bureau systemd[5979]: Started snap.canonical-livepatch.canonical-livepatch-701d8fc7-c675-48fe-82a1-8aa66143afb6.scope.
mai 13 11:44:53 Bureau systemd[5979]: Started snap.canonical-livepatch.canonical-livepatch-80f06faf-85f8-433b-9559-197b7b205968.scope.
mai 13 11:45:01 Bureau CRON[6965]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
mai 13 11:45:01 Bureau CRON[6966]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
mai 13 11:45:01 Bureau CRON[6965]: pam_unix(cron:session): session closed for user root
mai 13 11:45:12 Bureau onedrive[5991]: Sync with OneDrive is complete
mai 13 11:45:55 Bureau systemd[5979]: Started snap.firefox.firefox-200b2b02-ed0c-4df5-b83e-69f820f75924.scope.
mai 13 11:45:55 Bureau systemd[1]: tmp-snap.rootfs_SnsCDD.mount: Deactivated successfully.
mai 13 11:45:58 Bureau dbus-daemon[1781]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.124' (uid=1000 pid=7221 comm="/snap/firefox/8247/usr/lib/firefox/firefox" label="snap.firefox.firefox (enforce)")
mai 13 11:45:58 Bureau systemd[1]: Starting systemd-timedated.service - Time & Date Service...
mai 13 11:45:58 Bureau dbus-daemon[1781]: [system] Successfully activated service 'org.freedesktop.timedate1'
mai 13 11:45:58 Bureau systemd[1]: Started systemd-timedated.service - Time & Date Service.
mai 13 11:45:58 Bureau rtkit-daemon[2508]: Supervising 7 threads of 4 processes of 1 users.
mai 13 11:45:58 Bureau rtkit-daemon[2508]: Supervising 7 threads of 4 processes of 1 users.
mai 13 11:45:58 Bureau rtkit-daemon[2508]: Supervising 7 threads of 4 processes of 1 users.
mai 13 11:45:58 Bureau rtkit-daemon[2508]: Supervising 7 threads of 4 processes of 1 users.
mai 13 11:45:58 Bureau rtkit-daemon[2508]: Successfully made thread 7451 of process 7221 owned by '1000' RT at priority 10.
mai 13 11:45:58 Bureau rtkit-daemon[2508]: Supervising 8 threads of 5 processes of 1 users.
mai 13 11:45:59 Bureau dbus-daemon[6001]: [session uid=1000 pid=6001] Activating service name='io.snapcraft.Settings' requested by ':1.92' (uid=1000 pid=7462 comm="dbus-send --print-reply=literal --session --dest=i" label="snap.firefox.firefox (enforce)")
mai 13 11:45:59 Bureau dbus-daemon[6001]: [session uid=1000 pid=6001] Successfully activated service 'io.snapcraft.Settings'
mai 13 11:45:59 Bureau io.snapcraft.Settings[7465]: userd.go:93: Starting snap userd
mai 13 11:45:59 Bureau rtkit-daemon[2508]: Supervising 8 threads of 5 processes of 1 users.
mai 13 11:45:59 Bureau rtkit-daemon[2508]: Supervising 8 threads of 5 processes of 1 users.
mai 13 11:46:00 Bureau rtkit-daemon[2508]: Supervising 8 threads of 5 processes of 1 users.
mai 13 11:46:00 Bureau rtkit-daemon[2508]: Supervising 8 threads of 5 processes of 1 users.
mai 13 11:46:00 Bureau kernel: usb 4-1: reset high-speed USB device number 2 using ehci-pci
mai 13 11:46:00 Bureau rtkit-daemon[2508]: Supervising 8 threads of 5 processes of 1 users.
mai 13 11:46:00 Bureau rtkit-daemon[2508]: Supervising 8 threads of 5 processes of 1 users.
mai 13 11:46:01 Bureau rtkit-daemon[2508]: Supervising 8 threads of 5 processes of 1 users.
mai 13 11:46:01 Bureau rtkit-daemon[2508]: Supervising 8 threads of 5 processes of 1 users.
mai 13 11:46:01 Bureau rtkit-daemon[2508]: Supervising 8 threads of 5 processes of 1 users.
mai 13 11:46:01 Bureau rtkit-daemon[2508]: Supervising 8 threads of 5 processes of 1 users.
mai 13 11:46:01 Bureau rtkit-daemon[2508]: Supervising 8 threads of 5 processes of 1 users.
mai 13 11:46:01 Bureau rtkit-daemon[2508]: Supervising 8 threads of 5 processes of 1 users.
mai 13 11:46:05 Bureau rtkit-daemon[2508]: Supervising 8 threads of 5 processes of 1 users.
mai 13 11:46:05 Bureau rtkit-daemon[2508]: Supervising 8 threads of 5 processes of 1 users.
mai 13 11:46:09 Bureau rtkit-daemon[2508]: Supervising 8 threads of 5 processes of 1 users.
mai 13 11:46:09 Bureau rtkit-daemon[2508]: Supervising 8 threads of 5 processes of 1 users.
mai 13 11:46:28 Bureau systemd[1]: systemd-timedated.service: Deactivated successfully.
┌─( didier ) - ( 6.8.0-111-generic ) - ( ~ )
└─> ─> ls -Rl /var/log/journal
ls: impossible d'accéder à '/var/log/journal': Aucun fichier ou dossier de ce nom
┌─( didier ) - ( 6.8.0-111-generic ) - ( ~ )Pas de répertoire journal !
ls -l /var/log/
total 652
-rw-r--r-- 1 root root 8352 mai 13 11:15 alternatives.log
drwxr-x--- 2 root adm 40 mai 5 15:22 apache2
-rw-r----- 1 root adm 0 mai 13 11:14 apport.log
drwxr-xr-x 2 root root 100 mai 13 11:16 apt
-rw-r----- 1 syslog adm 5581 mai 13 11:45 auth.log
-rw------- 1 root root 11030 mai 13 11:14 boot.log
-rw-rw---- 1 root utmp 0 mai 13 11:14 btmp
drwxr-x--- 2 root lp 80 mai 13 11:14 cups
-rw-r----- 1 root adm 100506 mai 13 11:14 dmesg
-rw-r--r-- 1 root root 34225 mai 13 11:16 dpkg.log
-rw-r--r-- 1 root root 1505 mai 13 11:14 gpu-manager.log
-rw-r----- 1 syslog adm 118672 mai 13 11:46 kern.log
-rw-rw-r-- 1 root utmp 0 mai 13 11:14 lastlog
drwx--x--x 2 root root 100 mai 13 11:14 lightdm
drwxr-xr-x 2 minidlna minidlna 40 mai 13 11:14 minidlna
drwx------ 2 root root 40 mai 13 11:14 private
lrwxrwxrwx 1 root root 39 mai 13 11:14 README -> ../../usr/share/doc/systemd/README.logs
-rw-r----- 1 syslog adm 318909 mai 13 11:49 syslog
drwxr-xr-x 2 root root 100 mai 13 11:14 unattended-upgrades
-rw-rw-r-- 1 root utmp 2688 mai 13 11:44 wtmp
-rw-r--r-- 1 root root 46442 mai 13 11:44 Xorg.0.logPas de saturation sur les disques ... mais le répertoire log monté sur tmpfs !
└─> df -h
Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur
tmpfs 1,2G 11M 1,2G 1% /run
/dev/sda1 55G 27G 26G 51% /
tmpfs 5,9G 0 5,9G 0% /dev/shm
tmpfs 5,0M 20K 5,0M 1% /run/lock
tmpfs 4,0G 8,0K 4,0G 1% /tmp
tmpfs 5,9G 848K 5,9G 1% /var/log
/dev/sdb1 688G 510G 144G 79% /old
/dev/sdc1 458G 281G 154G 65% /home
/dev/sdd1 100G 41G 59G 41% /Data1
/dev/sdd2 825G 732G 94G 89% /Data2
tmpfs 1,2G 144K 1,2G 1% /run/user/1000Xubuntu 24.04 64 Xfce et autres PC avec des variantes Xubuntu/Kubuntu en 32 et 64 bits / tablettes Android, téléphones Android
Hors ligne
#4 Le 13/05/2026, à 13:07
- ylag
Re : [RESOLU] Disposer des logs sytèmes sur plusieurs démarrage ?
Bonjour,
Vu au #3 :
ls: impossible d'accéder à '/var/log/journal': Aucun fichier ou dossier de ce nomIl faudrait créer ce répertoire, sinon je crois que les fichiers journaux ne seront pas conservés.
sudo mkdir -v /var/log/journalA+
Hors ligne
#5 Le 13/05/2026, à 15:55
- Watael

Re : [RESOLU] Disposer des logs sytèmes sur plusieurs démarrage ?
oui, en mode "auto".
cependant, par défaut (ce qui est le cas ici : storage est commenté), journald est configuré en "persistent", et devrait, en conséquence, créer /var/log/journal si le disque est writable, sinon (si j'ai bien compris le man journald.conf) écrire (et le créer s'il n'existe pas) sous /run/log/journal.
Connected \o/
Welcome to sHell. · eval is evil.
Hors ligne
#6 Le 13/05/2026, à 16:17
- ylag
Re : [RESOLU] Disposer des logs sytèmes sur plusieurs démarrage ?
Bonjour,
Si on crée manuellement /var/log/journal, faudrait probablement passer :
sudo systemctl restart systemd-journald... pour prendre en compte, sinon redémarrer.
Je crois aussi qu'il faut avoir Storage=persistent dans le fichier /etc/systemd/journald.conf
@Watael :
Sauf erreur de ma part, les fichiers dans /run/log/journal seraient volatiles, non conservés lors d'un redémarrage ?
A+
Dernière modification par ylag (Le 13/05/2026, à 16:18)
Hors ligne
#7 Le 13/05/2026, à 16:28
- Watael

Re : [RESOLU] Disposer des logs sytèmes sur plusieurs démarrage ?
ah, d'accord, c'est pourquoi il peut être créé même si le disque n'est writable !
persistent est le mode par défaut, et comme storage est commenté, ça devrait être le mode courant et créer /var/log/journal.
mais pourquoi ce répertoire n'est-il pas créé au démarrage ?
je me répond tout seul : on voit que /var/log est monté en tmpfs
il faudrait regarder /etc/fstab et supprimer ce montage...
Dernière modification par Watael (Le 13/05/2026, à 16:29)
Connected \o/
Welcome to sHell. · eval is evil.
Hors ligne
#8 Le 13/05/2026, à 16:40
- geole
Re : [RESOLU] Disposer des logs sytèmes sur plusieurs démarrage ?
sinon (si j'ai bien compris le man journald.conf) écrire (et le créer s'il n'existe pas) sous /run/log/journal.
s'il n'est pas automatiquement créé:
sudo mkdir -pv /var/log/journal
sudo chown root:systemd-journal /var/log/journalMais je ne sais pas ce que veut dire le signe +
a@a:~$ ls -l /var/log | grep journal
drwxr-sr-x+3 root systemd-journal 4096 Apr 25 18:06 journal
file /var/log/journal
/var/log/journal: setgid, directorydonc en plus
sudo chmod g+s /var/log/journalDernière modification par geole (Le 13/05/2026, à 16:59)
Les écrans de l'installateur 26.04 https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#9 Le 13/05/2026, à 16:42
- ylag
Re : [RESOLU] Disposer des logs sytèmes sur plusieurs démarrage ?
je me répond tout seul : on voit que /var/log est monté en tmpfs
il faudrait regarder /etc/fstab et supprimer ce montage...
Mille millions de mille sa... ! ![]()
J'avais loupé le montage en tmpfs de /var/log, merci de l'avoir pointé ...
Je me demande d'ailleurs pourquoi monter /var/log en tmpfs, on devrait plutôt configurer la taille et le nombre des fichiers journaux avec journalctl pour s'assurer de ne pas gonfler indûment ce répertoire, si on désire utiliser le mode persistent ?
A+
Dernière modification par ylag (Le 13/05/2026, à 16:44)
Hors ligne