On Wed, Jun 1, 2016 at 7:43 AM, Howard Chu <hyc(a)symas.com> wrote:
Tom Hughes wrote:
> On 01/06/16 12:19, Howard Chu wrote:
>> This is still looking at the problem back-asswards. The problem isn't
>> that screen and tmux are special cases. The problem is that some handful
>> of programs that got spawned in a GUI desktop environment are special
>> cases, not exiting when they should.
> I'm sorry, but I disagree.
> There are basically three things that I'm aware of that are used from a
> session to run something in background in a way that will survive the end
> the user session and you named them - nohup, screen and tmux.
Your awareness is apparently limited.
mysqldump, pg_dump, and rsync leap to mind as examples of potentially
lengthy procedures that need to continue even if the connecting user
shell from which they are executed is interrupted. So do some userland
"daemon" processes, such as a horrific "perl daemon" I've seen and
Python based "buildbot" daemon.