hello,
why /var/log/dmesg was suppressed ?
i would like have my system log with orodatage like
Wed Julÿ 8 08:34:24 AM CEST 2026
by date for log my system, i have some hardware problem on trixe and
T480s and i can't see the boot log or any else
kinds regards,
jean-christophe
i would like have my system log with orodatage likeHello Jean-Christophe, have you tried command dmesg?-e ?
Wed Jul 8 08:34:24 AM CEST 2026
hello,
why /var/log/dmesg was suppressed ?
If you don't have this file (or if it's empty), then make sure you
have the rsyslog package installed.
If you don't have this file (or if it's empty), then make sure you
have the rsyslog package installed. ?That one stopped being installed
by default some time ago, in favor of systemd's binary journaling.
On Wednesday 08 July 2026 07:23:33 am Greg Wooledge wrote:
If you don't have this file (or if it's empty), then make sure you
have the rsyslog package installed. ÿThat one stopped being installed
by default some time ago, in favor of systemd's binary journaling.
Why would they have done that? I remember reading about that in here
some time back, but don't understand the reasoning behind that
particular change...
Roy J. Tellason, Sr. <roy@rtellason.com> wrote:
On Wednesday 08 July 2026 07:23:33 am Greg Wooledge wrote:
If you don't have this file (or if it's empty), then make sure you
have the rsyslog package installed. ÿThat one stopped being installed
by default some time ago, in favor of systemd's binary journaling.
Why would they have done that? I remember reading about that in here
some time back, but don't understand the reasoning behind that
particular change...
People who want or need the traditional syslog know how to install it.
The rest doesn't and it reduced the unnecessary package bloat and log duplication.
I'd go as far as to say that the vast majority of non-server systems
does not need a traditional syslog deamon.
Roy J. Tellason, Sr. <roy@rtellason.com> wrote:
On Wednesday 08 July 2026 07:23:33 am Greg Wooledge wrote:
If you don't have this file (or if it's empty), then make sure
you
have the rsyslog package installed. ÿThat one stopped being
installed
by default some time ago, in favor of systemd's binary
journaling.
Why would they have done that?ÿ I remember reading about that in
here
some time back,ÿ but don't understand the reasoning behind that
particular change...
People who want or need the traditional syslog know how to install
it.
The rest doesn't and it reduced the unnecessary package bloat and log duplication.
I'd go as far as to say that the vast majority of non-server systems
does not need a traditional syslog deamon.
Gr�áe,
Sven.
On Tue 14 Jul 2026 at 00:39:50 (-0400), Sven Hartge wrote:
I'd go as far as to say that the vast majority of non-server systems
does not need a traditional syslog deamon.
Beg to differ. It's very handy to have around if you run (say) a
backup script from cron and have
logger -t 'backups' start
# rsync or whatever
logger -t 'backups' finish
leave a nice message for you.
Sven Hartge <sven@svenhartge.de> wrote:
Roy J. Tellason, Sr. <roy@rtellason.com> wrote:
On Wednesday 08 July 2026 07:23:33 am Greg Wooledge wrote:
If you don't have this file (or if it's empty), then make sure you
have the rsyslog package installed. ÿThat one stopped being installed
by default some time ago, in favor of systemd's binary journaling.
Why would they have done that? I remember reading about that in here
some time back, but don't understand the reasoning behind that
particular change...
People who want or need the traditional syslog know how to install it.
The rest doesn't and it reduced the unnecessary package bloat and log
duplication.
I'd go as far as to say that the vast majority of non-server systems
does not need a traditional syslog deamon.
One significant downside of systemd's journal is that, with default
settings, it eats up a **lot** of disk space. It's probably not
significant on laptops/desktops but on Rasberry Pis, Beaglebones and
similar systems it can cause problems.
On Tue 14 Jul 2026 at 00:39:50 (-0400), Sven Hartge wrote:
I'd go as far as to say that the vast majority of non-server systems
does not need a traditional syslog deamon.
Beg to differ. It's very handy to have around if you run (say) a
backup script from cron and have
logger -t 'backups' start
# rsync or whatever
logger -t 'backups' finish
leave a nice message for you.
One significant downside of systemd's journal is that, with default
settings, it eats up a **lot** of disk space. It's probably not
significant on laptops/desktops but on Rasberry Pis, Beaglebones and
similar systems it can cause problems.
On Wednesday 08 July 2026 07:23:33 am Greg Wooledge wrote:
If you don't have this file (or if it's empty), then make sure you
have the rsyslog package installed. ÿThat one stopped being installed
by default some time ago, in favor of systemd's binary journaling.
Why would they have done that? I remember reading about that in here
some time back, but don't understand the reasoning behind that
particular change...
| Sysop: | Jacob Catayoc |
|---|---|
| Location: | Pasay City, Metro Manila, Philippines |
| Users: | 5 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 498677:21:05 |
| Calls: | 212 |
| Calls today: | 3 |
| Files: | 910 |
| D/L today: |
31 files (22,593K bytes) |
| Messages: | 69,826 |