I&#39;m working on a Linux machine through SSH (Putty). I need to leave a process running during the night, so I thought I could do that by starting the process in background (with an ampersand at the end of the command) and redirecting stdout to a file.

To my surprise, that doesn&#39;t work. As soon as I close the Putty window, the process is stopped.

How can I prevent that from happening??


How to prevent a background process from being stopped after closing SSH client in Linux

I&#39;m designing an android app which will need to do the following steps:

1. user pushes a button or otherwise indicates to &quot;sync data&quot;.
2. sync process will use REST web services to move data to and from the server.
3. the data will be stored locally in a sqlite database.
4. the sync process should provide status updates/messages to the UI 
5. the user should not be allowed to wander off to other parts of the application and do more work during the sync process.

The first time the sync process runs, it may take 10-20 minutes.
After the initial sync, less data will be transferred and stored and
I expect the process to take 1-2 minutes or less.

I&#39;ve been doing a lot of reading about android&#39;s `AsyncTask` and various examples of using a Service ... But I don&#39;t fully understand the design considerations and trade-offs of choosing one design over the other.  I currently have my demo project stubbed out using an AsyncTask.  After watching (most of) Developing Android REST client applications:  http://code.google.com/events/io/2010/sessions/developing-RESTful-android-apps.html# I&#39;m left confused the design patterns described here feel overly
complex, perhaps because I just &quot;don&#39;t get it&quot; yet.

