1

How to stop a infinite running process(ztail) started by a ssh session after that session is closed

view story
linux-howto

http://unix.stackexchange.com – I have a peculiar problem. My server supports multiple ssh session simultaneously, so that multiple admins can manage( via Command line interface) it simultaneously. we have a command which calls ztail to show the compressed log files. Now when the current ssh session is closed( without pressing ctrl - c , to stop the tail command), this command should ideally stop working. But what I observed when I start a new ssh session that , the process(ztail) is still running in background and consuming my cpu, even though the previous session was closed. Now how can I know when the session was closed, (HowTos)

Danial's picture
Submitted by Danial on 11/11/2012

Stories similar to How to stop a infinite running process(ztail) started by a ssh session after that session is closed

I have a peculiar problem. My server supports multiple ssh session simultaneously, so that multiple admins can manage (via command line interface) it simultaneously. We have a command which calls ztail to show the compressed log files. Now when the current ssh session is closed (without pressing Ctrl-C, to stop the ztail command), this command should ideally stop working.

I have a peculiar problem. My server supports multiple ssh session simultaneously, so that multiple admins can manage it simultaneously.

We have a command which calls ztail to show the compressed log files and when the current ssh session is closed (without pressing ctrlc, to stop the tail command), the command should ideally stop working.

Hi Everyone, I am a new unix user. I started a qlogin session in SSH terminal, then I closed the window assuming that the qlogin session will be closed automatically. But it was still running. I tried to kill the process using kill ID or kill -9 ID, but the ID I got using ps aux | grep qlogin keeps changing. Does anyone have good suggestions on how to stop the qlogin process ?

Windows Performance Recorder runs in the background when I start windows and I want to stop this session, but I can't.

I know it is running because if I fire up the app and tries to start a new recording session I get http://i.imgur.com/CDfFbOl.png

But when I go to command line it says:

C:\Users\admin>wpr -status

Microsoft Windows Performance Recorder Version 6.2.9200 Copyright (c) 2012 Mic

I am working on CentOS6, and running a django server for my development on a tmux session as：

python manage.py runserver 0.0.0.0:8000

So I can read my debug string print on it.

While there is an unknown reason which made my tmux session lost, and I cannot to bak to my working session using "tmux attach" command.

I still can find my server is running by ps command, but I have no permission to k

The Non Session Manager is a robust session management API and implementation allowing for faster and vastly simplified workflows in Linux audio. NSM finally delivers on the broken promise made by LASH et al--for Non anyway. So read the at API documentation and get to patching your favorite applications so everybody can feel the relief 1. User Manual 1.1.

I would like to send a command to a screen session and if possible get the output.

My attempt at sending a command to a screen session is as I found on this website and lots of others, but it doesn't seem to work:

root@server [~]# screen -X "script -a -c 'ls -l' /tmp/command.log" && cat /tmp/command.log cat: /tmp/command.log: No such file or directory root@server [~]#

Note there is on

I've had this problem occur at random, intermittently, across boxes at multiple companies, multiple distros, and multiple kernel revs. I think that I'm just cursed.

What happens is that I'll have a new box loaded, and I'll be doing something inside ssh, like a yum update or an apt-get. Everything will be progressing fine and then the session just stops.

Installed McMyAdmin (minecraft manager) on Ubuntu 12.04 32 bit. Wrote my own service to start McMyAdmin (.net app running in Mono) in its own screen session, and be able to inject proper McMyAdmin commands into that session with the init.d script.