jablonka.czprosek.czf

hotsanic

Subversion Repositories:
[/] [trunk/] [var/] [log/] [HotSaNIC.log] - Diff between revs 27 and 29

Show entire file Ignore whitespace

Rev 27 Rev 29
Line 1... Line 1...
Use of uninitialized value $xs in printf at ./diagrams.pl line 812 (#1)  
   
  ----------------------------------------
  1616107890: archiver successfully forked into background and running on PID 4074
  1616107890 Initializing modules...
  1616107890 END Initializing modules...
  --------------------------------------------------
   
   
  starting module: "part"
  PART: Operating system "linux" not supported!
  PART: Falling back to "default"
  part running on PID 4078
   
   
  starting module: "ping"
  ping running on PID 4081
   
   
  starting module: "system"
  system running on PID 4085
   
   
  starting module: "temp"
  temp running on PID 4088
   
   
  starting module: "traffic"
  traffic running on PID 4097
   
   
  starting module: "wireless"
  wireless running on PID 4100
   
  Use of uninitialized value $HotSaNICmod::OSdep::memfre in subtraction (-) at
  ./platform/linux.pm line 232 (#1)
(W uninitialized) An undefined value was used as if it were already (W uninitialized) An undefined value was used as if it were already
defined. It was interpreted as a "" or a 0, but maybe it was a mistake. defined. It was interpreted as a "" or a 0, but maybe it was a mistake.
To suppress this warning assign a defined value to your variables. To suppress this warning assign a defined value to your variables.
   
To help you figure out what was undefined, perl will try to tell you To help you figure out what was undefined, perl will try to tell you
Line 11... Line 46...
literally in your program. For example, "that $foo" is usually literally in your program. For example, "that $foo" is usually
optimized into "that " . $foo, and the warning will refer to the optimized into "that " . $foo, and the warning will refer to the
concatenation (.) operator, even though there is no . in concatenation (.) operator, even though there is no . in
your program. your program.
   
Use of uninitialized value $ys in printf at ./diagrams.pl line 812 (#1) Use of uninitialized value $HotSaNICmod::OSdep::memtot in subtraction (-) at
Use of uninitialized value $xs in printf at ./diagrams.pl line 812 (#1) ./platform/linux.pm line 232 (#1)
  Use of uninitialized value $HotSaNICmod::OSdep::membuf in subtraction (-) at
  ./platform/linux.pm line 232 (#1)
  Use of uninitialized value $HotSaNICmod::OSdep::memcac in subtraction (-) at
  ./platform/linux.pm line 232 (#1)
  Use of uninitialized value $HotSaNICmod::OSdep::memfre in concatenation (.) or
  string at ./platform/linux.pm line 234 (#1)
  Use of uninitialized value $HotSaNICmod::OSdep::membuf in concatenation (.) or
  string at ./platform/linux.pm line 234 (#1)
  Use of uninitialized value $HotSaNICmod::OSdep::memcac in concatenation (.) or
  string at ./platform/linux.pm line 234 (#1)
  Use of uninitialized value $HotSaNICmod::OSdep::swpfre in concatenation (.) or
  string at ./platform/linux.pm line 234 (#1)
  Use of uninitialized value $HotSaNICmod::OSdep::swpuse in concatenation (.) or
  string at ./platform/linux.pm line 234 (#1)
  part running on PID 4078
   
  ping running on PID 4081
   
  system running on PID 4085
   
  temp running on PID 4088
   
  traffic running on PID 4097
   
  wireless running on PID 4100
   
  1616108021Stopping all running modules.
  1616108021Daemon exiting normally.
  PID-file removed.
   
   
  ----------------------------------------
  1616108022: archiver successfully forked into background and running on PID 4814
  1616108022 Initializing modules...
  1616108022 END Initializing modules...
  --------------------------------------------------
   
   
  starting module: "part"
  PART: Operating system "linux" not supported!
  PART: Falling back to "default"
  part running on PID 4818
   
   
  starting module: "ping"
  ping running on PID 4821
   
   
  starting module: "system"
  system running on PID 4825
   
   
  starting module: "temp"
  temp running on PID 4828
   
   
  starting module: "traffic"
  traffic running on PID 4832
   
   
  starting module: "wireless"
  wireless running on PID 4835
   
  Use of uninitialized value $HotSaNICmod::OSdep::memfre in subtraction (-) at
  ./platform/linux.pm line 232 (#1)
(W uninitialized) An undefined value was used as if it were already (W uninitialized) An undefined value was used as if it were already
defined. It was interpreted as a "" or a 0, but maybe it was a mistake. defined. It was interpreted as a "" or a 0, but maybe it was a mistake.
To suppress this warning assign a defined value to your variables. To suppress this warning assign a defined value to your variables.
   
To help you figure out what was undefined, perl will try to tell you To help you figure out what was undefined, perl will try to tell you
Line 27... Line 127...
literally in your program. For example, "that $foo" is usually literally in your program. For example, "that $foo" is usually
optimized into "that " . $foo, and the warning will refer to the optimized into "that " . $foo, and the warning will refer to the
concatenation (.) operator, even though there is no . in concatenation (.) operator, even though there is no . in
your program. your program.
   
Use of uninitialized value $ys in printf at ./diagrams.pl line 812 (#1) Use of uninitialized value $HotSaNICmod::OSdep::memtot in subtraction (-) at
Use of uninitialized value $xs in printf at ./diagrams.pl line 812 (#1) ./platform/linux.pm line 232 (#1)
(W uninitialized) An undefined value was used as if it were already Use of uninitialized value $HotSaNICmod::OSdep::membuf in subtraction (-) at
defined. It was interpreted as a "" or a 0, but maybe it was a mistake. ./platform/linux.pm line 232 (#1)
To suppress this warning assign a defined value to your variables. Use of uninitialized value $HotSaNICmod::OSdep::memcac in subtraction (-) at
  ./platform/linux.pm line 232 (#1)
To help you figure out what was undefined, perl will try to tell you Use of uninitialized value $HotSaNICmod::OSdep::memfre in concatenation (.) or
the name of the variable (if any) that was undefined. In some cases string at ./platform/linux.pm line 234 (#1)
it cannot do this, so it also tells you what operation you used the Use of uninitialized value $HotSaNICmod::OSdep::membuf in concatenation (.) or
undefined value in. Note, however, that perl optimizes your program string at ./platform/linux.pm line 234 (#1)
anid the operation displayed in the warning may not necessarily appear Use of uninitialized value $HotSaNICmod::OSdep::memcac in concatenation (.) or
literally in your program. For example, "that $foo" is usually string at ./platform/linux.pm line 234 (#1)
optimized into "that " . $foo, and the warning will refer to the Use of uninitialized value $HotSaNICmod::OSdep::swpfre in concatenation (.) or
concatenation (.) operator, even though there is no . in string at ./platform/linux.pm line 234 (#1)
your program. Use of uninitialized value $HotSaNICmod::OSdep::swpuse in concatenation (.) or
  string at ./platform/linux.pm line 234 (#1)
Use of uninitialized value $ys in printf at ./diagrams.pl line 812 (#1) 1616108023 WIRELESS: setting up database zlebra-krive-kritozle.rrd for values [0..U]
Use of uninitialized value $xs in printf at ./diagrams.pl line 812 (#1) 1616108023 WIRELESS: setting up database zlebra-krive-zletokri.rrd for values [0..U]
(W uninitialized) An undefined value was used as if it were already part running on PID 4818
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.  
To suppress this warning assign a defined value to your variables. ping running on PID 4821
   
To help you figure out what was undefined, perl will try to tell you system running on PID 4825
the name of the variable (if any) that was undefined. In some cases  
it cannot do this, so it also tells you what operation you used the temp running on PID 4828
undefined value in. Note, however, that perl optimizes your program  
anid the operation displayed in the warning may not necessarily appear traffic running on PID 4832
literally in your program. For example, "that $foo" is usually  
optimized into "that " . $foo, and the warning will refer to the wireless running on PID 4835
concatenation (.) operator, even though there is no . in  
your program. 1616108170Stopping all running modules.
  1616108170Daemon exiting normally.
Use of uninitialized value $ys in printf at ./diagrams.pl line 812 (#1) PID-file removed.
Use of uninitialized value $xs in printf at ./diagrams.pl line 812 (#1)  
(W uninitialized) An undefined value was used as if it were already  
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.  
To suppress this warning assign a defined value to your variables.  
   
To help you figure out what was undefined, perl will try to tell you  
the name of the variable (if any) that was undefined. In some cases  
it cannot do this, so it also tells you what operation you used the  
undefined value in. Note, however, that perl optimizes your program  
anid the operation displayed in the warning may not necessarily appear  
literally in your program. For example, "that $foo" is usually  
optimized into "that " . $foo, and the warning will refer to the  
concatenation (.) operator, even though there is no . in  
your program.  
   
Use of uninitialized value $ys in printf at ./diagrams.pl line 812 (#1)  
Use of uninitialized value $xs in printf at ./diagrams.pl line 812 (#1)  
(W uninitialized) An undefined value was used as if it were already  
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.  
To suppress this warning assign a defined value to your variables.  
   
To help you figure out what was undefined, perl will try to tell you  
the name of the variable (if any) that was undefined. In some cases  
it cannot do this, so it also tells you what operation you used the  
undefined value in. Note, however, that perl optimizes your program  
anid the operation displayed in the warning may not necessarily appear  
literally in your program. For example, "that $foo" is usually  
optimized into "that " . $foo, and the warning will refer to the  
concatenation (.) operator, even though there is no . in  
your program.  
   
Use of uninitialized value $ys in printf at ./diagrams.pl line 812 (#1)  
Use of uninitialized value $xs in printf at ./diagrams.pl line 812 (#1)  
(W uninitialized) An undefined value was used as if it were already  
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.  
To suppress this warning assign a defined value to your variables.  
   
To help you figure out what was undefined, perl will try to tell you  
the name of the variable (if any) that was undefined. In some cases  
it cannot do this, so it also tells you what operation you used the  
undefined value in. Note, however, that perl optimizes your program  
anid the operation displayed in the warning may not necessarily appear  
literally in your program. For example, "that $foo" is usually  
optimized into "that " . $foo, and the warning will refer to the  
concatenation (.) operator, even though there is no . in  
your program.  
   
Use of uninitialized value $ys in printf at ./diagrams.pl line 812 (#1)  
Use of uninitialized value $xs in printf at ./diagrams.pl line 812 (#1)  
(W uninitialized) An undefined value was used as if it were already  
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.  
To suppress this warning assign a defined value to your variables.  
   
To help you figure out what was undefined, perl will try to tell you  
the name of the variable (if any) that was undefined. In some cases  
it cannot do this, so it also tells you what operation you used the  
undefined value in. Note, however, that perl optimizes your program  
anid the operation displayed in the warning may not necessarily appear  
literally in your program. For example, "that $foo" is usually  
optimized into "that " . $foo, and the warning will refer to the  
concatenation (.) operator, even though there is no . in  
your program.  
   
Use of uninitialized value $ys in printf at ./diagrams.pl line 812 (#1)  
Use of uninitialized value $xs in printf at ./diagrams.pl line 812 (#1)  
(W uninitialized) An undefined value was used as if it were already  
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.  
To suppress this warning assign a defined value to your variables.  
   
To help you figure out what was undefined, perl will try to tell you  
the name of the variable (if any) that was undefined. In some cases  
it cannot do this, so it also tells you what operation you used the  
undefined value in. Note, however, that perl optimizes your program  
anid the operation displayed in the warning may not necessarily appear  
literally in your program. For example, "that $foo" is usually  
optimized into "that " . $foo, and the warning will refer to the  
concatenation (.) operator, even though there is no . in  
your program.  
   
Use of uninitialized value $ys in printf at ./diagrams.pl line 812 (#1)  
Use of uninitialized value $xs in printf at ./diagrams.pl line 812 (#1)  
(W uninitialized) An undefined value was used as if it were already  
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.  
To suppress this warning assign a defined value to your variables.  
   
To help you figure out what was undefined, perl will try to tell you  
the name of the variable (if any) that was undefined. In some cases  
it cannot do this, so it also tells you what operation you used the  
undefined value in. Note, however, that perl optimizes your program  
anid the operation displayed in the warning may not necessarily appear  
literally in your program. For example, "that $foo" is usually  
optimized into "that " . $foo, and the warning will refer to the  
concatenation (.) operator, even though there is no . in  
your program.  
   
Use of uninitialized value $ys in printf at ./diagrams.pl line 812 (#1)  
Use of uninitialized value $xs in printf at ./diagrams.pl line 812 (#1)  
(W uninitialized) An undefined value was used as if it were already  
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.  
To suppress this warning assign a defined value to your variables.  
   
To help you figure out what was undefined, perl will try to tell you  
the name of the variable (if any) that was undefined. In some cases  
it cannot do this, so it also tells you what operation you used the  
undefined value in. Note, however, that perl optimizes your program  
anid the operation displayed in the warning may not necessarily appear  
literally in your program. For example, "that $foo" is usually  
optimized into "that " . $foo, and the warning will refer to the  
concatenation (.) operator, even though there is no . in  
your program.  
   
Use of uninitialized value $ys in printf at ./diagrams.pl line 812 (#1)  
Use of uninitialized value $xs in printf at ./diagrams.pl line 812 (#1)  
(W uninitialized) An undefined value was used as if it were already  
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.  
To suppress this warning assign a defined value to your variables.  
   
To help you figure out what was undefined, perl will try to tell you  
the name of the variable (if any) that was undefined. In some cases  
it cannot do this, so it also tells you what operation you used the  
undefined value in. Note, however, that perl optimizes your program  
anid the operation displayed in the warning may not necessarily appear  
literally in your program. For example, "that $foo" is usually  
optimized into "that " . $foo, and the warning will refer to the  
concatenation (.) operator, even though there is no . in  
your program.  
   
Use of uninitialized value $ys in printf at ./diagrams.pl line 812 (#1)  
Use of uninitialized value $xs in printf at ./diagrams.pl line 812 (#1)  
(W uninitialized) An undefined value was used as if it were already  
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.  
To suppress this warning assign a defined value to your variables.  
   
To help you figure out what was undefined, perl will try to tell you  
the name of the variable (if any) that was undefined. In some cases  
it cannot do this, so it also tells you what operation you used the  
undefined value in. Note, however, that perl optimizes your program  
anid the operation displayed in the warning may not necessarily appear  
literally in your program. For example, "that $foo" is usually  
optimized into "that " . $foo, and the warning will refer to the  
concatenation (.) operator, even though there is no . in  
your program.  
   
Use of uninitialized value $ys in printf at ./diagrams.pl line 812 (#1)  
Use of uninitialized value $xs in printf at ./diagrams.pl line 812 (#1)  
(W uninitialized) An undefined value was used as if it were already  
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.  
To suppress this warning assign a defined value to your variables.  
   
To help you figure out what was undefined, perl will try to tell you  
the name of the variable (if any) that was undefined. In some cases  
it cannot do this, so it also tells you what operation you used the  
undefined value in. Note, however, that perl optimizes your program  
anid the operation displayed in the warning may not necessarily appear  
literally in your program. For example, "that $foo" is usually  
optimized into "that " . $foo, and the warning will refer to the  
concatenation (.) operator, even though there is no . in  
your program.  
   
Use of uninitialized value $ys in printf at ./diagrams.pl line 812 (#1)  
Use of uninitialized value $xs in printf at ./diagrams.pl line 812 (#1)  
(W uninitialized) An undefined value was used as if it were already  
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.  
To suppress this warning assign a defined value to your variables.  
   
To help you figure out what was undefined, perl will try to tell you  
the name of the variable (if any) that was undefined. In some cases  
it cannot do this, so it also tells you what operation you used the  
undefined value in. Note, however, that perl optimizes your program  
anid the operation displayed in the warning may not necessarily appear  
literally in your program. For example, "that $foo" is usually  
optimized into "that " . $foo, and the warning will refer to the  
concatenation (.) operator, even though there is no . in  
your program.  
   
Use of uninitialized value $ys in printf at ./diagrams.pl line 812 (#1)  
Use of uninitialized value $xs in printf at ./diagrams.pl line 812 (#1)  
(W uninitialized) An undefined value was used as if it were already  
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.  
To suppress this warning assign a defined value to your variables.  
   
To help you figure out what was undefined, perl will try to tell you  
the name of the variable (if any) that was undefined. In some cases  
it cannot do this, so it also tells you what operation you used the  
undefined value in. Note, however, that perl optimizes your program  
anid the operation displayed in the warning may not necessarily appear  
literally in your program. For example, "that $foo" is usually  
optimized into "that " . $foo, and the warning will refer to the  
concatenation (.) operator, even though there is no . in  
your program.  
   
Use of uninitialized value $ys in printf at ./diagrams.pl line 812 (#1)  
Use of uninitialized value $xs in printf at ./diagrams.pl line 812 (#1)  
(W uninitialized) An undefined value was used as if it were already  
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.  
To suppress this warning assign a defined value to your variables.  
   
To help you figure out what was undefined, perl will try to tell you  
the name of the variable (if any) that was undefined. In some cases  
it cannot do this, so it also tells you what operation you used the  
undefined value in. Note, however, that perl optimizes your program  
anid the operation displayed in the warning may not necessarily appear  
literally in your program. For example, "that $foo" is usually  
optimized into "that " . $foo, and the warning will refer to the  
concatenation (.) operator, even though there is no . in  
your program.  
   
Use of uninitialized value $ys in printf at ./diagrams.pl line 812 (#1)  
Use of uninitialized value $xs in printf at ./diagrams.pl line 812 (#1)  
(W uninitialized) An undefined value was used as if it were already  
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.  
To suppress this warning assign a defined value to your variables.  
   
To help you figure out what was undefined, perl will try to tell you  
the name of the variable (if any) that was undefined. In some cases  
it cannot do this, so it also tells you what operation you used the  
undefined value in. Note, however, that perl optimizes your program  
anid the operation displayed in the warning may not necessarily appear  
literally in your program. For example, "that $foo" is usually  
optimized into "that " . $foo, and the warning will refer to the  
concatenation (.) operator, even though there is no . in  
your program.  
   
Use of uninitialized value $ys in printf at ./diagrams.pl line 812 (#1)  
Use of uninitialized value $xs in printf at ./diagrams.pl line 812 (#1)  
(W uninitialized) An undefined value was used as if it were already  
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.  
To suppress this warning assign a defined value to your variables.  
   
To help you figure out what was undefined, perl will try to tell you  
the name of the variable (if any) that was undefined. In some cases  
it cannot do this, so it also tells you what operation you used the  
undefined value in. Note, however, that perl optimizes your program  
anid the operation displayed in the warning may not necessarily appear  
literally in your program. For example, "that $foo" is usually  
optimized into "that " . $foo, and the warning will refer to the  
concatenation (.) operator, even though there is no . in  
your program.  
   
Use of uninitialized value $ys in printf at ./diagrams.pl line 812 (#1)  
Use of uninitialized value $xs in printf at ./diagrams.pl line 812 (#1)  
(W uninitialized) An undefined value was used as if it were already  
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.  
To suppress this warning assign a defined value to your variables.  
   
To help you figure out what was undefined, perl will try to tell you  
the name of the variable (if any) that was undefined. In some cases  
it cannot do this, so it also tells you what operation you used the  
undefined value in. Note, however, that perl optimizes your program  
anid the operation displayed in the warning may not necessarily appear  
literally in your program. For example, "that $foo" is usually  
optimized into "that " . $foo, and the warning will refer to the  
concatenation (.) operator, even though there is no . in  
your program.  
   
Use of uninitialized value $ys in printf at ./diagrams.pl line 812 (#1)  
Use of uninitialized value $xs in printf at ./diagrams.pl line 812 (#1)  
(W uninitialized) An undefined value was used as if it were already  
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.  
To suppress this warning assign a defined value to your variables.  
   
To help you figure out what was undefined, perl will try to tell you  
the name of the variable (if any) that was undefined. In some cases  
it cannot do this, so it also tells you what operation you used the  
undefined value in. Note, however, that perl optimizes your program  
anid the operation displayed in the warning may not necessarily appear  
literally in your program. For example, "that $foo" is usually  
optimized into "that " . $foo, and the warning will refer to the  
concatenation (.) operator, even though there is no . in  
your program.  
   
Use of uninitialized value $ys in printf at ./diagrams.pl line 812 (#1)  
Use of uninitialized value $xs in printf at ./diagrams.pl line 812 (#1)  
(W uninitialized) An undefined value was used as if it were already  
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.  
To suppress this warning assign a defined value to your variables.  
   
To help you figure out what was undefined, perl will try to tell you  
the name of the variable (if any) that was undefined. In some cases  
it cannot do this, so it also tells you what operation you used the  
undefined value in. Note, however, that perl optimizes your program  
anid the operation displayed in the warning may not necessarily appear  
literally in your program. For example, "that $foo" is usually  
optimized into "that " . $foo, and the warning will refer to the  
concatenation (.) operator, even though there is no . in  
your program.  
   
Use of uninitialized value $ys in printf at ./diagrams.pl line 812 (#1)  
Use of uninitialized value $xs in printf at ./diagrams.pl line 812 (#1)  
(W uninitialized) An undefined value was used as if it were already  
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.  
To suppress this warning assign a defined value to your variables.  
   
To help you figure out what was undefined, perl will try to tell you  
the name of the variable (if any) that was undefined. In some cases  
it cannot do this, so it also tells you what operation you used the  
undefined value in. Note, however, that perl optimizes your program  
anid the operation displayed in the warning may not necessarily appear  
literally in your program. For example, "that $foo" is usually  
optimized into "that " . $foo, and the warning will refer to the  
concatenation (.) operator, even though there is no . in  
your program.  
   
Use of uninitialized value $ys in printf at ./diagrams.pl line 812 (#1)  
Use of uninitialized value $xs in printf at ./diagrams.pl line 812 (#1)  
(W uninitialized) An undefined value was used as if it were already  
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.  
To suppress this warning assign a defined value to your variables.  
   
To help you figure out what was undefined, perl will try to tell you  
the name of the variable (if any) that was undefined. In some cases  
it cannot do this, so it also tells you what operation you used the  
undefined value in. Note, however, that perl optimizes your program  
anid the operation displayed in the warning may not necessarily appear  
literally in your program. For example, "that $foo" is usually  
optimized into "that " . $foo, and the warning will refer to the  
concatenation (.) operator, even though there is no . in  
your program.  
   
Use of uninitialized value $ys in printf at ./diagrams.pl line 812 (#1)  
Use of uninitialized value $xs in printf at ./diagrams.pl line 812 (#1)  
(W uninitialized) An undefined value was used as if it were already  
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.  
To suppress this warning assign a defined value to your variables.  
   
To help you figure out what was undefined, perl will try to tell you  
the name of the variable (if any) that was undefined. In some cases  
it cannot do this, so it also tells you what operation you used the  
undefined value in. Note, however, that perl optimizes your program  
anid the operation displayed in the warning may not necessarily appear  
literally in your program. For example, "that $foo" is usually  
optimized into "that " . $foo, and the warning will refer to the  
concatenation (.) operator, even though there is no . in  
your program.  
   
Use of uninitialized value $ys in printf at ./diagrams.pl line 812 (#1)  
Use of uninitialized value $xs in printf at ./diagrams.pl line 812 (#1)  
(W uninitialized) An undefined value was used as if it were already  
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.  
To suppress this warning assign a defined value to your variables.  
   
To help you figure out what was undefined, perl will try to tell you  
the name of the variable (if any) that was undefined. In some cases  
it cannot do this, so it also tells you what operation you used the  
undefined value in. Note, however, that perl optimizes your program  
anid the operation displayed in the warning may not necessarily appear  
literally in your program. For example, "that $foo" is usually  
optimized into "that " . $foo, and the warning will refer to the  
concatenation (.) operator, even though there is no . in  
your program.  
   
Use of uninitialized value $ys in printf at ./diagrams.pl line 812 (#1)  
Use of uninitialized value $xs in printf at ./diagrams.pl line 812 (#1)  
(W uninitialized) An undefined value was used as if it were already  
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.  
To suppress this warning assign a defined value to your variables.  
   
To help you figure out what was undefined, perl will try to tell you  
the name of the variable (if any) that was undefined. In some cases  
it cannot do this, so it also tells you what operation you used the  
undefined value in. Note, however, that perl optimizes your program  
anid the operation displayed in the warning may not necessarily appear  
literally in your program. For example, "that $foo" is usually  
optimized into "that " . $foo, and the warning will refer to the  
concatenation (.) operator, even though there is no . in  
your program.  
   
Use of uninitialized value $ys in printf at ./diagrams.pl line 812 (#1)  
Use of uninitialized value $xs in printf at ./diagrams.pl line 812 (#1)  
(W uninitialized) An undefined value was used as if it were already  
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.  
To suppress this warning assign a defined value to your variables.  
   
To help you figure out what was undefined, perl will try to tell you  
the name of the variable (if any) that was undefined. In some cases  
it cannot do this, so it also tells you what operation you used the  
undefined value in. Note, however, that perl optimizes your program  
anid the operation displayed in the warning may not necessarily appear  
literally in your program. For example, "that $foo" is usually  
optimized into "that " . $foo, and the warning will refer to the  
concatenation (.) operator, even though there is no . in  
your program.  
   
Use of uninitialized value $ys in printf at ./diagrams.pl line 812 (#1)  
Use of uninitialized value $xs in printf at ./diagrams.pl line 812 (#1)  
(W uninitialized) An undefined value was used as if it were already  
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.  
To suppress this warning assign a defined value to your variables.  
   
To help you figure out what was undefined, perl will try to tell you  
the name of the variable (if any) that was undefined. In some cases  
it cannot do this, so it also tells you what operation you used the  
undefined value in. Note, however, that perl optimizes your program  
anid the operation displayed in the warning may not necessarily appear  
literally in your program. For example, "that $foo" is usually  
optimized into "that " . $foo, and the warning will refer to the  
concatenation (.) operator, even though there is no . in  
your program.  
   
Use of uninitialized value $ys in printf at ./diagrams.pl line 812 (#1)  
Use of uninitialized value $xs in printf at ./diagrams.pl line 812 (#1)  
(W uninitialized) An undefined value was used as if it were already  
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.  
To suppress this warning assign a defined value to your variables.  
   
To help you figure out what was undefined, perl will try to tell you  
the name of the variable (if any) that was undefined. In some cases  
it cannot do this, so it also tells you what operation you used the  
undefined value in. Note, however, that perl optimizes your program  
anid the operation displayed in the warning may not necessarily appear  
literally in your program. For example, "that $foo" is usually  
optimized into "that " . $foo, and the warning will refer to the  
concatenation (.) operator, even though there is no . in  
your program.  
   
Use of uninitialized value $ys in printf at ./diagrams.pl line 812 (#1)  
Use of uninitialized value $xs in printf at ./diagrams.pl line 812 (#1)  
(W uninitialized) An undefined value was used as if it were already  
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.  
To suppress this warning assign a defined value to your variables.  
   
To help you figure out what was undefined, perl will try to tell you  
the name of the variable (if any) that was undefined. In some cases  
it cannot do this, so it also tells you what operation you used the  
undefined value in. Note, however, that perl optimizes your program  
anid the operation displayed in the warning may not necessarily appear  
literally in your program. For example, "that $foo" is usually  
optimized into "that " . $foo, and the warning will refer to the  
concatenation (.) operator, even though there is no . in  
your program.  
   
Use of uninitialized value $ys in printf at ./diagrams.pl line 812 (#1)  
Use of uninitialized value $xs in printf at ./diagrams.pl line 812 (#1)  
(W uninitialized) An undefined value was used as if it were already  
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.  
To suppress this warning assign a defined value to your variables.  
   
To help you figure out what was undefined, perl will try to tell you  
the name of the variable (if any) that was undefined. In some cases  
it cannot do this, so it also tells you what operation you used the  
undefined value in. Note, however, that perl optimizes your program  
anid the operation displayed in the warning may not necessarily appear  
literally in your program. For example, "that $foo" is usually  
optimized into "that " . $foo, and the warning will refer to the  
concatenation (.) operator, even though there is no . in  
your program.  
   
Use of uninitialized value $ys in printf at ./diagrams.pl line 812 (#1)  
Use of uninitialized value $xs in printf at ./diagrams.pl line 812 (#1)  
(W uninitialized) An undefined value was used as if it were already  
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.  
To suppress this warning assign a defined value to your variables.  
   
To help you figure out what was undefined, perl will try to tell you  
the name of the variable (if any) that was undefined. In some cases  
it cannot do this, so it also tells you what operation you used the  
undefined value in. Note, however, that perl optimizes your program  
anid the operation displayed in the warning may not necessarily appear  
literally in your program. For example, "that $foo" is usually  
optimized into "that " . $foo, and the warning will refer to the  
concatenation (.) operator, even though there is no . in  
your program.  
   
Use of uninitialized value $ys in printf at ./diagrams.pl line 812 (#1)  
Use of uninitialized value $xs in printf at ./diagrams.pl line 812 (#1)  
(W uninitialized) An undefined value was used as if it were already  
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.  
To suppress this warning assign a defined value to your variables.  
   
To help you figure out what was undefined, perl will try to tell you  
the name of the variable (if any) that was undefined. In some cases  
it cannot do this, so it also tells you what operation you used the  
undefined value in. Note, however, that perl optimizes your program  
anid the operation displayed in the warning may not necessarily appear  
literally in your program. For example, "that $foo" is usually  
optimized into "that " . $foo, and the warning will refer to the  
concatenation (.) operator, even though there is no . in  
your program.  
   
Use of uninitialized value $ys in printf at ./diagrams.pl line 812 (#1)  
Use of uninitialized value $xs in printf at ./diagrams.pl line 812 (#1)  
(W uninitialized) An undefined value was used as if it were already  
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.  
To suppress this warning assign a defined value to your variables.  
   
To help you figure out what was undefined, perl will try to tell you  
the name of the variable (if any) that was undefined. In some cases  
it cannot do this, so it also tells you what operation you used the  
undefined value in. Note, however, that perl optimizes your program  
anid the operation displayed in the warning may not necessarily appear  
literally in your program. For example, "that $foo" is usually  
optimized into "that " . $foo, and the warning will refer to the  
concatenation (.) operator, even though there is no . in  
your program.  
   
Use of uninitialized value $ys in printf at ./diagrams.pl line 812 (#1)  
Use of uninitialized value $xs in printf at ./diagrams.pl line 812 (#1)  
(W uninitialized) An undefined value was used as if it were already  
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.  
To suppress this warning assign a defined value to your variables.  
   
To help you figure out what was undefined, perl will try to tell you  
the name of the variable (if any) that was undefined. In some cases  
it cannot do this, so it also tells you what operation you used the  
undefined value in. Note, however, that perl optimizes your program  
anid the operation displayed in the warning may not necessarily appear  
literally in your program. For example, "that $foo" is usually  
optimized into "that " . $foo, and the warning will refer to the  
concatenation (.) operator, even though there is no . in  
your program.  
   
Use of uninitialized value $ys in printf at ./diagrams.pl line 812 (#1)  
Use of uninitialized value $xs in printf at ./diagrams.pl line 812 (#1)  
(W uninitialized) An undefined value was used as if it were already  
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.  
To suppress this warning assign a defined value to your variables.  
   
To help you figure out what was undefined, perl will try to tell you  
the name of the variable (if any) that was undefined. In some cases  
it cannot do this, so it also tells you what operation you used the  
undefined value in. Note, however, that perl optimizes your program  
anid the operation displayed in the warning may not necessarily appear  
literally in your program. For example, "that $foo" is usually  
optimized into "that " . $foo, and the warning will refer to the  
concatenation (.) operator, even though there is no . in  
your program.  
   
Use of uninitialized value $ys in printf at ./diagrams.pl line 812 (#1)  
   

Powered by WebSVN 2.2.1