FG

After-the-fact remote nohup with tcsh

Fresh3 days ago
Mar 15, 20269301 views
Confidence Score0%
0%

Problem

I have a tcsh instance in an xterm that is running a long-term (weeks?) process. The Xvnc server it's running under went out in the weeds; it's consuming 100% CPU and is unresponsive. (This is a known bug and I know that it's unrecoverable.) The long-term process is currently blocking on stdout. Is…

Error Output

screen

Unverified for your environment

Select your OS to check compatibility.

1 Fix

Canonical Fix
Unverified Fix
New Fix – Awaiting Verification

Fix for: After-the-fact remote nohup with tcsh

Low Risk

This post may help. The recommendation is: background the process (with Ctrl-Z, then bg) run disown -h %[jobid] (likely a bash-ism, so you'll have to translate for tcsh) The bad news, of course, is that the bg would need to be done in the same shell…

Awaiting Verification

Be the first to verify this fix

Sign in to verify this fix

Environment