<html><body><div><div dir="auto" style="direction: ltr; margin: 0; padding: 0; font-family: sans-serif; font-size: 11pt; color: black; ">That should work. <br>
<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0; font-family: sans-serif; font-size: 11pt; color: black; ">Wesley</div>
<br><br><br>
<div class="gmail_quote">On Wed, May 23, 2018 at 7:40 PM -0500, "Bruce Hill" <span dir="ltr"><<a href="mailto:bhill@slac.stanford.edu" target="_blank">bhill@slac.stanford.edu</a>></span> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="3D"ltr"">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
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.<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.<br>
<br>
Cheers,<br>
- Bruce<br>
<br>
<div class="moz-cite-prefix">On 05/23/2018 05:20 PM, Bruce Hill
wrote:<br>
</div>
<blockquote type="cite" cite="mid:04368c1c-29f3-55ef-0a69-5beb47dbcd8d@slac.stanford.edu">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
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="moz-cite-prefix">On 05/23/2018 11:28 AM, Sonya Hoobler
wrote:<br>
</div>
<blockquote type="cite" cite="mid:alpine.LRH.2.00.1805231126440.24937@lcls-dev2.slac.stanford.edu">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="moz-txt-link-rfc2396E" href="mailto:sonya@slac.stanford.edu" moz-do-not-send="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="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Mailing List: <a class="moz-txt-link-abbreviated" href="mailto:Lerftest-ctrls@jlab.org" moz-do-not-send="true">Lerftest-ctrls@jlab.org</a>
<a class="moz-txt-link-freetext" href="https://mailman.jlab.org/mailman/listinfo/lerftest-ctrls" moz-do-not-send="true">https://mailman.jlab.org/mailman/listinfo/lerftest-ctrls</a>
Wiki: <a class="moz-txt-link-freetext" href="https://wiki.jlab.org/lerf/index.php/Network" moz-do-not-send="true">https://wiki.jlab.org/lerf/index.php/Network</a>
</pre>
</blockquote>
<br>
<pre class="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="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Mailing List: <a class="moz-txt-link-abbreviated" href="mailto:Lerftest-ctrls@jlab.org">Lerftest-ctrls@jlab.org</a>
<a class="moz-txt-link-freetext" href="https://mailman.jlab.org/mailman/listinfo/lerftest-ctrls">https://mailman.jlab.org/mailman/listinfo/lerftest-ctrls</a>
Wiki: <a class="moz-txt-link-freetext" href="https://wiki.jlab.org/lerf/index.php/Network">https://wiki.jlab.org/lerf/index.php/Network</a>
</pre>
</blockquote>
<br>
<pre class="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>
</blockquote>
</div>
</div><br><div>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#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.<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.<br>
<br>
Cheers,<br>
- Bruce<br>
<br>
<div class="moz-cite-prefix">On 05/23/2018 05:20 PM, Bruce Hill
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:04368c1c-29f3-55ef-0a69-5beb47dbcd8d@slac.stanford.edu">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
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="moz-cite-prefix">On 05/23/2018 11:28 AM, Sonya Hoobler
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:alpine.LRH.2.00.1805231126440.24937@lcls-dev2.slac.stanford.edu">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="moz-txt-link-rfc2396E"
href="mailto:sonya@slac.stanford.edu" moz-do-not-send="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="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Mailing List: <a class="moz-txt-link-abbreviated" href="mailto:Lerftest-ctrls@jlab.org" moz-do-not-send="true">Lerftest-ctrls@jlab.org</a>
<a class="moz-txt-link-freetext" href="https://mailman.jlab.org/mailman/listinfo/lerftest-ctrls" moz-do-not-send="true">https://mailman.jlab.org/mailman/listinfo/lerftest-ctrls</a>
Wiki: <a class="moz-txt-link-freetext" href="https://wiki.jlab.org/lerf/index.php/Network" moz-do-not-send="true">https://wiki.jlab.org/lerf/index.php/Network</a>
</pre>
</blockquote>
<br>
<pre class="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="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Mailing List: <a class="moz-txt-link-abbreviated" href="mailto:Lerftest-ctrls@jlab.org">Lerftest-ctrls@jlab.org</a>
<a class="moz-txt-link-freetext" href="https://mailman.jlab.org/mailman/listinfo/lerftest-ctrls">https://mailman.jlab.org/mailman/listinfo/lerftest-ctrls</a>
Wiki: <a class="moz-txt-link-freetext" href="https://wiki.jlab.org/lerf/index.php/Network">https://wiki.jlab.org/lerf/index.php/Network</a>
</pre>
</blockquote>
<br>
<pre class="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></body></html>