On Mon, 04 Mar 2019 22:14:56 -0800, T wrote:

On 3/4/19 7:40 PM, Sam Hill wrote:
On Mon, 04 Mar 2019 19:11:45 -0800, T wrote:
On 3/4/19 6:38 PM, Sam Hill wrote:
On Mon, 04 Mar 2019 17:55:57 -0800, T wrote:
For those that need to run 24/7, doing a reboot in the night clears
them up.

Think about what you just wrote: "For those that need to run
*24/7*,". How does a reboot fit into that?

Who is processing something 100% of the time?

The remote server that sits waiting for world-wide salespersons to log
business transactions... Geez, think beyond the mom-n-pop people you
serve for once.

You pick a stop when nothing is expected to be happening, like when
all the remote loggers have finally gone to sleep, etc.. And just let
everyone know when the reboot will occure.

What if the loggers are in Denver, Dubai, and Dingzhou?

My computer has been running since the last neighborhood power
failure, 67 days, 12 hours, 10 minutes ago.

A Windows machine?

No. (Now you're going to complain that 'this is a Windows group' - just
know I was picking on your silly comment about what "24/7" is.)

That is the longest I have seen! 12 days and one customer could not
type, or send eMail, and Chrome's windows shimmered.

"A Windows machine?" g

Maybe it's okay in your little world that not being able to run more
than a few days is sufficient.

Uhhhh. Sam, I was talking to a home user. Please do not go off on a
tangent.

Yeah, I suppose it was a bit of a tangent. But your statement that "24/7"
equates to "reboot each night" grabbed my immediate attention. As Char
stated, that was just wrong!