First pass to increase classad integers to 64 bits. #2472

Classad integers are now internally reprsented as type long long. New
methods have been added to get and set integer values as long and long
long. The soversion is bumped, but code that uses classads should only
need a recompile to use the new version.

Some work remains:
* Decide what to do when an integer larger than 32 bits needs to be
returned via the old interfaces? The options are truncate, cap, and
fail.
* Add units tests for 64-bit integers.
* Fix the random() classad function to handle 64-bit integers.
* Fix the list subscript operation to handle 64-bit integers.
* Improve the right-sift operation to not count to obscene values
and handle negative values.
The file in question is usually called a log file, not a debug file.
Remove XML diagnosis code used only by DAGman

===GT=== #2807
Introduce a helper class to split UserLog lists

===GT=== #2807
Let submit use recursive macros

===GT=== #2807

This has been suggested a lot.

This is  a partial solution to #406 and #2428
Make schedd understand new UserLog format

This is compatible with the old Userlog format, unless ';' is used as a
separator.  There is probably some system that I don't know about uses
semicolons as a regular part of the filename

The idea here is that if the UserLog is specified in the JobAd as

UserLog = "bob;bill"

then the schedd will write a two copies of each event: one into the
"bob" file and one into the "bill" file.

I think if the event log is enabled, we get 2 copies of each event in
the event log; this is a bad thing, but I have not tested it yet.

===GT=== #2807
Make shadow understand new UserLog format

This is compatible with the old Userlog format, unless ';' is used as a
separator.  There is probably some system that I don't know about uses
semicolons as a regular part of the filename

The idea here is that if the UserLog is specified in the JobAd as

UserLog = "bob;bill"

then the shadow will write a two copies of each event: one into the
"bob" file and one into the "bill" file.

I think if the event log is enabled, we get a copy of each event for
each userlog entry. This is a bad thing; I have not tested it yet.

===GT=== #2807
Use new macro capability in DAGman

DAGman now requests the schedd and shadow to write each event to the
default log, i.e., <DAG file>.nodes.log, along with whatever log is
specified by the user.

DAGman only looks in the default log for events.

DAGman only writes POST Script TERMINATE events to its default log, not
to the user log.

DAGman specifies that the default user log is in plain text format, not
XML format.

This allows the user to have his own templated UserLog file, as
requested in #2428.

This does not completely implement the solution specified in #2807, as
we still write to a log which is also being written to by the schedd and
shadow.  However, it does fix the fd-throttling issue in #659, as there
is only one userlog that condor_dagman watches for events.

===GT=== #2807
Fix tests affected by DAGman userlog changes

===GT=== #2807
Document DAGman userlog changes in manual

And in the version history.

===GT=== #2807
===VersionHistory===
fix bug in submit where RequestCpus may not be set into the job ad correctly. #2968
===VersionHistory:None===
Merge branch 'V7_8_0-branch' into V7_8-branch
Merge branch 'V7_8-branch'
Merge remote-tracking branch 'origin/master' into gittrac-2807
Update Globus external to 5.2.1. #2838

Even now that we dynamically link against Globus libraries, we continue
to have trouble with the Globus external when globus_xio tries to
dlopen() its plugins. dlopen() doesn't find libraries if LD_LIBRARY_PATH
isn't set.
Add Cpus attribute to schedd ad used for matching local jobs. #2968
Do not pass CONDOR_INHERIT to the user job when JOB_INHERITS_STARTER_ENVIRONMENT is true. #2970
Merge branch 'V7_8-branch'
Merge branch 'master' of /p/condor/repository/CONDOR_SRC
Have V7_8-branch manual announce itself as for version 7.8.1