<p dir="ltr">I have a process running now to import ~3TB into hadoop. It's a single command that I forgot to run in screen. It will return when it finishes. Too small to script.</p>
<div class="gmail_quote">On Dec 18, 2013 9:56 AM, "JD" <<a href="mailto:jdp@algoloma.com">jdp@algoloma.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Never got into screen or tmux. Tend to script things, so submitting a batch task<br>
via "task spooler" automatically logs all output to a file and disconnects from<br>
the terminal. It also provides control over how many tasks run concurrently -<br>
queuing other jobs automatically.<br>
<br>
Or am I missing the point completely?<br>
<br>
Between task spooler and ansible and cluster-ssh, I feel well covered for any<br>
possible remote admin need. Task Spooler is not in many repositories, but it is<br>
1 tool that I will manually install on my batch processing systems.<br>
<br>
No need to remember much ... just put "ts" in front of any batch command. It<br>
becomes 2nd nature quickly.<br>
<br>
It has been around for a very long time. <a href="http://freecode.com/projects/taskspooler" target="_blank">http://freecode.com/projects/taskspooler</a><br>
<br>
On 12/18/2013 09:14 PM, Lightner, Jeff wrote:<br>
> To prevent hang up you have to start with nohup and end with ampersand (&).<br>
><br>
> However, the purpose of screen is NOT just to run a process in the background but to allow you to start one in the foreground then send it to background so you can either go to another terminal and pull it into foreground or simply pull it back into foreground when you log back in. As Jim notes screen is really good for when you know you're going to start a process that is going to run longer than you want to stick around and watch it but you do want to see its output or current status later.<br>
><br>
> Jeffrey C. Lightner<br>
> Sr. UNIX Administrator<br>
><br>
> DS Waters of America, Inc.<br>
> 5660 New Northside Drive NW<br>
> Suite 250 (adjust as needed)<br>
> Atlanta, GA 30328<br>
><br>
> P: <a href="tel:678-486-3516" value="+16784863516">678-486-3516</a><br>
> C: <a href="tel:678-772-0018" value="+16787720018">678-772-0018</a><br>
> F: <a href="tel:678-460-3603" value="+16784603603">678-460-3603</a><br>
> E: <a href="mailto:jlightner@water.com">jlightner@water.com</a><br>
><br>
><br>
><br>
><br>
><br>
> -----Original Message-----<br>
> From: <a href="mailto:ale-bounces@ale.org">ale-bounces@ale.org</a> [mailto:<a href="mailto:ale-bounces@ale.org">ale-bounces@ale.org</a>] On Behalf Of Paul Cartwright<br>
> Sent: Wednesday, December 18, 2013 6:28 AM<br>
> To: Atlanta Linux Enthusiasts<br>
> Subject: Re: [ale] How to move a running process to screen session<br>
><br>
> On 12/17/2013 10:21 PM, Jim Kinney wrote:<br>
>> Sometimes I start a process that is going to take far longer than I'm<br>
>> willing to wait on and I forgot to load up a screen session to run in<br>
>> so if my VPN connection dies my process dies with it. Such is the life<br>
>> of an admin.<br>
> what about & ?? can't you run it in the background ?? I do that with processes that I don't want hogging my terminal session ( like hodoku.py<br>
> ) and I close the screen session and the process is still running..<br>
><br>
><br>
_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
</blockquote></div>