[Bio] / FigKernelPackages / Tracer.pm Repository:
ViewVC logotype

Diff of /FigKernelPackages/Tracer.pm

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.66, Tue Sep 26 13:37:07 2006 UTC revision 1.73, Tue Oct 3 12:04:50 2006 UTC
# Line 19  Line 19 
19    
20      require Exporter;      require Exporter;
21      @ISA = ('Exporter');      @ISA = ('Exporter');
22      @EXPORT = qw(Trace T TSetup QTrace Confess Cluck Min Max Assert Open OpenDir TICK StandardSetup ScriptSetup ScriptFinish Insure ChDir);      @EXPORT = qw(Trace T TSetup QTrace Confess Cluck Min Max Assert Open OpenDir TICK StandardSetup EmergencyKey ETracing ScriptSetup ScriptFinish Insure ChDir Emergency);
23      @EXPORT_OK = qw(GetFile GetOptions Merge MergeOptions ParseCommand ParseRecord UnEscape Escape);      @EXPORT_OK = qw(GetFile GetOptions Merge MergeOptions ParseCommand ParseRecord UnEscape Escape);
24      use strict;      use strict;
25      use Carp qw(longmess croak);      use Carp qw(longmess croak);
# Line 37  Line 37 
37    
38  =head1 Tracing and Debugging Helpers  =head1 Tracing and Debugging Helpers
39    
40  =head2 Introduction  =head2 Tracing
41    
42  This package provides simple tracing for debugging and reporting purposes. To use it simply call the  This package provides simple tracing for debugging and reporting purposes. To use it simply call the
43  L</TSetup> method to set the options and call L</Trace> to write out trace messages. Each trace  L</TSetup> or L</ETracing> method to set the options and call L</Trace> to write out trace messages.
44  message has a I<trace level> and I<category> associated with it. In addition, the tracing package itself  L</TSetup> and L</ETracing> both establish a I<trace level> and a list of I<categories>. Similarly,
45  has a list of categories and a single trace level set by the B<TSetup> method. Only messages whose trace  each trace message has a I<trace level> and I<category> associated with it. Only messages whose trace
46  level is less than or equal to this package's trace level and whose category is activated will  level is less than or equal to the setup trace level and whose category is activated will
47  be written. Thus, a higher trace level on a message indicates that the message  be written. Thus, a higher trace level on a message indicates that the message
48  is less likely to be seen. A higher trace level passed to B<TSetup> means more trace messages will  is less likely to be seen, while a higher trace level passed to B<TSetup> means more trace messages will
49  appear. To generate a trace message, use the following syntax.  appear.
50    
51  C<< Trace($message) if T(errors => 4); >>  =head3 Putting Trace Messages in Your Code
52    
53    To generate a trace message, use the following syntax.
54    
55        Trace($message) if T(errors => 4);
56    
57  This statement will produce a trace message if the trace level is 4 or more and the C<errors>  This statement will produce a trace message if the trace level is 4 or more and the C<errors>
58  category is active. Note that the special category C<main> is always active, so  category is active. There is a special category C<main> that is always active, so
59    
60  C<< Trace($message) if T(main => 4); >>      Trace($message) if T(main => 4);
61    
62  will trace if the trace level is 4 or more.  will trace if the trace level is 4 or more.
63    
# Line 61  Line 65 
65  following call is made in the B<Sprout> package, it will appear if the C<Sprout> category is  following call is made in the B<Sprout> package, it will appear if the C<Sprout> category is
66  active and the trace level is 2 or more.  active and the trace level is 2 or more.
67    
68  C<< Trace($message) if T(2); >>      Trace($message) if T(2);
69    
70    In scripts, where no package name is available, the category defaults to C<main>.
71    
72    =head3 Custom Tracing
73    
74  To set up tracing, you call the L</TSetup> method. The method takes as input a trace level, a list  Many programs have customized tracing configured using the L</TSetup> method. This is no longer
75  of category names, and a set of options. The trace level and list of category names are  the preferred method, but a knowledge of how custom tracing works can make the more modern
76    L</Emergency Tracing> easier to understand.
77    
78    To set up custom tracing, you call the L</TSetup> method. The method takes as input a trace level,
79    a list of category names, and a destination. The trace level and list of category names are
80  specified as a space-delimited string. Thus  specified as a space-delimited string. Thus
81    
82  C<< TSetup('3 errors Sprout ERDB', 'HTML'); >>      TSetup('3 errors Sprout ERDB', 'TEXT');
83    
84  sets the trace level to 3, activates the C<errors>, C<Sprout>, and C<ERDB> categories, and  sets the trace level to 3, activates the C<errors>, C<Sprout>, and C<ERDB> categories, and
85  specifies that messages should be output as HTML paragraphs.  specifies that messages should be sent to the standard output.
86    
87  To turn on tracing for ALL categories, use an asterisk. The call below sets every category to  To turn on tracing for ALL categories, use an asterisk. The call below sets every category to
88  level 3 and writes the output to the standard error output. This sort of thing might be  level 3 and writes the output to the standard error output. This sort of thing might be
89  useful in a CGI environment.  useful in a CGI environment.
90    
91  C<< TSetup('3 *', 'WARN'); >>      TSetup('3 *', 'WARN');
92    
93  In addition to HTML and file output for trace messages, you can specify that the trace messages  In addition standard error and file output for trace messages, you can specify that the trace messages
94  be queued. The messages can then be retrieved by calling the L</QTrace> method. This approach  be queued. The messages can then be retrieved by calling the L</QTrace> method. This approach
95  is useful if you are building a web page. Instead of having the trace messages interspersed with  is useful if you are building a web page. Instead of having the trace messages interspersed with
96  the page output, they can be gathered together and displayed at the end of the page. This makes  the page output, they can be gathered together and displayed at the end of the page. This makes
97  it easier to debug page formatting problems.  it easier to debug page formatting problems.
98    
99  Finally, you can specify that all trace messages be emitted as warnings.  Finally, you can specify that all trace messages be emitted to a file, or the standard output and
100    a file at the same time. To trace to a file, specify the filename with an output character in front
101    of it.
102    
103        TSetup('4 SQL', ">$fileName");
104    
105    To trace to the standard output and a file at the same time, put a C<+> in front of the angle
106    bracket.
107    
108        TSetup('3 *', "+>$fileName");
109    
110  The flexibility of tracing makes it superior to simple use of directives like C<die> and C<warn>.  The flexibility of tracing makes it superior to simple use of directives like C<die> and C<warn>.
111  Tracer calls can be left in the code with minimal overhead and then turned on only when needed.  Tracer calls can be left in the code with minimal overhead and then turned on only when needed.
112  Thus, debugging information is available and easily retrieved even when the application is  Thus, debugging information is available and easily retrieved even when the application is
113  being used out in the field.  being used out in the field.
114    
115    =head3 Trace Levels
116    
117  There is no hard and fast rule on how to use trace levels. The following is therefore only  There is no hard and fast rule on how to use trace levels. The following is therefore only
118  a suggestion.  a suggestion.
119    
# Line 121  Line 144 
144    
145  =back  =back
146    
147    The format of trace messages is important because some utilities analyze trace files.
148    There are three fields-- the time stamp, the category name, and the text.
149    The time stamp is between square brackets and the category name between angle brackets.
150    After the category name there is a colon (C<:>) followed by the message text.
151    If the square brackets or angle brackets are missing, then the trace management
152    utilities assume that they are encountering a set of pre-formatted lines.
153    
154    Note, however, that this formatting is done automatically by the tracing functions. You
155    only need to know about it if you want to parse a trace file.
156    
157    =head3 Emergency Tracing
158    
159    Sometimes, you need a way for tracing to happen automatically without putting parameters
160    in a form or on the command line. Emergency tracing does this. You invoke emergency tracing
161    from the debug form, which is accessed from I<MySeedInstance>C</FIG/Html/SetPassword.html>.
162    Emergency tracing requires you specify a tracing key. For command-line tools, the key is
163    taken from the C<TRACING> environment variable. For web services, the key is taken from
164    a cookie. Either way, the key tells the tracing facility who you are, so that you control
165    the tracing in your environment without stepping on other users.
166    
167    The key can be anything you want. If you don't have a key, the C<SetPassword> page will
168    generate one for you.
169    
170    You can activate and de-activate emergency tracing from the debugging control panel, as
171    well as display the trace file itself.
172    
173    To enable emergency tracing in your code, call
174    
175        ETracing($cgi)
176    
177    from a web script and
178    
179        ETracing()
180    
181    from a command-line script.
182    
183    The web script will look for the tracing key in the cookies, and the command-line
184    script will look for it in the C<TRACING> environment variable. If you are
185    using the L</StandardScript> or L</StandardSetup> methods, emergency tracing
186    will be configured automatically.
187    
188    =head3 Debugging Control Panel
189    
190    The debugging control panel provides several tools to assist in development of
191    SEED and Sprout software. You access the debugging control panel from the URL
192    C</FIG/Html/SetPassword.html> in whichever seed instance you're using. (So,
193    for example, the panel access point for the development NMPDR system is
194    C<http://web-1.nmpdr.org/next/FIG/Html/SetPassword.html>. Contact Bruce to
195    find out what the password is. From this page, you can also specify a tracing
196    key. If you don't specify a key, one will be generated for you.
197    
198    =head4 Emergency Tracing Form
199    
200    At the bottom of the debugging control panel is a form that allows you to
201    specify a trace level and tracing categories. Special and common categories
202    are listed with check boxes. You can hold your mouse over a check box to see
203    what its category does. In general, however, a category name is the same as
204    the name of the package in which the trace message occurs.
205    
206    Additional categories can be entered in an input box, delimited by spaces or commas.
207    
208    The B<Activate> button turns on Emergency tracing at the level you specify with the
209    specified categories active. The B<Terminate> button turns tracing off. The
210    B<Show File> button displays the current contents of the trace file. The tracing
211    form at the bottom of the control panel is designed for emergency tracing, so it
212    will only affect programs that call L</ETracing>, L</StandardScript>,
213    or L</StandardSetup>.
214    
215    =head4 Script Form
216    
217    The top form of the debugging control panel allows you to enter a tiny script and
218    have the output generated in a formatted table. Certain object variables are
219    predefined in the script, including a FIG object (C<$fig>), a CGI object (C<$cgi>),
220    and-- if Sprout is active-- Sprout (C<$sprout>) and SFXlate (C<$sfx>) objects.
221    
222    The last line of the script must be a scalar, but it can be a reference to a hash,
223    a list, a list of lists, and various other combinations. If you select the appropriate
224    data type in the dropdown box, the output will be formatted accordingly. The form
225    also has controls for specifying tracing. These controls override any emergency
226    tracing in effect.
227    
228    =head4 Database Query Forms
229    
230    The forms between the script form and the emergency tracing form allow you to
231    make queries against the database. The FIG query form allows simple queries against
232    a single FIG table. The Sprout query form uses the B<GetAll> method to do a
233    multi-table query against the Sprout database. B<GetAll> is located in the B<ERDB>
234    package, and it takes five parameters.
235    
236        GetAll(\@objectNames, $filterClause, \@parameters, \@fields, $count);
237    
238    Each of the five parameters corresponds to a text box on the query form:
239    
240    =over 4
241    
242    =item Objects
243    
244    Comma-separated list containing the names of the entity and relationship objects to be retrieved.
245    
246    =item Filter
247    
248    WHERE/ORDER BY clause (without the WHERE) to be used to filter and sort the query. The WHERE clause can
249    be parameterized with parameter markers (C<?>). Each field used must be specified in the standard form
250    B<I<objectName>(I<fieldName>)> or B<$I<number>(I<fieldName>)> where I<fieldName> is the name of a
251    field, I<objectName> is the name of the entity or relationship object containing the field, and
252    I<number> is the 1-based position of the object in the object list. Any parameters
253    specified in the filter clause should be specified in the B<Params> field.
254    The fields in a filter clause can come from primary entity relations,
255    relationship relations, or secondary entity relations; however, all of the
256    entities and relationships involved must be included in the list of object names.
257    
258    =item Params
259    
260    List of the parameters to be substituted in for the parameters marks in the filter clause. This
261    is a comma-separated list without any quoting or escaping.
262    
263    =item fields
264    
265    Comma-separated list of the fields to be returned in each element of the list returned. Fields
266    are specified in the same manner as in the filter clause.
267    
268    =item count
269    
270    Maximum number of records to return. If omitted or 0, all available records will be returned.
271    
272    =back
273    
274    B<GetAll> automatically joins together the entities and relationships listed in the object
275    names. This simplifies the coding of the filter clause, but it means that some queries are
276    not possible, since they cannot be expressed in a linear sequence of joins. This is a limitation
277    that has yet to be addressed.
278    
279  =cut  =cut
280    
281  # Declare the configuration variables.  # Declare the configuration variables.
# Line 200  Line 355 
355          }          }
356          if ($target =~ m/^>[^>]/) {          if ($target =~ m/^>[^>]/) {
357              open TRACEFILE, $target;              open TRACEFILE, $target;
358              print TRACEFILE Now() . " Tracing initialized.\n";              print TRACEFILE "[" . Now() . "] <Tracer>: Tracing initialized.\n";
359              close TRACEFILE;              close TRACEFILE;
360              $Destination = ">$target";              $Destination = ">$target";
361          } else {          } else {
# Line 233  Line 388 
388      ["Sprout", "SproutLoad", "ERDB"]      ["Sprout", "SproutLoad", "ERDB"]
389    
390  This would cause trace messages in the specified three packages to appear in  This would cause trace messages in the specified three packages to appear in
391  the output. There are threer special tracing categories that are automatically  the output. There are two special tracing categories that are automatically
392  handled by this method. In other words, if you used L</TSetup> you would need  handled by this method. In other words, if you used L</TSetup> you would need
393  to include these categories manually, but if you use this method they are turned  to include these categories manually, but if you use this method they are turned
394  on automatically.  on automatically.
395    
396  =over 4  =over 4
397    
 =item FIG  
   
 Turns on trace messages inside the B<FIG> package.  
   
398  =item SQL  =item SQL
399    
400  Traces SQL commands and activity.  Traces SQL commands and activity.
# Line 308  Line 459 
459  In this case, C<register>, C<../xacts>, and C<IDs.tbl> are the positional  In this case, C<register>, C<../xacts>, and C<IDs.tbl> are the positional
460  parameters, and would find themselves in I<@parameters> after executing the  parameters, and would find themselves in I<@parameters> after executing the
461  above code fragment. The tracing would be set to level 2, and the categories  above code fragment. The tracing would be set to level 2, and the categories
462  would be C<FIG>, C<Tracer>, and <DocUtils>. C<FIG> and C<Tracer> are standard,  would be C<Tracer>, and <DocUtils>. C<Tracer> is standard,
463  and C<DocUtils> was included because it came in within the first parameter  and C<DocUtils> was included because it came in within the first parameter
464  to this method. The I<$options> hash would be  to this method. The I<$options> hash would be
465    
# Line 333  Line 484 
484  C<outBruce.log>, and the error output to C<errBruce.log>. This is designed to  C<outBruce.log>, and the error output to C<errBruce.log>. This is designed to
485  simplify starting a command in the background.  simplify starting a command in the background.
486    
487    The user name is also used as the tracing key for L</Emergency Tracing>.
488    Specifying a value of C<E> for the trace level causes emergency tracing to
489    be used instead of custom tracing. If the user name is not specified,
490    the tracing key is taken from the C<Tracing> environment variable. If there
491    is no value for that variable, the tracing key will be computed from the PID.
492    
493  Finally, if the special option C<-h> is specified, the option names will  Finally, if the special option C<-h> is specified, the option names will
494  be traced at level 0 and the program will exit without processing.  be traced at level 0 and the program will exit without processing.
495  This provides a limited help capability. For example, if the user enters  This provides a limited help capability. For example, if the user enters
# Line 342  Line 499 
499  he would see the following output.  he would see the following output.
500    
501      TransactFeatures [options] command transactionDirectory IDfile      TransactFeatures [options] command transactionDirectory IDfile
502          -trace    tracing level (default 2)          -trace    tracing level (default E)
503          -sql      trace SQL commands          -sql      trace SQL commands
504          -safe     use database transactions          -safe     use database transactions
505          -noAlias  do not expect aliases in CHANGE transactions          -noAlias  do not expect aliases in CHANGE transactions
# Line 357  Line 514 
514      { trace => [0, "tracing level (default 0)"],      { trace => [0, "tracing level (default 0)"],
515         ...         ...
516    
517  would set the default trace level to 0 instead of 2, while  would set the default trace level to 0 instead of E, while
518    
519      { trace => ["2-", "tracing level (default 2)"],      { trace => ["2-", "tracing level (default 2)"],
520         ...         ...
521    
522  would leave the default at 2, but trace only to the log file, not to the  would set the default to 2, but trace only to the log file, not to the
523  standard output.  standard output.
524    
525  The parameters to this method are as follows.  The parameters to this method are as follows.
# Line 409  Line 566 
566  sub StandardSetup {  sub StandardSetup {
567      # Get the parameters.      # Get the parameters.
568      my ($categories, $options, $parmHelp, @argv) = @_;      my ($categories, $options, $parmHelp, @argv) = @_;
569        # Get the default tracing key.
570        my $tkey = EmergencyKey();
571      # Add the tracing options.      # Add the tracing options.
572      if (! exists $options->{trace}) {      if (! exists $options->{trace}) {
573          $options->{trace} = [2, "tracing level"];          $options->{trace} = ['E', "tracing level (E for emergency tracing)"];
574      }      }
575      $options->{sql} = [0, "turn on SQL tracing"];      $options->{sql} = [0, "turn on SQL tracing"];
576      $options->{h} = [0, "display command-line options"];      $options->{h} = [0, "display command-line options"];
577      $options->{user} = [$$, "trace log file name suffix"];      $options->{user} = [$tkey, "tracing key"];
578      $options->{background} = [0, "spool standard and error output"];      $options->{background} = [0, "spool standard and error output"];
579      # Create a parsing hash from the options hash. The parsing hash      # Create a parsing hash from the options hash. The parsing hash
580      # contains the default values rather than the default value      # contains the default values rather than the default value
# Line 440  Line 599 
599          open STDOUT, ">$outFileName";          open STDOUT, ">$outFileName";
600          open STDERR, ">$errFileName";          open STDERR, ">$errFileName";
601      }      }
602      # Now we want to set up tracing. First, we need to know if SQL is to      # Now we want to set up tracing. First, we need to know if the user
603      # be traced.      # wants emergency tracing.
604        if ($retOptions->{trace} eq 'E') {
605            ETracing($retOptions->{user});
606        } else {
607            # Here the tracing is controlled from the command line.
608      my @cats = @{$categories};      my @cats = @{$categories};
609      if ($retOptions->{sql}) {      if ($retOptions->{sql}) {
610          push @cats, "SQL";          push @cats, "SQL";
611      }      }
612      # Add the default categories.      # Add the default categories.
613      push @cats, "Tracer", "FIG";          push @cats, "Tracer";
614      # Next, we create the category string by joining the categories.      # Next, we create the category string by joining the categories.
615      my $cats = join(" ", @cats);      my $cats = join(" ", @cats);
616      # Check to determine whether or not the caller wants to turn off tracing      # Check to determine whether or not the caller wants to turn off tracing
# Line 482  Line 645 
645      }      }
646      # Now set up the tracing.      # Now set up the tracing.
647      TSetup("$traceLevel $cats", $traceMode);      TSetup("$traceLevel $cats", $traceMode);
648        }
649      # Check for the "h" option. If it is specified, dump the command-line      # Check for the "h" option. If it is specified, dump the command-line
650      # options and exit the program.      # options and exit the program.
651      if ($retOptions->{h}) {      if ($retOptions->{h}) {
652          $0 =~ m#[/\\](\w+)(\.pl)?$#i;          $0 =~ m#[/\\](\w+)(\.pl)?$#i;
653          Trace("$1 [options] $parmHelp") if T(0);          print "$1 [options] $parmHelp\n";
654          for my $key (sort keys %{$options}) {          for my $key (sort keys %{$options}) {
655              my $name = Pad($key, $longestName, 0, ' ');              my $name = Pad($key, $longestName, 0, ' ');
656              my $desc = $options->{$key}->[1];              my $desc = $options->{$key}->[1];
657              if ($options->{$key}->[0]) {              if ($options->{$key}->[0]) {
658                  $desc .= " (default " . $options->{$key}->[0] . ")";                  $desc .= " (default " . $options->{$key}->[0] . ")";
659              }              }
660              Trace("  $name $desc") if T(0);              print "  $name $desc\n";
661          }          }
662          exit(0);          exit(0);
663      }      }
# Line 969  Line 1133 
1133      # Get the timestamp.      # Get the timestamp.
1134      my $timeStamp = Now();      my $timeStamp = Now();
1135      # Format the message. Note we strip off any line terminators at the end.      # Format the message. Note we strip off any line terminators at the end.
1136      my $formatted = "$timeStamp <$LastCategory>: " . Strip($message);      my $formatted = "[$timeStamp] <$LastCategory>: " . Strip($message);
1137      # Process according to the destination.      # Process according to the destination.
1138      if ($Destination eq "TEXT") {      if ($Destination eq "TEXT") {
1139          # Write the message to the standard output.          # Write the message to the standard output.
# Line 1720  Line 1884 
1884    
1885  C<< if (Tracer::DebugMode) { ...code... } >>  C<< if (Tracer::DebugMode) { ...code... } >>
1886    
1887  Return TRUE if debug mode has been turned on, else output an error  Return TRUE if debug mode has been turned on, else abort.
 page and return FALSE.  
1888    
1889  Certain CGI scripts are too dangerous to exist in the production  Certain CGI scripts are too dangerous to exist in the production
1890  environment. This method provides a simple way to prevent them  environment. This method provides a simple way to prevent them
1891  from working unless they are explicitly turned on by creating a password  from working unless they are explicitly turned on by creating a password
1892  cookie via the B<SetPassword> script.  If debugging mode  cookie via the B<SetPassword> script.  If debugging mode
1893  is not turned on, an error web page will be output directing the  is not turned on, an error will occur.
 user to enter in the correct password.  
1894    
1895  =cut  =cut
1896    
# Line 1741  Line 1903 
1903      if ($encrypted eq "252dec43280e0c0d6a75ffcec486e61d") {      if ($encrypted eq "252dec43280e0c0d6a75ffcec486e61d") {
1904          $retVal = 1;          $retVal = 1;
1905      } else {      } else {
1906          # Here debug mode is off, so we generate an error page.          # Here debug mode is off, so we generate an error.
1907          my $pageString = PageBuilder::Build("<<Html/ErrorPage.html", {}, "Html");          Confess("Cannot use this facility without logging in.");
         print $pageString;  
1908      }      }
1909      # Return the determination indicator.      # Return the determination indicator.
1910      return $retVal;      return $retVal;
# Line 1895  Line 2056 
2056    
2057  =head3 ScriptSetup  =head3 ScriptSetup
2058    
2059  C<< my ($query, $varHash) = ScriptSetup(); >>  C<< my ($cgi, $varHash) = ScriptSetup($noTrace); >>
2060    
2061  Perform standard tracing and debugging setup for scripts. The value returned is  Perform standard tracing and debugging setup for scripts. The value returned is
2062  the CGI object followed by a pre-built variable hash.  the CGI object followed by a pre-built variable hash.
2063    
2064  The C<Trace> query parameter is used to determine whether or not tracing is active and  The C<Trace> form parameter is used to determine whether or not tracing is active and
2065  which trace modules (other than C<Tracer> and C<FIG>) should be turned on. Specifying  which trace modules (other than C<Tracer> itself) should be turned on. Specifying
2066  the C<CGI> trace module will trace parameter and environment information. Parameters are  the C<CGI> trace module will trace parameter and environment information. Parameters are
2067  traced at level 3 and environment variables at level 4. At the end of the script, the  traced at level 3 and environment variables at level 4. To trace to a file instead of to
2068  client should call L</ScriptFinish> to output the web page.  the web page, set C<TF> to 1. At the end of the script, the client should call
2069    L</ScriptFinish> to output the web page.
2070    
2071    In some situations, it is not practical to invoke tracing via form parameters. For this
2072    situation, you can turn on emergency tracing from the debugging control panel.
2073    Tracing will then be turned on automatically for all programs that use the L</ETracing>
2074    method, which includes every program that uses this method or L</StandardSetup>.
2075    
2076    =over 4
2077    
2078    =item noTrace (optional)
2079    
2080    If specified, tracing will be suppressed. This is useful if the script wants to set up
2081    tracing manually.
2082    
2083    =item RETURN
2084    
2085    Returns a two-element list consisting of a CGI query object and a variable hash for
2086    the output page.
2087    
2088    =back
2089    
2090  =cut  =cut
2091    
2092  sub ScriptSetup {  sub ScriptSetup {
2093        # Get the parameters.
2094        my ($noTrace) = @_;
2095      # Get the CGI query object.      # Get the CGI query object.
2096      my $query = CGI->new();      my $cgi = CGI->new();
2097      # Check for tracing. Set it up if the user asked for it.      # Set up tracing if it's not suppressed.
2098      if ($query->param('Trace')) {      ETracing($cgi) unless $noTrace;
         # Set up tracing.  
         my $ttype = ($query->param('TF') ? ">$FIG_Config::temp/Trace$$.log" : "QUEUE");  
         TSetup($query->param('Trace') . " FIG Tracer", $ttype);  
         # Trace the parameter and environment data.  
         TraceParms($query);  
     } else {  
         # Here tracing is to be turned off. All we allow is errors traced into the  
         # error log.  
         TSetup("0", "WARN");  
     }  
2099      # Create the variable hash.      # Create the variable hash.
2100      my $varHash = { DebugData => '' };      my $varHash = { results => '' };
2101      # Return the query object and variable hash.      # Return the query object and variable hash.
2102      return ($query, $varHash);      return ($cgi, $varHash);
2103    }
2104    
2105    =head3 ETracing
2106    
2107    C<< ETracing($parameter); >>
2108    
2109    Set up emergency tracing. Emergency tracing is tracing that is turned
2110    on automatically for any program that calls this method. The emergency
2111    tracing parameters are stored in a a file identified by a tracing key.
2112    If this method is called with a CGI object, then the tracing key is
2113    taken from a cookie. If it is called with no parameters, then the tracing
2114    key is taken from an environment variable. If it is called with a string,
2115    the tracing key is that string.
2116    
2117    =over 4
2118    
2119    =item parameter
2120    
2121    A parameter from which the tracing key is computed. If it is a scalar,
2122    that scalar is used as the tracing key. If it is a CGI object, the
2123    tracing key is taken from the C<IP> cookie. If it is omitted, the
2124    tracing key is taken from the C<TRACING> environment variable. If it
2125    is a CGI object and emergency tracing is not on, the C<Trace> and
2126    C<TF> parameters will be used to determine the type of tracing.
2127    
2128    =back
2129    
2130    =cut
2131    
2132    sub ETracing {
2133        # Get the parameter.
2134        my ($parameter) = @_;
2135        # Check for CGI mode.
2136        my $cgi = (ref $parameter eq 'CGI' ? $parameter : undef);
2137        # Default to no tracing except errors.
2138        my ($tracing, $dest) = ("0", "WARN");
2139        # Check for emergency tracing.
2140        my $tkey = EmergencyKey($parameter);
2141        my $emergencyFile = EmergencyFileName($tkey);
2142        if (-e $emergencyFile) {
2143            # We have the file. Read in the data.
2144            my @tracing = GetFile($emergencyFile);
2145            # Pull off the time limit.
2146            my $expire = shift @tracing;
2147            # Convert it to seconds.
2148            $expire *= 3600;
2149            # Check the file data.
2150            my $stat = stat($emergencyFile);
2151            my ($now) = gettimeofday;
2152            if ($now - $stat->mtime > $expire) {
2153                # Delete the expired file.
2154                unlink $emergencyFile;
2155            } else {
2156                # Emergency tracing is on. Pull off the destination and
2157                # the trace level;
2158                $dest = shift @tracing;
2159                my $level = shift @tracing;
2160                # Convert the destination to a real tracing destination.
2161                # temp directory.
2162                $dest = EmergencyTracingDest($tkey, $dest);
2163                # Insure Tracer is specified.
2164                my %moduleHash = map { $_ => 1 } @tracing;
2165                $moduleHash{Tracer} = 1;
2166                # Set the trace parameter.
2167                $tracing = join(" ", $level, sort keys %moduleHash);
2168            }
2169        } elsif (defined $cgi) {
2170            # There's no emergency tracing, but we have a CGI object, so check
2171            # for tracing from the form parameters.
2172            if ($cgi->param('Trace')) {
2173                # Here the user has requested tracing via a form.
2174                $dest = ($cgi->param('TF') ? ">$FIG_Config::temp/Trace$$.log" : "QUEUE");
2175                $tracing = $cgi->param('Trace') . " Tracer";
2176            }
2177        }
2178        # Setup the tracing we've determined from all the stuff above.
2179        TSetup($tracing, $dest);
2180        # If we're a web script, trace the parameter and environment data.
2181        if (defined $cgi) {
2182            TraceParms($cgi);
2183        }
2184    }
2185    
2186    =head3 EmergencyFileName
2187    
2188    C<< my $fileName = Tracer::EmergencyFileName($tkey); >>
2189    
2190    Return the emergency tracing file name. This is the file that specifies
2191    the tracing information.
2192    
2193    =over 4
2194    
2195    =item tkey
2196    
2197    Tracing key for the current program.
2198    
2199    =item RETURN
2200    
2201    Returns the name of the file to contain the emergency tracing information.
2202    
2203    =back
2204    
2205    =cut
2206    
2207    sub EmergencyFileName {
2208        # Get the parameters.
2209        my ($tkey) = @_;
2210        # Compute the emergency tracing file name.
2211        return "$FIG_Config::temp/Emergency$tkey.txt";
2212  }  }
2213    
2214    =head3 EmergencyFileTarget
2215    
2216    C<< my $fileName = Tracer::EmergencyFileTarget($tkey); >>
2217    
2218    Return the emergency tracing target file name. This is the file that receives
2219    the tracing output for file-based tracing.
2220    
2221    =over 4
2222    
2223    =item tkey
2224    
2225    Tracing key for the current program.
2226    
2227    =item RETURN
2228    
2229    Returns the name of the file to contain the trace output.
2230    
2231    =back
2232    
2233    =cut
2234    
2235    sub EmergencyFileTarget {
2236        # Get the parameters.
2237        my ($tkey) = @_;
2238        # Compute the emergency tracing file name.
2239        return "$FIG_Config::temp/trace$tkey.log";
2240    }
2241    
2242    =head3 EmergencyTracingDest
2243    
2244    C<< my $dest = Tracer::EmergencyTracingDest($tkey, $myDest); >>
2245    
2246    This method converts an emergency tracing destination to a real
2247    tracing destination. The main difference is that if the
2248    destination is C<FILE> or C<APPEND>, we convert it to file
2249    output.
2250    
2251    =over 4
2252    
2253    =item tkey
2254    
2255    Tracing key for this environment.
2256    
2257    =item myDest
2258    
2259    Destination from the emergency tracing file.
2260    
2261    =item RETURN
2262    
2263    Returns a destination that can be passed into L</TSetup>.
2264    
2265    =back
2266    
2267    =cut
2268    
2269    sub EmergencyTracingDest {
2270        # Get the parameters.
2271        my ($tkey, $myDest) = @_;
2272        # Declare the return variable.
2273        my $retVal;
2274        # Process according to the destination value.
2275        if ($myDest eq 'FILE') {
2276            $retVal = ">" . EmergencyFileTarget($tkey);
2277        } elsif ($myDest eq 'APPEND') {
2278            $retVal = ">>" . EmergencyFileTarget($tkey);
2279        } else {
2280            $retVal = $myDest;
2281        }
2282        # Return the result.
2283        return $retVal;
2284    }
2285    
2286    =head3 Emergency
2287    
2288    C<< Emergency($key, $hours, $dest, $level, @modules); >>
2289    
2290    Turn on emergency tracing. This method can only be invoked over the web and is
2291    should not be called if debug mode is off. The caller specifies the duration of the
2292    emergency in hours, the desired tracing destination, the trace level,
2293    and a list of the trace modules to activate. For the length of the duration, when a
2294    program in an environment with the specified tracing key active invokes a Sprout
2295    CGI script, tracing will be turned on automatically. See L</TSetup> for more
2296    about tracing setup and L</ETracing> for more about emergency tracing.
2297    
2298    =over 4
2299    
2300    =item tkey
2301    
2302    The tracing key. This is used to identify the control file and the trace file.
2303    
2304    =item hours
2305    
2306    Number of hours to keep emergency tracing alive.
2307    
2308    =item dest
2309    
2310    Tracing destination. If no path information is specified for a file
2311    destination, it is put in the FIG temporary directory.
2312    
2313    =item level
2314    
2315    Tracing level. A higher level means more trace messages.
2316    
2317    =item modules
2318    
2319    A list of the tracing modules to activate.
2320    
2321    =back
2322    
2323    =cut
2324    
2325    sub Emergency {
2326        # Get the parameters.
2327        my ($tkey, $hours, $dest, $level, @modules) = @_;
2328        # Create the emergency file.
2329        my $specFile = EmergencyFileName($tkey);
2330        my $outHandle = Open(undef, ">$specFile");
2331        print $outHandle join("\n", $hours, $dest, $level, @modules, "");
2332    }
2333    
2334    =head3 EmergencyKey
2335    
2336    C<< my $tkey = EmergencyKey($parameter); >>
2337    
2338    Return the Key to be used for emergency tracing. This could be an IP address,
2339     a session ID, or a user name, depending on the environment.
2340    
2341    =over 4
2342    
2343    =item parameter
2344    
2345    Parameter defining the method for finding the tracing key. If it is a scalar,
2346    then it is presumed to be the tracing key itself. If it is a CGI object, then
2347    the tracing key is taken from the C<IP> cookie. Otherwise, the tracing key is
2348    taken from the C<TRACING> environment variable.
2349    
2350    =item RETURN
2351    
2352    Returns the key to be used for labels in emergency tracing.
2353    
2354    =back
2355    
2356    =cut
2357    
2358    sub EmergencyKey {
2359        # Get the parameters.
2360        my ($parameter) = @_;
2361        # Declare the return variable.
2362        my $retVal;
2363        # Determine the parameter type.
2364        if (! defined $parameter) {
2365            # Here we're supposed to check the environment.
2366            $retVal = $ENV{TRACING};
2367        } else {
2368            my $ptype = ref $parameter;
2369            if ($ptype eq 'CGI') {
2370                # Here we were invoked from a web page. Look for a cookie.
2371                $retVal = $parameter->cookie('IP');
2372            } elsif (! $ptype) {
2373                # Here the key was passed in.
2374                $retVal = $parameter;
2375            }
2376        }
2377        # If no luck finding a key, use the PID.
2378        if (! defined $retVal) {
2379            $retVal = $$;
2380        }
2381        # Return the result.
2382        return $retVal;
2383    }
2384    
2385    
2386  =head3 TraceParms  =head3 TraceParms
2387    
2388  C<< Tracer::TraceParms($query); >>  C<< Tracer::TraceParms($cgi); >>
2389    
2390  Trace the CGI parameters at trace level CGI => 3 and the environment variables  Trace the CGI parameters at trace level CGI => 3 and the environment variables
2391  at level CGI => 4.  at level CGI => 4.
2392    
2393  =over 4  =over 4
2394    
2395  =item query  =item cgi
2396    
2397  CGI query object containing the parameters to trace.  CGI query object containing the parameters to trace.
2398    
# Line 1948  Line 2402 
2402    
2403  sub TraceParms {  sub TraceParms {
2404      # Get the parameters.      # Get the parameters.
2405      my ($query) = @_;      my ($cgi) = @_;
2406      if (T(CGI => 3)) {      if (T(CGI => 3)) {
2407          # Here we want to trace the parameter data.          # Here we want to trace the parameter data.
2408          my @names = $query->param;          my @names = $cgi->param;
2409          for my $parmName (sort @names) {          for my $parmName (sort @names) {
2410              # Note we skip "Trace", which is for our use only.              # Note we skip the Trace parameters, which are for our use only.
2411              if ($parmName ne 'Trace') {              if ($parmName ne 'Trace' && $parmName ne 'TF') {
2412                  my @values = $query->param($parmName);                  my @values = $cgi->param($parmName);
2413                  Trace("CGI: $parmName = " . join(", ", @values));                  Trace("CGI: $parmName = " . join(", ", @values));
2414              }              }
2415          }          }
2416            # Display the request method.
2417            my $method = $cgi->request_method();
2418            Trace("Method: $method");
2419      }      }
2420      if (T(CGI => 4)) {      if (T(CGI => 4)) {
2421          # Here we want the environment data too.          # Here we want the environment data too.
# Line 1992  Line 2449 
2449      use FIG;      use FIG;
2450      # ... more uses ...      # ... more uses ...
2451    
2452      my ($query, $varHash) = ScriptSetup();      my ($cgi, $varHash) = ScriptSetup();
2453      eval {      eval {
2454          # ... get data from $query, put it in $varHash ...          # ... get data from $cgi, put it in $varHash ...
2455      };      };
2456      if ($@) {      if ($@) {
2457          Trace("Script Error: $@") if T(0);          Trace("Script Error: $@") if T(0);
# Line 2042  Line 2499 
2499          $outputString = $webData;          $outputString = $webData;
2500      }      }
2501      # Check for trace messages.      # Check for trace messages.
2502      if ($Destination eq "QUEUE") {      if ($Destination ne "NONE" && $TraceLevel > 0) {
2503          # We have trace messages, so we want to put them at the end of the body. This          # We have trace messages, so we want to put them at the end of the body. This
2504          # is either at the end of the whole string or at the beginning of the BODY          # is either at the end of the whole string or at the beginning of the BODY
2505          # end-tag.          # end-tag.
# Line 2050  Line 2507 
2507          if ($outputString =~ m#</body>#gi) {          if ($outputString =~ m#</body>#gi) {
2508              $pos = (pos $outputString) - 7;              $pos = (pos $outputString) - 7;
2509          }          }
2510          substr $outputString, $pos, 0, QTrace('Html');          # If the trace messages were queued, we unroll them. Otherwise, we display the
2511            # destination.
2512            my $traceHtml;
2513            if ($Destination eq "QUEUE") {
2514                $traceHtml = QTrace('Html');
2515            } elsif ($Destination =~ /^>>(.+)$/) {
2516                # Here the tracing output it to a file. We code it as a hyperlink so the user
2517                # can copy the file name into the clipboard easily.
2518                my $actualDest = $1;
2519                $traceHtml = "<p>Tracing output to $actualDest.</p>\n";
2520            } else {
2521                # Here we have one of the special destinations.
2522                $traceHtml = "<P>Tracing output type is $Destination.</p>\n";
2523            }
2524            substr $outputString, $pos, 0, $traceHtml;
2525      }      }
2526      # Write the output string.      # Write the output string.
2527      print $outputString;      print $outputString;

Legend:
Removed from v.1.66  
changed lines
  Added in v.1.73

MCS Webmaster
ViewVC Help
Powered by ViewVC 1.0.3