Re: Using SMARTd to monitor drives
Ray Andrews <[email protected]> Sat, 04 Feb 2017 07:15:10 -0800
| Newsgroups | gmane.linux.utilities.smartmontools |
|---|---|
| Message-ID | <[email protected]> |
On 04/02/17 03:24 AM, Christian Franke wrote: > Ray Andrews wrote: >> On 31/01/17 01:21 AM, Christian Franke wrote: >> >> >> >> Your question suggests that you never checked the SYSLOG output of >> smartd. Please do this first before asking further questions here. >> >> On Debian, try: >> grep -w smartd /var/log/daemon.log >> or for older logs: >> zgrep -w smartd /var/log/daemon.log.* >> That is very useful thanks. Honestly I thought you could only examine syslog under systemd using the official tools like 'journalctl' , they are always saying that it's binary now. I had no idea you could just grep. The entire subject of access to logs is another thing that has become very difficult to understand. Until now, I've been using "journalctl -p err -b -1", and not seeing very much :( > >> Yes, BUT, I want to see if the count ever increases. That is, I don't >> want to see '77' over and over again, but I do want to see if it goes to 78. > This is exactly the effect of the example from the mentioned mail. I didn't realize that. The docs seem to say it kills the entire test. As I replied last night, all of this is obvious to you, but not to others. But sorry to test your patience. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot