$ kill -15 -1 Will gracefully kill all PIDs running as the user executing the command. $ kill -9 -1 Will force quit all PIDs. This is a quick way of killing all processes and log out at the same time. You could even assign this command to an alias. NB: do not run the above commands as root since it will kill all PIDs running as that UID. -----Original Message----- From: Speakup [mailto:speakup-bounces@xxxxxxxxxxxxxxxxx] On Behalf Of Kerry Hoath Sent: 1. april 2013 13:22 To: Speakup is a screen review system for Linux. Subject: Re: Screen help Screen is only adding one more control d to your logout sequence. Why not control a x to lock the screen then close your cygwin terminal to force a detach? It's expected behaviour for screen to launch one shell with stuff running in it. So you launch a su shell from screen, you have the login shell, the screen shell and the su shell, that's standard Unix with screen behaviour. Short of setting up an alias to kill your login shell and everything under it I don't see a way around this. Even if you don't run screen there is still 3 lots of control-d to log out one from su shell, one from screen and one from the box. Seems like a lot of effort to get rid of one control d have you even tried setting screen as a login shell on a test account to see if this would function? Only other way I can see of dealing with this is to tell screen to launch popular processes like mutt in screen windows in .screenrc, control-a c to create a new shell. Other than that you're out of luck. Regards, Kerry. On 1/04/2013 7:31 PM, Tony Baechler wrote: > Yes, but this assumes that I'm at the local console. I almost never > am. When I am, I only have to use the Alt-right arrow to get to > another VT. That doesn't work with ssh which is usually how I > connect. I use ssh over the LAN. I just want one press of ^d to log > me out instead of two. As it is now, if I su to root,I have to press > ^d four times. The first exits my root shell, the second exits > Screen, the third logs me out and the fourth closes my Cygwin bash > shell. There must be a quicker and easier way. > > On 3/31/2013 9:14 PM, Devon Stewart wrote: >> I did this a while back. It got a bit unusable on a remote machine, >> but it could work for you: >> >> Create a script, and use this in your inittab (or however you launch >> your VTs) >> >> Use 'tty' to determine your TTY name >> Look for a screen session matching that name. >> If it doesn't, create it. >> If it does, attach to it. >> >> Should be pretty straight forward. I used a technique like this to >> separate shell history files per VT for a friend of mine. >> >> -Devon >> > _______________________________________________ > Speakup mailing list > Speakup at linux-speakup.org > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup _______________________________________________ Speakup mailing list Speakup at linux-speakup.org http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
