I assume you mean worker_resources, not properties, requirements, or restrictions. I also assume you're talking about worker configuration not job submission.
In that case, a resource defined on a worker means that this worker contains a certain number/amount of the given resource. In the example:
host.nuke6=1
(if put into the worker's local qb.conf or the supervisor's central qbwrk.conf for a worker), this means that the worker has 1 "nuke6" resource, which would imply that you're limiting the worker to run only one instance of nuke6 at a time (which also assumes that you submit the job with the proper reservation).
This is not the typical way of controlling how jobs are distributed around your farm. What is it that you are trying to do - maybe I can offer a better suggestion.
