<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
<tt>Hi Marty,<br>
<br>
These two applications still don't show plots:<br>
<a class="moz-txt-link-freetext" href="http://claswebnew.jlab.org/cgi-bin/epics_history/epics.pl">http://claswebnew.jlab.org/cgi-bin/epics_history/epics.pl</a><br>
<a class="moz-txt-link-freetext" href="http://claswebnew.jlab.org/cgi-bin/ONLINE_TIMELINE/timeline_frames.pl">http://claswebnew.jlab.org/cgi-bin/ONLINE_TIMELINE/timeline_frames.pl</a><br>
<br>
I believe it is gnuplot issue.<br>
You managed to fix it in <br>
<a moz-do-not-send="true"
href="http://claswebnew.jlab.org/cgi-bin/HALL_ABC/top_frame-MEW.pl">http://claswebnew.jlab.org/cgi-bin/HALL_ABC/top_frame-MEW.pl</a><br>
It displays plots generated by gnuplot.<br>
Probably should be similar fix in those too.</tt><br>
<br>
-Eugene<br>
<br>
On 01/06/11 06:52, Marty Wise wrote:
<blockquote cite="mid:000001cbad98$38e691a0$aab3b4e0$@org"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 12 (filtered
medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:572741734;
mso-list-type:hybrid;
mso-list-template-ids:-1764822862 42506952 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:20.25pt;
text-indent:-.25in;
font-family:"Calibri","sans-serif";
mso-fareast-font-family:Calibri;}
@list l1
{mso-list-id:1867331214;
mso-list-type:hybrid;
mso-list-template-ids:-361347470 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal">All,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Using the Pezca-0.4 source package, I was
able to build and
install it into our central /apps version of perl without
having to build or
make any parts of the EPICS distribution available to it. At
runtime, the
package still needs access to a couple of EPICS shared
libraries, but this is
easily arranged through LD_LIBRARY_PATH. The bottom line is
that I have a
working example of this new configuration. If you access the
URL: <a moz-do-not-send="true"
href="http://claswebnew.jlab.org/cgi-bin/HALL_ABC/top_frame-MEW.pl">http://claswebnew.jlab.org/cgi-bin/HALL_ABC/top_frame-MEW.pl</a>,
you’ll see an example of the configuration at work. This page
is a _<i>slighlty</i>_
modified version of the original -- <a moz-do-not-send="true"
href="http://claswebnew.jlab.org/cgi-bin/HALL_ABC/top_frame.pl">http://claswebnew.jlab.org/cgi-bin/HALL_ABC/top_frame.pl</a>
which does not work.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">After building Pezca into /apps Perl, I
made a small
modification to the top_frame-MEW.pl script mentioned above.
All I had to do
was comment out the line: <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> #use lib
('/group/clas/www/clasweb/htbin/PERL_CPAN/lib/site_perl/5.6.0/i686-linux');<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">This change removes the explicit reference
to the perl
library installation down in /group/clas/www/clasweb/… Since
the script
uses /apps/bin/perl, it Is able to find the Pezca module in
the apps build.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">To address the runtime dependence on the
epics shlibs, I set
LD_LIBRARY_PATH in the web server configuration to include a
temporary
directory into which I’ve placed the libca, libCom and libezca
shared
libraries.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">This seems to work, though it’s hard to be
sure since
I’m not very familiar with them.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The problem is that with the explicit
library reference,
there is no way to fix this without modifying all the scripts
individually. You
guys have a number of scripts configured like this. Changing
them now will
break them on the running clasweb. I can easily find and fix
most of these
problems, but, I will need to do it as part of the cutover.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">So… given these results, if nobody sees any
problem
with these changes, can we plan to do the switch to the new
server today? I
will need to have both the new and old servers offline for an
hour or two to
make all the necessary changes. Then, there will certainly
still be other
problems that turn up afterward. These will need to be dealt
with as they are
discovered. I think, however, that all the major stuff that
has been seen has
been addressed.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I should also point out that reverting back
to the original
server in the event of insurmountable problems of some kind
will require a
similar 1-2 hour outage to switch back. Personally, I hate to
go back in
general, and in this case, RHEL3 (on the current clasweb) is
obsolete and no
longer supported, and has been holding up a number of projects
you guys have
asked for that require newer software versions – e.g. newer
MediaWiki,
MantisBT, DocDB, etc.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">So, can I move forward with the switch? If
so, when is a
good time?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Marty<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Clas_offline mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Clas_offline@jlab.org">Clas_offline@jlab.org</a>
<a class="moz-txt-link-freetext" href="https://mailman.jlab.org/mailman/listinfo/clas_offline">https://mailman.jlab.org/mailman/listinfo/clas_offline</a></pre>
</blockquote>
</body>
</html>