| 1 |
Grant Edwards wrote: |
| 2 |
> I've got a couple Gentoo machines that normally run 24/7. I've |
| 3 |
> learned over the years that it's a good idea to reboot them |
| 4 |
> occasionally (when I have some spare time and I know they're idle) |
| 5 |
> just to make they still can. |
| 6 |
> |
| 7 |
> I've settled on roughly once a month or so. |
| 8 |
> |
| 9 |
> What seems to happen if I don't do this is that some update (or |
| 10 |
> perhaps just a stupid configuration mistake on my part) will render |
| 11 |
> the machine non-bootable, and I won't discover it until several months |
| 12 |
> later at the worst possible moment when I'm in the middle of something |
| 13 |
> urgent and the power fails, or I type "reboot" into the wrong xterm, |
| 14 |
> or whatever. Or maybe those things don't happen to other people... |
| 15 |
> |
| 16 |
|
| 17 |
|
| 18 |
I reboot when the power fails. That is the number one reason that I |
| 19 |
reboot. The only other reason, adding a hard drive or something like |
| 20 |
that. Heck, I don't cut it off when I'm blowing out the dust. I used |
| 21 |
to reboot when I did a kernel update but even that isn't very often. |
| 22 |
Generally, I'll build a new kernel and then select it when I reboot, |
| 23 |
which may be months. I keep my older known to work kernels around in |
| 24 |
case the new kernel goes wonky. Little info since I built this rig a |
| 25 |
few years ago. |
| 26 |
|
| 27 |
|
| 28 |
|
| 29 |
root@fireball / # uprecords |
| 30 |
# Uptime | System |
| 31 |
Boot up |
| 32 |
----------------------------+--------------------------------------------------- |
| 33 |
1 193 days, 09:28:37 | Linux 3.5.3-gentoo Sat Sep 22 |
| 34 |
07:50:38 2012 |
| 35 |
2 184 days, 15:47:57 | Linux 3.18.7-gentoo Tue Dec 15 |
| 36 |
21:53:59 2015 |
| 37 |
3 116 days, 16:24:24 | Linux 3.16.3-gentoo Mon Oct 13 |
| 38 |
20:27:52 2014 |
| 39 |
4 111 days, 00:34:49 | Linux 3.18.7-gentoo Tue Mar 31 |
| 40 |
18:57:19 2015 |
| 41 |
5 101 days, 18:34:17 | Linux 3.5.3-gentoo Wed Dec 31 |
| 42 |
18:00:00 1969 |
| 43 |
-> 6 98 days, 20:55:12 | Linux 4.5.2-gentoo Sun Oct 23 |
| 44 |
20:09:26 2016 |
| 45 |
7 83 days, 02:15:38 | Linux 3.18.7-gentoo Wed Sep 23 |
| 46 |
19:50:20 2015 |
| 47 |
8 72 days, 12:03:16 | Linux 3.9.5-gentoo Sat Jul 13 |
| 48 |
19:11:24 2013 |
| 49 |
9 69 days, 00:44:23 | Linux 3.11.6-gentoo Mon Jan 6 |
| 50 |
03:33:34 2014 |
| 51 |
10 67 days, 09:29:07 | Linux 4.5.2-gentoo Wed Aug 17 |
| 52 |
10:38:08 2016 |
| 53 |
----------------------------+--------------------------------------------------- |
| 54 |
1up in 2 days, 21:39:06 | at Thu Feb 2 |
| 55 |
13:43:44 2017 |
| 56 |
no1 in 94 days, 12:33:26 | at Fri May 5 |
| 57 |
05:38:04 2017 |
| 58 |
up 1694 days, 09:23:14 | since Wed Dec 31 |
| 59 |
18:00:00 1969 |
| 60 |
down 15502 days, 12:41:2 | since Wed Dec 31 |
| 61 |
18:00:00 1969 |
| 62 |
%up 9.853 | since Wed Dec 31 |
| 63 |
18:00:00 1969 |
| 64 |
root@fireball / # |
| 65 |
|
| 66 |
|
| 67 |
|
| 68 |
Ignore the down part. When I first booted, the clock was set to the |
| 69 |
default which was ages ago. When I reset the clock, it got weird. I |
| 70 |
have no clue how or if I can fix that. |
| 71 |
|
| 72 |
Now that I'm basically forced to have a init thingy, that is a |
| 73 |
additional reason not to reboot. In the past, another distro, the init |
| 74 |
thingy would break and I couldn't boot. I despise having to have a init |
| 75 |
thingy. If I ever replace the hard drive that has my OS with a SSD or |
| 76 |
something, the separate /usr is gone. Maybe I can ditch the init thingy |
| 77 |
at that point. |
| 78 |
|
| 79 |
That's my info. Maybe it will give you something to think about. |
| 80 |
|
| 81 |
Dale |
| 82 |
|
| 83 |
:-) :-) |
Archives