gearman_worker_unregister_all - Gearmand Documentation, http://gearman.info/
Link with -lgearman
gearman_worker_st is used for worker communication with the server.
gearman_worker_context() and gearman_worker_set_context() can be used to store an arbitrary object for the user.
gearman_worker_set_task_context_free_fn() sets a trigger that will be called when a gearman_task_st is released.
gearman_worker_timeout() and gearman_worker_set_timeout() get and set the current timeout value, in milliseconds, for the worker.
gearman_worker_function_exist() is used to determine if a given worker has a specific function.
gearman_worker_work() have the worker execute against jobs until an error occurs.
gearman_worker_grab_job() Takes a job from one of the job servers. It is the responsibility of the caller to free the job once they are done. This interface is used in testing, and is very rarely the correct interface to program against.
Normally malloc(3) and free(3) are used for allocation and releasing workloads. gearman_worker_set_workload_malloc_fn() and gearman_worker_set_workload_free_fn() can be used to replace these with custom functions.
If you need to remove a function from the server you can call either gearman_worker_unregister_all() to remove all functions that the worker has told the gearmand server about, or you can use gearman_worker_unregister() to remove just a single function.
To find out more information please check: http://gearman.info/
Data Differential http://www.datadifferential.com/
2011-2017, Data Differential, http://www.datadifferential.com/
|August 10, 2017||1.1.17|