[Info-vax] reasons I like long uptime

[already5chosen at yahoo.com]

On Friday, June 30, 2017 at 9:21:23 PM UTC+3, Paul Sture wrote:
> On 2017-06-29, already5chosen at yahoo.com <already5chosen at yahoo.com> wrote:
> > On Wednesday, June 28, 2017 at 4:53:10 PM UTC+3, Stephen Hoffman wrote:
> >> On 2017-06-28 11:04:43 +0000, John Reagan said:
> >> 
> >> > I'm surprised that large companies like Merck don't have a company-wide 
> >> > IT department to deploy the Microsoft patch from March to fix the 
> >> > SMB/ExternalBlue hole.  After Wannacry last month, I would expect 
> >> > EVERYBODY to pick up the security patches.
> >> 
> >> Maybe they were extending their aggregate uptime?
> >
> > Jokes asides, I personally like long uptimes at desktop not for sake
> > of dick measurements, but because it is convenient. You, may be, would
> > call it laziness, at the end it's the same thing.
> > 
> > My workplace consists of multiple command-line sessions each with
> > different accumulated histories and environment setting plus several
> > text editor windows, pdf viewer(s) plus sometimes other types of
> > document editors/viewer plus programs like Gnu Octave, often also with
> > several open sessions for several different issues.
> >
> > If there was (or should I say "if I knew"?) an easy way of
> > saving/restoring the state of everything then I wouldn't mind weekly
> > reboot. But as long as I am not aware of such possibility, I really
> > want long uptime, preferably years, anything less than 3 months is
> > very annoying.
> 
> I've largely got that using macOS.  My PDF viewers / editors will
> restore any documents which were open when I last quit those
> utilities, my editors do the same, 

Editors and PDF viewers are not really a problems for me too, because I tend to have just one session of each (with multiple tabs), so their built-in save/restore works satisfactorily.
But I would imagine that for people with more advanced habits than mine they do present problem.
As I said, after command line sessions, my 2nd biggest problem is Gnu Octave sessions. I do often have a couple of those, more rarely even three.

> and my Terminal sessions come
> back to the directories they were last in.
> 
> What does get lost: 
> 
> o - any ssh sessions from Terminal to remote systems, but tmux or screen
>     would solve that

I tend to think about it as the responsibility of remote systems.
Not sure I even would want it handled locally, for security reasons.

> o - my current viewing position in an audio or video file - open ones
>     do get reopened, but the play position is at the beginning
> 
> I do have a problem with a power cut though.  On logging in again after
> a restart, macOS will try to restart everything that was open at the
> power cut, and with the amount of stuff I typically have open, timeouts
> do occur.  If I am doing a controlled reboot, I close apps manually
> first to avoid that (they still preserve their open file state).
> 

I am pretty ignorant about macOS.
Are OS updates forced? If they are, for how long can you postpone them? How often OS updates require reboot or log-off? Does reboot due to macOS update feel more like "controlled reboot" or more like power cut? 

Luckily, at work I have no problem of power cuts. UPSes tends to work fine.

> -- 
> Everybody has a testing environment. Some people are lucky enough to
> have a totally separate environment to run production in.