Difference between revisions of "Daemons"
| Line 1: | Line 1: | ||
| − | |||
| − | + | ==Overview== | |
| + | The daemon server provides UF Research Computing users with the space and resources to run long-running processes that do not require a lot of computational power. Please remember that these types of processes cannot be run on the login servers and the walltime on the test servers is thirty minutes. | ||
| − | + | Daemon processes run in the background of a system rather than under the direct control of an interactive user. There are many uses for daemon tasks, from polling the batch system to collecting data from external sources. Daemon tasks are usually long-running or scheduled to run recurrently. They are also characterized by a small computational footprint (i.e., low average CPU and RAM usage). '''Daemon processes should not use 100% of a CPU for extended periods and such processes will be killed without warning.''' | |
| − | Access to the daemon server | + | ==Access to the daemon server== |
| − | + | Connect to the cluster (gator.rc.ufl.edu) and use the ssh command to access the daemon server. | |
| + | <pre>ssh daemon1</pre> | ||
| − | + | You can also connect directly to the daemon server from your SSH client. Instead of connecting to gator.rc.ufl.edu, connect to | |
| − | + | <pre>daemon1.rc.ufl.edu</pre> | |
| − | |||
==Running daemon processes== | ==Running daemon processes== | ||
| − | + | There are two ways to run a process in the background: | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | 1. Add an ampersand (&) to the end of the command | |
| + | <pre>my.process.sh &</pre> | ||
| − | + | 2. Start the process and once it is running, type | |
| + | <pre>control-Z + b + g</pre> | ||
| − | + | ==Setting up recurring tasks with Cron== | |
| + | You can schedule a task to run recurrently with Cron, a time-based job scheduler by editing your crontab file on the daemon1 server. [[Cron | Click here for more detailed instructions.]] | ||
Revision as of 14:22, 15 April 2015
Overview
The daemon server provides UF Research Computing users with the space and resources to run long-running processes that do not require a lot of computational power. Please remember that these types of processes cannot be run on the login servers and the walltime on the test servers is thirty minutes.
Daemon processes run in the background of a system rather than under the direct control of an interactive user. There are many uses for daemon tasks, from polling the batch system to collecting data from external sources. Daemon tasks are usually long-running or scheduled to run recurrently. They are also characterized by a small computational footprint (i.e., low average CPU and RAM usage). Daemon processes should not use 100% of a CPU for extended periods and such processes will be killed without warning.
Access to the daemon server
Connect to the cluster (gator.rc.ufl.edu) and use the ssh command to access the daemon server.
ssh daemon1
You can also connect directly to the daemon server from your SSH client. Instead of connecting to gator.rc.ufl.edu, connect to
daemon1.rc.ufl.edu
Running daemon processes
There are two ways to run a process in the background:
1. Add an ampersand (&) to the end of the command
my.process.sh &
2. Start the process and once it is running, type
control-Z + b + g
Setting up recurring tasks with Cron
You can schedule a task to run recurrently with Cron, a time-based job scheduler by editing your crontab file on the daemon1 server. Click here for more detailed instructions.