Michael Biebl a écrit : > Rainer Gerhards wrote: >> The reason is "because this is the way it was always done" and rsyslog is >> compatible to the past. > > Agreed, closing it as not-a-bug. > > There is basically no point in writing mark messages if you have regular > syslog > messages.
Hi, Thank you for your responses. If you look at the extract from the log file "messages", you see that there would be a mark to 1h17. But there was none. I have provided the log file "syslog" to show that rsyslog running and that there was no problem to write on the hard disk. And at 1h17 there were entries in the file "syslog" and no mark in the file "messages": Aug 2 01:17:01 yuggoth /USR/SBIN/CRON[17604]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Aug 2 01:17:03 yuggoth hddtemp[2900]: /dev/sda: MAXTOR STM3320613AS: 39 C Aug 2 01:17:03 yuggoth hddtemp[2900]: /dev/sdb: MAXTOR STM3320613AS: 44 C Aug 2 01:17:03 yuggoth hddtemp[2900]: /dev/sdc: MAXTOR STM3320613AS: 39 C Aug 2 01:17:03 yuggoth hddtemp[2900]: /dev/sdd: Maxtor 6V300F0: 47 C I have perhaps not been precise enough in my first post, and writing the marks every 20 minutes unconditionally was a suggestion. But I think, there would be a mark at 1h17. Regards. -- ============================================== | FRÉDÉRIC MASSOT | | http://www.juliana-multimedia.com | | mailto:frede...@juliana-multimedia.com | ===========================Debian=GNU/Linux=== -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
