anshultiwari1

When a client program wants to access a server by its domain name, it must find out how to translate the domain name into an actual routable address that it can use to communicate. It needs to know this information in order to get or send information to the server.

Some applications, including most web browsers, maintain an internal cache of recent queries. This is the first place the application will check, if it has this capability, in order to find the IP address of the domain in question. If it does not find the answer to its question here, it then asks the system resolver to find out what the address of the domain name is.

A resolver in general is any component that acts as a client-side participant in a DNS query. The system resolver is the resolving library that your operating system uses to seek out the answer for DNS queries. In general, system resolvers are usually what we consider stub resolvers because they are not capable of much complexity beyond searching a few static files on the system (lik

anshultiwari1

## tool to transfer jobs from one (local) tractor farm to other (away) tractor farm
## either directly using .alf file, maya file and user, in that order.

#!/bin/sh

maya -batch -file "$2" -command 'python "import pymel.core as pm; import sys, os; sys.path.append(\"/nas/projects/development/productionTools\"); from py_queue.sync import find_scene_deps; bin = \"/nas/projects/development/productionTools/py_queue/bin/submit_to_queue.py\"; import uuid; uuid_num = uuid.uuid4(); scene_name = pm.sceneName(); (file_path, _) = find_scene_deps.gen2(scene_name); (f1, _) = os.path.basename(scene_name).split(\".\"); print bin, \"SYNC_RENDER\", file_path, \"'"$3"'\", \"'"$1"'\", uuid_num, \"50\", \"'"$2"'\", \"%s_%s\" % (f1, uuid_num) "'