> * Micah Cowan <zvpnu-4C9oUIHXRmIOQYmH/b5...@choyvp.tznar.bet> [2009-02-28 > 15:04:27 -0800]: > Marc Lanctot wrote: >> Typically I run commands on servers and let them run for some time.. >> when I'm done I kill all the processes with one command. >> >> I would like to be able to kill all my screens in one command as well, >> so I thought of parsing screen -r and sending a "kill command" to each >> screen, but I can't find anything on how to do that in the man page. >> >> I tried >> >> screen -S id -X exit > > Try: screen -S id -X quit
yes, but will it send EOF to each bash window? if it will not, I will lose my bash history! I often type quite complex commands (micro-scripts, actually) at the bash prompt, and recall them using C-r. I would like them to persist for some time in the bash history files until they are eventually forgotten due to dis-use. So, I love it that screen saves my bash sessions from crashing when my connection fails, but I hate it that screen does not tell the bash sessions in it to terminate when it is exiting (e.g., when the host is rebooted). In my ideal world the reboot script will send all screen sessions a "finish" signal and screens will send EOF to each bash window they have. -- Sam Steingold (http://sds.podval.org/) on CentOS release 5.6 (Final) X 11.0.60900031 http://jihadwatch.org http://truepeace.org http://palestinefacts.org http://www.memritv.org http://openvotingconsortium.org Software is like sex: it's better when it's free. _______________________________________________ screen-users mailing list screen-users@gnu.org https://lists.gnu.org/mailman/listinfo/screen-users
