Hacker News Reader

Comment by trollied | Hacker News Reader

I am well aware of setuid. I was informing the parent comment of which arg to use for the actual functionality.

I was surprised to hear OP wasn't aware of it as it was the first reason I ever had to use screen (shared remote debugging session.)

I use screen almost by default when connecting over SSH, but I've never used -x and didn't know about it.

Habbit from back in the dial-up days when connections got dropped quite frequently. Still relevant with laptop going into sleep mode and such.

So nice to just resume wherever you were as of nothing happened. Or to run jobs in the background, like long compiles, without an additional SSH session.

Often for long running jobs you want to see the status of where logging out of the system stops the job output.

Or where you can't risk dropping the terminal session, like during a system upgrade via SSH.

System upgrade shouldn't drop your session btw, at least not on most flavors I'm familiar with

The risk is anything else dropping your connection while an interactive long-running process is going. You can nohup, or run inside something like screen/tmux,

You're not wrong, but largely in the virtualized world we live in, it matters less and less when you have a virtual console.

That said the sshd session you are connected on is still running the old executable until the service is restarted AND your session ends, so even if sshd gets upgraded, you should still be good to go.

A thoughtfully designed upgrade system doesn’t do the real work side your terminal session in the interactive process.

Defense in depth is always valuable. The point of this thread is that screen protects your workflow from an unexpected disconnection.

Reply on news.ycombinator.com