This depends on what version you are using.
Versions below 1.20.0 (e.g., 1.12.8) store this information (command line
information, &c) in a file that is available to the queue daemon at the
remote host via NFS. These versions simply open a TCP/IP socket connection to
tell the remote host to look for new files in its NFS directory.
Versions 1.20.0 and higher (in pre-release) send this file directly to the
remote host via TCP/IP (thus eliminating the need for NFS.)
I hope this helps.
If you make any changes to GNU Queue that might be of interest to other
users, in the spirit of OpenSource software I hope you will submit the
patches to either bug...@gn... or the patch facility on Sourceforge.
Thanks.
Monica Lau wrote:
> Hi everyone!
>
> I am a student intern, working on a project that involves modifying a
> little bit of the Queue software. First, however, I must understand the
> source code in order to do so. I have been looking at the "queue.c"
> source code for two days now, and I am having trouble understanding the
> big picture. Can someone please give me a general overview of what
> queue.c is doing? After it parses the command line options and finds the
> load of all the hosts, then what does it do? I mainly want to understand
> how queue communicates with the queue daemon at the remote host, how
> information from what the user types on the command line gets transferred
> over to the queue daemon.
>
> Thank you,
> Monica
>
> _______________________________________________
> Queue-developers mailing list
> Que...@li...
> http://lists.sourceforge.net/mailman/listinfo/queue-developers
|