I come from a java, spring, web and desktop application background.  Thinking and designing in terms of a handheld device is quite new to me. (What happens when the screen layout is changed? What happens when the phone rings while I&#39;m running a sync?)  Taking 2 steps back, if the initial sync IS going to be such a long running process, is there a better way for me to think about the problem-&gt;solution, the user experience, the user expectations of an application running on a phone? 

Would love to hear from some more experienced android developers out there who have already wrestled with these questions.


android design considerations: AsyncTask vs Service (IntentService?)

I have a Service in my application which is designed to run every 10 minutes. It basically checks up on our servers to see if everything is running properly and notifies the user of any problems. I created this application for internal use at our company.

My co-worker used the application over the long weekend and noticed that no checks were performed when the device went to sleep. I was under the impression that the Service was supposed to keep running in the background until I explicitly call `stopService()` in my code.

So ultimately, my goal is to have the service running until the user hits the off button in the application or kills the process.

I heard about something called `WakeLock` which is meant to keep the screen from turning off, which is not what I want. I then heard of another thing called a _partial WakeLock_, which keeps the CPU running even when the device is asleep. The latter sounds closer to what I need.

How do I acquire this WakeLock and when should I release it and are there other ways around this?

Keep a Service running even when phone is asleep?

In linux you can use *command* **&amp;** to run command on the background, the same will continue after the shell is offline. I was wondering is there something like that for windows…


How to run a command in the background on Windows?

I&#39;m looking for a way to get a background location update every n minutes in my iOS application.  I&#39;m using iOS 4.3 and the solution should work for non-jailbroken iPhones.

I tried / considered following options:

* `CLLocationManager startUpdatingLocation/startMonitoringSignificantLocationChanges`: This works in the background as expected, based on the configured properties, but it seems not possible to force it to update the location every n minutes
* `NSTimer`: Does work when the app is running in the foreground but doesn&#39;t seem to be designed for background tasks
* Local notifications: Local notifications can be scheduled every n minutes, but it&#39;s not possible to execute some code to get the current location (without the user having to launch the app via the notification).  This approach also doesn&#39;t seem to be a clean approach as this is not what notifications should be used for.
* `UIApplication:beginBackgroundTaskWithExpirationHandler`:  As far as I understand, this should be used to finish some work in the background (also limited in time) when an app is moved to the background rather than implementing &quot;long-running&quot; background processes.

How can I implement these regular background location updates?

How do I get a background location update every n minutes in my iOS application?

**Note**: I **don&#39;t** think this is a duplicate of [this question][1], which is talking about a non-background pack which *hangs* git *with a subtly different error message*.

---

In one of my git repositories, each time I invoke (for example) `git fetch`, git prints:

    Auto packing the repository in background for optimum performance.
    See &quot;git help gc&quot; for manual housekeeping.

It appears to print this every time if I do a `git fetch` repeatedly, even when there are no changes and nothing for `git fetch` to do. This doesn&#39;t make a lot of sense to me. It also seems to happen with other network operations, such as `git push` and `git pull`.

The command returns back to the prompt instantly with no further output, and I cannot find any git process running on my machine. It seems to happen only with this repository, and only on this machine. `git config -l | grep gc` returns nothing.

What can I do to diagnose or fix this problem?

    $ git --version 
    git version 2.0.1

I am using OS X 10.9.

  [1]: https://stackoverflow.com/questions/8633981/what-does-auto-packing-the-repository-for-optimum-performance-mean

Why does git keep telling me it&#39;s &quot;Auto packing the repository in background for optimum performance&quot;?

What is a good aproach to handle background processes in a NodeJS application? 

**Scenario**: After a user posts something to an app I want to crunch the data, request additional data from external resources, etc. All of this is quite time consuming, so I want it out of the req/res loop. Ideal would be to just have a queue of jobs where you can quickly dump a job on and a daemon or task runner will always take the oldest one and process it.

In RoR I would have done it with something like Delayed Job. What is the Node equivalent of this API?



Background processes in Node.js

I&#39;m using Java and I want to keep a servlet continuously running in my application, but I&#39;m not getting how to do it. My servlet has a method which gives counts of the user from a database on a daily basis as well as the total count of the users from the whole database. So I want to keep the servlet continuously running for that.

How to run a background task in a servlet based web application?

I connect to the linux server via putty SSH. I tried to run it as a background process like this:

    $ node server.js &amp;


However, after 2.5 hrs the terminal becomes inactive and the process dies.  Is there anyway I can keep the process alive even with the terminal disconnected?

---

**Edit 1**

Actually, I tried `nohup`, but as soon as I close the Putty SSH terminal or unplug my internet, the server process stops right away. 


Is there anything I have to do in Putty?

---

**Edit 2 (on Feb, 2012)**

There is a `node.js` module, [forever][1]. It will run node.js server as daemon service. 

  [1]: https://github.com/nodejitsu/forever

How to run Node.js as a background process and never die?

I start a background process from my shell script, and I would like to kill this process when my script finishes.

How to get the PID of this process from my shell script? As far as I can see variable ``$!`` contains the PID of the current script, not the background process.

How to get process ID of background process?

In an ASP.Net application, the user clicks a button on the webpage and this then instantiates an object on the server through the event handler and calls a method on the object.
The method goes off to an external system to do stuff and this could take a while. So, what I would like to do is run that method call in another thread so I can return control to the user with &quot;Your request has been submitted&quot;.
I am reasonably happy to do this as fire-and-forget, though it would be even nicer if the user could keep polling the object for status.

What I don&#39;t know is if IIS allows my thread to keep running, even if the user session expires.
Imagine, the user fires the event and we instantiate the object on the server and fire the method in a new thread. The user is happy with the &quot;Your request has been submitted&quot; message and closes his browser. Eventually, this users session will time out on IIS, but the thread may still be running, doing work. Will IIS allow the thread to keep running or will it kill it and dispose of the object once the user session expires?


EDIT: From the answers and comments, I understand that the best way to do this is to move the long-running processing outside of IIS. Apart from everything else, this deals with the appdomain recycling problem. In practice, I need to get version 1 off the ground in limited time and has to work inside an existing framework, so would like to avoid the service layer, hence the desire to just fire off the thread inside IIS. In practice, &quot;long running&quot; here will only be a few minutes and the concurrency on the website will be low so it should be okay. But, next version definitely will need splitting into a separate service layer.


Can I use threads to carry out long-running jobs on IIS?

We are working with .NET Core Web Api, and looking for a lightweight solution to log requests with variable intensity into database, but don&#39;t want client&#39;s to wait for the saving process.  
Unfortunately there&#39;s no `HostingEnvironment.QueueBackgroundWorkItem(..)` implemented in `dnx`, and `Task.Run(..)` is not safe.  
Is there any elegant solution?

Alternative solution to HostingEnvironment.QueueBackgroundWorkItem in .NET Core

I am using the program synergy together with an ssh tunnel

It works, i just have to open an console an type these two commands:

    ssh -f -N -L localhost:12345:otherHost:12345 otherUser@OtherHost
    synergyc localhost

because im lazy i made an Bash-Script which is run with one mouseclick on an icon: 

    #!/bin/bash
    ssh -f -N -L localhost:12345:otherHost:12345 otherUser@OtherHost
    synergyc localhost

the Bash-Script above works as well, but now i also want to kill synergy and the ssh tunnel via one mouseclick, so i have to save the PIDs of synergy and ssh into file to kill them later:

    #!/bin/bash

    mkdir -p /tmp/synergyPIDs || exit 1
    rm -f /tmp/synergyPIDs/ssh || exit 1
    rm -f /tmp/synergyPIDs/synergy || exit 1
    
    [ ! -e /tmp/synergyPIDs/ssh ] || exit 1
    [ ! -e /tmp/synergyPIDs/synergy ] || exit 1

    ssh -f -N -L localhost:12345:otherHost:12345 otherUser@OtherHost
    echo $! &gt; /tmp/synergyPIDs/ssh
    synergyc localhost
    echo $! &gt; /tmp/synergyPIDs/synergy

But the files of this script are empty.

How do I get the PIDs of ssh and synergy?  
(I try to avoid `ps aux | grep ... | awk ... | sed ...` combinations, there has to be an easier way.)

How do I kill a backgrounded/detached ssh session?

How can I run a shell script and immediately *background* it, however keep the ability to inspect its output any time by tailing `/tmp/output.txt`.

It would be nice if I can *foreground* the process too later.

---
### P.S.  
It would be really cool if you can also show me how to &quot;send&quot; the backgrounded process in to a GNU screen that may or may not have been initialized.

All Background Process Solutions on Gang of Coders

Total of 14 Background Process Solutions