<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;" dir="ltr">
<p style="margin-top:0;margin-bottom:0">Hi,</p>
<p style="margin-top:0;margin-bottom:0">Comments below</p>
<br>
<br>
<div style="color: rgb(0, 0, 0);">
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Lerftest-ctrls <lerftest-ctrls-bounces@jlab.org> on behalf of Bruce Hill <bhill@slac.stanford.edu><br>
<b>Sent:</b> Wednesday, May 23, 2018 5:40 PM<br>
<b>To:</b> lerftest-ctrls@jlab.org<br>
<b>Subject:</b> Re: [Lerftest-ctrls] Ops with non-laci accounts</font>
<div> </div>
</div>
<meta content="text/html; charset=utf-8">
<div style="background-color:#FFFFFF">I should also point out that the ENVS.bash script sources epicsenv-3.15.5-1.0.bash.<br>
<br>
ENVS.bash should only be run once from your .bashrc to avoid bloating your env path variables.</div>
<div style="background-color:#FFFFFF"><br>
</div>
<div style="background-color:#FFFFFF">>>>>></div>
<div style="background-color:#FFFFFF">@Bruce, can you add some logic to prevent the path from getting bloated?</div>
<div style="background-color:#FFFFFF">>>>>>>>><br>
<br>
epicsenv-3.15.5-1.0.bash and it's variants for other base versions can be run as needed<br>
to setup or switch your EPICS environment.</div>
<div style="background-color:#FFFFFF"><br>
</div>
<div style="background-color:#FFFFFF">>>>>>></div>
<div style="background-color:#FFFFFF">Nice,</div>
<div style="background-color:#FFFFFF">Can we switch between different version of base versions and not worry about</div>
<div style="background-color:#FFFFFF">env path variable bloat?</div>
<div style="background-color:#FFFFFF">>>>>>>>>></div>
<div style="background-color:#FFFFFF"><br>
<br>
Cheers,<br>
- Bruce<br>
<br>
<div class="x_moz-cite-prefix">On 05/23/2018 05:20 PM, Bruce Hill wrote:<br>
</div>
<blockquote type="cite">Hi Sonya,<br>
Will the user's servers have access to the same NFS filesystem?<br>
If so, they should be able to source this file for EPICS setup.<br>
source /usr/local/lcls/epics/setup/epicsenv-3.15.5-1.0.bash<br>
<br>
Please note that this script only sets up EPICS related environment.<br>
For physics, matlab, python, etc, they should<br>
source /usr/local/lcls/tools/script/ENVS.bash<br>
<br>
Regards,<br>
- Bruce<br>
<br>
<div class="x_moz-cite-prefix">On 05/23/2018 11:28 AM, Sonya Hoobler wrote:<br>
</div>
<blockquote type="cite">Hugo, Bruce, Patrick, <br>
<br>
Which EPICS setup file (path+filename) should the user servers use to pick up our EPICS environment variables, etc.?
<br>
<br>
Thanks, <br>
Sonya <br>
<br>
<br>
<br>
On Mon, 21 May 2018, Wesley Moore wrote: <br>
<br>
<blockquote type="cite">Ive brought it uo before, but apparently in the wrong SLAC circle. r/w we can easily sort out.
<br>
<br>
<br>
<br>
<br>
If there's a setup file we can source, we're golden. <br>
<br>
<br>
<br>
<br>
Wesley <br>
<br>
<br>
<br>
<br>
On Mon, May 21, 2018 at 5:29 PM -0500, "Sonya Hoobler" <a class="x_moz-txt-link-rfc2396E OWAAutoLink" href="mailto:sonya@slac.stanford.edu" id="LPlnk428730" previewremoved="true">
<sonya@slac.stanford.edu></a> wrote: <br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
Hi Wesley, <br>
<br>
Yes, thanks for bringing this up. We'll need to figure this out. I had not <br>
realized until last week that the users would not be logged into the same <br>
servers that we are using. <br>
<br>
I am currently logged into lcls01 and I seem to have read-only access to <br>
the LCLS-II/LERF file system. The first couple things that come to mind: <br>
<br>
1. The users' environments will need to point to our displays, scripts, <br>
programs, etc. <br>
<br>
2. Some scripts/programs may try to write files to these read-only areas, <br>
so we may need to handle that. <br>
<br>
Sonya <br>
<br>
<br>
<br>
<br>
<br>
No write access may be an issue, for example if users need to execute <br>
<br>
On Mon, 21 May 2018, Wesley Moore wrote: <br>
<br>
<blockquote type="cite">Sonya, this isn?t directed at you only, but maybe the front-runner for this.
<br>
<br>
Any updates on running GUIs, etc, as a normal non-laci user? <br>
<br>
We don?t want that account to be requirement to run ops. Users will run from lclsl01-03 and lcls-vdi01-10.
<br>
<br>
Wesley <br>
<br>
</blockquote>
<br>
<br>
<br>
<br>
<br>
Hi Wesley, <br>
<br>
Yes, thanks for bringing this up. We'll need to figure this out. I had not <br>
realized until last week that the users would not be logged into the same <br>
servers that we are using. <br>
<br>
I am currently logged into lcls01 and I seem to have read-only access to <br>
the LCLS-II/LERF file system. The first couple things that come to mind: <br>
<br>
1. The users' environments will need to point to our displays, scripts, <br>
programs, etc. <br>
<br>
2. Some scripts/programs may try to write files to these read-only areas, <br>
so we may need to handle that. <br>
<br>
Sonya <br>
<br>
<br>
<br>
<br>
<br>
No write access may be an issue, for example if users need to execute <br>
<br>
On Mon, 21 May 2018, Wesley Moore wrote: <br>
<br>
<blockquote type="cite">Sonya, this isn?t directed at you only, but maybe the front-runner for this.
<br>
<br>
Any updates on running GUIs, etc, as a normal non-laci user? <br>
<br>
We don?t want that account to be requirement to run ops. Users will run from lclsl01-03 and lcls-vdi01-10.
<br>
<br>
Wesley <br>
<br>
</blockquote>
<br>
</blockquote>
<br>
<fieldset class="x_mimeAttachmentHeader"></fieldset> <br>
<pre>_______________________________________________
Mailing List: <a class="x_moz-txt-link-abbreviated OWAAutoLink" href="mailto:Lerftest-ctrls@jlab.org" id="LPlnk873383" previewremoved="true">Lerftest-ctrls@jlab.org</a>
<a class="x_moz-txt-link-freetext OWAAutoLink" href="https://mailman.jlab.org/mailman/listinfo/lerftest-ctrls" id="LPlnk965476" previewremoved="true">https://mailman.jlab.org/mailman/listinfo/lerftest-ctrls</a>
Wiki: <a class="x_moz-txt-link-freetext OWAAutoLink" href="https://wiki.jlab.org/lerf/index.php/Network" id="LPlnk367173" previewremoved="true">https://wiki.jlab.org/lerf/index.php/Network</a>
</pre>
</blockquote>
<br>
<pre class="x_moz-signature" cols="120">--
Bruce Hill
Member Technical Staff
SLAC National Accelerator Lab
2575 Sand Hill Road M/S 10
Menlo Park, CA 94025
</pre>
<br>
<fieldset class="x_mimeAttachmentHeader"></fieldset> <br>
<pre>_______________________________________________
Mailing List: <a class="x_moz-txt-link-abbreviated OWAAutoLink" href="mailto:Lerftest-ctrls@jlab.org" id="LPlnk766990" previewremoved="true">Lerftest-ctrls@jlab.org</a>
<a class="x_moz-txt-link-freetext OWAAutoLink" href="https://mailman.jlab.org/mailman/listinfo/lerftest-ctrls" id="LPlnk517006" previewremoved="true">https://mailman.jlab.org/mailman/listinfo/lerftest-ctrls</a>
Wiki: <a class="x_moz-txt-link-freetext OWAAutoLink" href="https://wiki.jlab.org/lerf/index.php/Network" id="LPlnk621471" previewremoved="true">https://wiki.jlab.org/lerf/index.php/Network</a>
</pre>
</blockquote>
<br>
<pre class="x_moz-signature" cols="120">--
Bruce Hill
Member Technical Staff
SLAC National Accelerator Lab
2575 Sand Hill Road M/S 10
Menlo Park, CA 94025
</pre>
</div>
</div>
</div>
</body>
</html>