So a week ago I rebooted one of my servers, running Slackware 14.1 64 bit. We use it for a fax server. It's an old Dell box sitting in a corner of the server room. Today I realized that the hylafax daemon hfaxd was not running (and it took people a week to realize their faxes weren't going out, go figure). After a bit of poking around I realized that 1) rc.hylafax was not chmod 755 and 2) there was no entry in rc.M anyhow. I fixed those, rebooted to make sure it was right, and now hfaxd starts up and faxing works and everyone is happy.

What bugged me was that this box has not been touched for over a year. Come to find out that when I set it a year or so ago, I manually started the hylafax daemon and never noticed that it wasn't set to autostart. As near as I can tell, the box has not been rebooted since. It sat in the corner of the server room for over a year happily chugging along, processing faxes, and just doing its job (I wish our Windows servers could do that!!).

So anyhow my question is this: is there any kind of reboot log that would show reboots from that long ago? I poked through /var/log and did not find anything helpful that went back that far. I'd like to find out for sure if it really has been that long since it was last rebooted.

Try /usr/bin/last.

EDIT: last -x shows just the shutdown/reboot events. (Well, perhaps not).

2 members found this post helpful.

Try

Try

last reboot

That was what I was looking for, tyvm!!!

And yeah, this box really has been running for about a year, untouched, ignored. What is weird that according to the bash history, I actually did a chmod 755 rc.hylafax when I was setting it up, but today I found the file to be chmod 644. <shrug> probably never figure that one out, I just don't remember what I did a year ago...

You could run "ls -lc rc.hylafax" to see when the last change occurred. Might be a clue there.

It was changed January of 2015 when I set it up. That is what bugs me. I see chmod 755 rc.hylafax in the history file, I see a file change date of 1/2015, but it was definitely chmod at 644 today.

But I had a lot of trouble getting it going when I initially set it up. I'm actually using Hylafax+ because we could never get Hylafax itself to work. So I switched to Hylafax+, and I've since done several Hylafax+ installs, and they are fast and smooth and relatively easy to get working now that I know what I'm doing. But Hylafax itself? Never worked. So it's very possible that the file I chmod'd was later deleted and replaced with the Hylafax+ file and that never got chmod'd to 755. Just guessing. That was over a year ago and I've done so much since then and honestly, I'm not as young as I used to be and my memory isn't as sharp as it used to be...