iceccd (1) - Linux Manuals

The daemon also has to run on clients sending compile jobs to the Icecream network. If a node should be able to send compile jobs, but never receive any, start the daemon with the option -m 0.

All Icecream daemons need to have contact to the Icecream scheduler which controls the distribution of data between compile nodes. Normally the daemon will automatically find the right scheduler. If this is not the case you can explicitly specify the name of the Icecream network and the host running the scheduler.

OPTIONS

-n netname

The name of the icecream network the daemon should connect to. There has to be a scheduler running for the network under the same network name.

-m max_processes

Maximum number of compile jobs started in parallel on machine running the daemon.

--no-remote

Prevents jobs from other nodes being scheduled on this one.

-w

-d, --daemonize

Detach daemon from shell.

-l logfile

Name of file where log output is written to.

-s scheduler_host

Name of host running the scheduler for the network the daemon should connect to. This option might help if the scheduler can't broadcast its presence to the clients due to firewall settings or similar reasons.

-v, -vv, -vvv

Control verbosity of daemon. The more v the more verbose.

-r, --run-as-user

Force running the daemon with user rights. Usually you will need to run the daemon with root rights.

-b env_basedir

Base directory for storing compile environments sent to the daemon by the compile clients.

-u, --nobody-uid nobodyuid

Id of user nobody. This user id is used when the daemon is dropping privileges.

--cache-limit MB

Maximum size in Mega Bytes of cache used to store compile environments of compile clients.

-N hostname

The name of the icecream host on the network.

AUTHOR

Cornelius Schumacher