Installing GNU Queue as an ordinary user is recommended only if you lack root (aka, superuser or Unix system administrative privileges) on your cluster.

You do not need to have system administrative privileges to install GNU Queue.

However, To allow all users in the cluster to use GNU Queue you should have your cluster's system administrator install Queue following the instructions in the chapter for See section Installation of GNU Queue by System Administrator (Preferred) installing Queue as root. However, if this is impractical, you may install Queue yourself without resorting to administrative superuser, or root, privileges by following the instructions in this chapter.

Note that, under its default configuration, GNU Queue supports only one installation per cluster, so if you install GNU Queue as an ordinary user you will be the only user able to run jobs through it. This can be overcome if another user edits GNU Queue's header files to change its network port numbers to avoid a conflict with another copy of GNU Queue running on the same cluster.

Also see See section Installation by Ordinary User on -DHAVE_IDENTD and running an RFC 931 identd service on cluster when installating GNU Queue as an ordinary user.

To do this, you will need write access to an NFS directory that is shared among all hosts in your cluster. In most cases, your system administrator will have set up your home directory this way.

Installing GNU Queue for one user:

1. Run ./configure . When installing as an ordinary user, configure sets the makefile to install GNU Queue into the current directory. queue will go in ./bin, queued daemon will go into ./sbin, /com/queue will be the shared spool directory, the host access control list file will go into ./share and the queued pid files will go into ./var . If you want things to go somewhere else, run ./configure --prefix=dir, where dir is the top-level directory where you want things to be installed. ./configure takes a number of additional options that you may wish to be aware of, ./configure --help gives a full listing of them. --bindir specifies where queue goes, --sbindir specifies where queued goes, --sharedstatedir where the spool directory goes, --datadir where the host access control file goes, and --localstatefile where the queued pid files go. If ./configure fails inelegantly, make sure lex is installed. GNU flex is an implementation of lex available from the FSF, http://www.gnu.org.
2. Now run make to compile the programs. If your make complains about a syntax error in the Makefile, you'll need to run GNU Make which is hopefully already installed on your machine (perhaps as "gmake" or "gnumake"), but, if not, you can obtain it from the FSF on prep.ai.mit.edu or its many mirrors.
3. If all goes well, make install will install the programs into directory you specified with ./configure. Missing directories will be created. The name of the localhost make install is being run on will be added to the host access control list if it is not already there.
4. Try running Queue. Start up ./queued on the localmachine. (If you did a make install on the localhost the localhost should already be in the host access control list file.) ./queue --help gives a list of options to Queue. Here are some simple examples:

   > queue -i -w -n -- hostname
   > queue -i -r -n -- hostname
   

   Here is a more sophisticated example. Try suspending and resuming it with Control-Z and 'fg':

   > queue -i -w -p -- emacs -nw
   

   If this example works on the localhost, you want want to add additional hosts to the host access control list in share (or --datadir) and start up queued on these.

   > queue -i -w -p -h hostname -- emacs -nw
   

   will run emacs on hostname. Without the -h argument, it will run the job on the best or least-loaded host in the ACL. See How do I configure a job queue's "profile" file? for details on how host selection is made.

You can also create additional queues for use with the -q and -d commands, as outlined for root users below. Each spooldir must have a profile file associated with it. See How do I configure a job queue's "profile" file? for details.

If you encounter problems with installation not explained here you should subscribe to the development list, queue-tips, and ask for help. Instructions for subscribing may be found off the development page.
werner.krebs@yale.edu