Installation Instructions

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

unlimited permission to copy, distribute and modify it.

Basic Installation

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

   The `configure' shell script attempts to guess correct values for

various system-dependent variables used during compilation.  It uses

those values to create a `Makefile' in each directory of the package.

It may also create one or more `.h' files containing system-dependent

definitions.  Finally, it creates a shell script `config.status' that

you can run in the future to recreate the current configuration, and a

file `config.log' containing compiler output (useful mainly for

debugging `configure').

   It can also use an optional file (typically called `config.cache'

and enabled with `--cache-file=config.cache' or simply `-C') that saves

disabled by default to prevent problems with accidental use of stale

   If you need to do unusual things to compile the package, please try

to figure out how `configure' could check whether to do them, and mail

diffs or instructions to the address given in the `README' so they can

be considered for the next release.  If you are using the cache, and at

some point `config.cache' contains results you don't want to keep, you

may remove or edit it.

   The file `configure.ac' (or `configure.in') is used to create

The simplest way to compile this package is:

  1. `cd' to the directory containing the package's source code and type

  2. Type `make' to compile the package.

  3. Optionally, type `make check' to run any self-tests that come with

     the package.

     a different kind of computer), type `make distclean'.  There is

     also a `make maintainer-clean' target, but that is intended mainly

     for the package's developers.  If you use it, you may have to get

     all sorts of other programs in order to regenerate files that came

     with the distribution.

Compilers and Options

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

   You can give `configure' initial values for configuration parameters

by setting variables in the command line or in the environment.  Here

is an example:

   *Note Defining Variables::, for more details.

Compiling For Multiple Architectures

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

same time, by placing the object files for each architecture in their

directory where you want the object files and executables to go and run

the `configure' script.  `configure' automatically checks for the

source code in the directory that `configure' is in and in `..'.

Installation Names

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

`/usr/local/bin', include files under `/usr/local/include', etc.  You

can specify an installation prefix other than `/usr/local' by giving

`configure' the option `--prefix=PREFIX'.

   You can specify separate installation prefixes for

architecture-specific files and architecture-independent files.  If you

with an extra prefix or suffix on their names by giving `configure' the

option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.

Optional Features

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

`configure', where FEATURE indicates an optional part of the package.

They may also pay attention to `--with-PACKAGE' options, where PACKAGE

is something like `gnu-as' or `x' (for the X Window System).  The

`README' should mention any `--enable-' and `--with-' options that the

package recognizes.

   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.

Specifying the System Type

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

`--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

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

eventually be run) with `--host=TYPE'.

Sharing Defaults

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

`configure' looks for `PREFIX/share/config.site' if it exists, then

`PREFIX/etc/config.site' if it exists.  Or, you can set the

`CONFIG_SITE' environment variable to the location of the site script.

A warning: not all `configure' scripts look for a site script.

Defining Variables

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

environment passed to `configure'.  However, some packages may run

configure again during the build, and the customized values of these

variables may be lost.  In order to avoid this problem, you should set

them in the `configure' command line, using `VAR=value'.  For example:

     ./configure CC=/usr/local2/bin/gcc

causes the specified `gcc' to be used as the C compiler (unless it is

`configure' Invocation

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

`--help'

`-h'

`--version'

`-V'

     Print the version of Autoconf used to generate the `configure'

     script, and exit.

     messages will still be shown).

`--srcdir=DIR'

     Look for the package's source code in directory DIR.  Usually

     `configure' can determine that directory automatically.

`configure' also accepts some other, not widely useful, options.  Run

`configure --help' for more details.

#include <malloc.h>

#include <stdio.h>

#include <stdlib.h>

#include <string.h>

#include <unistd.h>

#include <libxml/xmlmemory.h>

#include <libxml/parser.h>

#include <libxml/tree.h>

#include <libxml/encoding.h>

#include <libxml/xmlwriter.h>

int deleteUser(struct user *user_ptr)

{

	free(user_ptr->username);

	memset(user_ptr, '\0', sizeof(struct user));

	return 1;

}

int createUser(struct user *user_ptr, char *nameOfUser)

{

	// clear old memory

	memset(user_ptr, '\0', sizeof(struct user));

	user_ptr->username = nameOfUser;

	user_ptr->render_power = 0;

	user_ptr->last_job = 0;

	return 1;

}

// places the new user at position index in the array, moves other users if it needs to

int placeUser(int index, char *nameOfUser)

{

	int higher;

	int lower;

	// I shift data in the array to create an open the space where the user should be added

	// but first I figure out which way is the shortest

	if(user_mgr_info.user_array[index].username != 0)

	{

		higher = index + 1;

		lower = index - 1;

		while(user_mgr_info.user_array[lower].username != 0)

			lower--;

		// here the data is shifted to open up a space

		if(index - lower < higher - index)

				memcpy(&user_mgr_info.user_array[lower], &user_mgr_info.user_array[lower + 1], sizeof(struct user));

		else

				memcpy(&user_mgr_info.user_array[higher], &user_mgr_info.user_array[higher - 1], sizeof(struct user));

	}

	// add the user to the array

	createUser(&user_mgr_info.user_array[index], nameOfUser);

	return 1;

}

int addUser(char *nameOfUser)

{

	int high;

		{

			fprintf(stderr, "user already exists");

			return 0;

		}

	}

	return 0;

}

int initialize_users()

{

}

/********************************** XMLness *****************************/

int backup_list_XML()

{

	xmlTextWriterPtr writer;

	int counter;

	writer = xmlNewTextWriterFilename("user_list.xml", 0);

	xmlTextWriterStartDocument(writer, NULL, "utf-8", NULL);

	// create root element user_list

	xmlTextWriterStartElement(writer, (xmlChar*)"user_list");

	for(counter = 0; counter < user_mgr_info.user_array_size; counter++)

	{

		if(user_mgr_info.user_array[counter].username != 0)

		{

			xmlTextWriterStartElement(writer, (xmlChar*)"user");

			xmlTextWriterWriteAttribute(writer, (xmlChar*)"name", (xmlChar*)user_mgr_info.user_array[counter].username);

			_distren_asprintf(&tmp, "%d", user_mgr_info.user_array[counter].last_job);

			xmlTextWriterWriteAttribute(writer, (xmlChar*)"last_job", (xmlChar*)tmp);

			xmlTextWriterEndElement(writer);

		}

	}

	return 0;

}

{

	char *username;

	int render_power;

	int last_job;

};

#endif