According to Wikipedia, a daemon "is a computer program that runs as a background process, rather than being under the direct control of an interactive user." Reference There are many uses for daemon tasks, from polling the batch system to collecting data from external sources. The features that unify these tasks are that they are long running (or regularly scheduled with cron) and that they have a small computational footprint (i.e. low average CPU and RAM usage).
It is against UF Research Computing policy to run any interactive or long running process on the login nodes (gator.rc.ufl.edu servers) or the development servers (dev1 or dev2). To fill the need that users have to run these tasks, we have deployed a server dedicated to daemon tasks.
Access to daemon server
Access to the daemon server is via ssh from one of the login servers for the cluster. For example, after connecting to gator.rc.ufl.edu, you can type:
The daemon server can also be access from your desktop by using SSH to connect to:
Running daemon processes
Once connected to daemon1, you can start your daemon process and have it run in the background. Please note that as specified above, daemon processes use few resources—daemon processes that use 100% of a CPU for extended periods negatively impact the performance of this server for other users and will be killed without warning.
To run a process in the background, either add a & to the end of the command, e.g.
nohup my.process.sh &
or start the process and once it is running, type control-Z and then bg to run it in the background.
Setting up cron tasks
To schedule a task to run regularly with cron, edit your crontab on the daemon1 node using:
There are several online resources for how to format a crontab file, but note that the configuration is specific to the server you are loged in on, so it is important to configure cron while logged into daemon1.