Installation Instructions

*************************

Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,

   This file is free documentation; the Free Software Foundation gives

unlimited permission to copy, distribute and modify it.

Basic Installation

==================

   Briefly, the shell commands `./configure; make; make install' should

configure, build, and install this package.  The following

more-detailed instructions are generic; see the `README' file for

instructions specific to this package.

   For packages that use the X Window System, `configure' can usually

find the X include and library files automatically, but if it doesn't,

you can use the `configure' options `--x-includes=DIR' and

`--x-libraries=DIR' to specify their locations.

Particular systems

==================

   On HP-UX, the default C compiler is not ANSI C compatible.  If GNU

CC is not installed, it is recommended to use the following options in

order to use an ANSI C compiler:

and if that doesn't work, install pre-built binaries of GCC for HP-UX.

   On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot

parse its `<wchar.h>' header file.  The option `-nodtk' can be used as

a workaround.  If GNU CC is not installed, it is therefore recommended

to try

     ./configure CC="cc"

and if that doesn't work, try

     ./configure CC="cc -nodtk"

Specifying the System Type

==========================

   There may be some features `configure' cannot figure out

automatically, but needs to determine by the type of machine the package

will run on.  Usually, assuming the package is built to be run on the

_same_ architectures, `configure' can figure that out, but if it prints

a message saying it cannot guess the machine type, give it the

`--build=TYPE' option.  TYPE can either be a short name for the system

type, such as `sun4', or a canonical name which has the form:

     CPU-COMPANY-SYSTEM

where SYSTEM can have one of these forms:

   See the file `config.sub' for the possible values of each field.  If

`config.sub' isn't included in this package, then this package doesn't

need to know the machine type.

   If you are _building_ compiler tools for cross-compiling, you should

use the option `--target=TYPE' to select the type of system they will

produce code for.

   If you want to _use_ a cross compiler, that generates code for a

platform different from the build platform, you should specify the

"host" platform (i.e., that on which the generated programs will

1. Create a CLI interface for distren

	X command: distren

	X args: -i infile.tar.bz2 -o outfile.tar.bz2 

	action: submits and blocks and retreives result of rendering the contents of infile.tar.bz2. Should currently just call stub functions.

2. Design of stubs in distren library:

   	X Stub for submitting file to server

	WIP Write configuration loader

	Stub for submitting file to a server (using a stream)

	Stub for waiting for server -> Maybe the client can just poll? I've got to decide this.

	Stub for retrieving result (using another stream)

  int priority;

  int mode; // 0 = Static Render, stop at Spp, or infinity if spp is null. Framerange is ignored || 1 = animation, stop at Spp and stay in framerange.

  int spp;

  struct frameset ** frameset;

} luxjob[max];

int main(int argc, char *argv[])

{

/* !!!!!!! Important notes !!!!!!!!!!!!

So, we need a common key. Maybe. Or we need to generate a key in registeruser() and get it to the client somehow.

If we use a common key, then we'll need different passphrases for each user, which would be kinda crazy. How can

we get a key generated on the server, and transferred to the client's distrend?

*/

  int cont = 1;

  struct distrend_listenset *listenset;

  struct distrend_config *config;

  distrend_do_config(argc, argv, &config);

}

struct distrend_config

{

  cfg_t *mycfg;

  struct options_common *options;

  struct distrend_listen **listens; /*< Null terminated array of structs */

}

// Registration on server. Needs attention. (e.g., people could make tons of accounts with the key we give them...

// Set up distrend -c username email@example.com

// We must prevent multi-user-creation abuse, too.

void registeruser(char *username, char *email){

  // Logs into sandboxed user on zserver2 and registers a user. Should eventually generate a key on the server and return it to the user.

  // All created user accounts should be sandboxed accordingly, requiring a different skel, and the default shell to be rbash. They also

  // need a custom path, which can be defined in the .bash_profile of the skel. All activity of server-side configuration should be documented

  // to ease the creation of new distren servers, or it should be automated and made much more all-inclusive, not requiring much config.

  char buf[10];

  struct execio *testrem;

  char *execargv[] =

      }

    buf[readlen] = '\0'; // Null-terminating the end of it again based on how large the data is?

    fprintf(stderr, "read \"%s\"\n", buf);

    }

  execio_close(testrem);

}

void loginuser(char *username, int secret){

  char buf[10];

  struct execio *testrem;

  char *execargv[] =

    {

  "ssh",

  "distren_setup@protofusion.org",

  "-i",

  "setup.rsa", // We gotta figure out how we're going to do the whole keys thing... maybe grab this key via http? But have a secret password compiled in distren to prevent fraud?

  "-p",

  "23",

  (char *)NULL

  };

  size_t readlen;

  fprintf(stderr, "Opening stream:\n", execio_open(&testrem, "ssh", execargv));

  buf[9] = '\0'; // null-terminating the array...

  while(!execio_read(testrem, buf, 9, &readlen)) // What's with the readlen stuff?

    {

      if(readlen > 9) {

	fprintf(stderr, "!!!! Something is terribly wrong!\n");

      }

      if(buf == 0) {

	fprintf(stderr, "**** Operation successful, or so we hope. We got no output. Just kidding. You will never see this. Something else should catch this though!");

	while(x < total){

		blendjob[jobnum_new].frameset[x].frame_num = fcount;

		x++;

		fcount++;

	}

	highest_jobnum++;

}

// matches your computer up with a lovely frame to render

int frame_finder(){

	int finder_jobnum = 0;

	int frameset_count = 0; // the frameset number, because frames in an animation don't start at zero

	short int done = 0;

	for(int priority = 10; priority >= 1; priority--){ // start the scan for the next job with the highest priority

		finder_jobnum = hcfjob + 1; // reset it to start scanning at first uncompleted job for the pass at each priority level

		while(finder_jobnum <= highest_jobnum){

			if(blendjob[finder_jobnum].priority = priority){  // looks for a job with the current priority value

				done = 1;									  // notice it starts by looking at the oldest job first

				break;

			}