[Lerftest-ctrls] Ops with non-laci accounts
Wesley Moore
wmoore at jlab.org
Wed May 23 21:18:53 EDT 2018
That should work.
Wesley
On Wed, May 23, 2018 at 7:40 PM -0500, "Bruce Hill" <bhill at slac.stanford.edu> wrote:
I should also point out that the ENVS.bash script sources
epicsenv-3.15.5-1.0.bash.
ENVS.bash should only be run once from your .bashrc to avoid
bloating your env path variables.
epicsenv-3.15.5-1.0.bash and it's variants for other base versions
can be run as needed
to setup or switch your EPICS environment.
Cheers,
- Bruce
On 05/23/2018 05:20 PM, Bruce Hill
wrote:
Hi Sonya,
Will the user's servers have access to the same NFS filesystem?
If so, they should be able to source this file for EPICS setup.
source /usr/local/lcls/epics/setup/epicsenv-3.15.5-1.0.bash
Please note that this script only sets up EPICS related
environment.
For physics, matlab, python, etc, they should
source /usr/local/lcls/tools/script/ENVS.bash
Regards,
- Bruce
On 05/23/2018 11:28 AM, Sonya Hoobler
wrote:
Hugo,
Bruce, Patrick,
Which EPICS setup file (path+filename) should the user servers
use to pick up our EPICS environment variables, etc.?
Thanks,
Sonya
On Mon, 21 May 2018, Wesley Moore wrote:
Ive brought it uo before, but apparently
in the wrong SLAC circle. r/w we can easily sort out.
If there's a setup file we can source, we're golden.
Wesley
On Mon, May 21, 2018 at 5:29 PM -0500, "Sonya Hoobler" <sonya at slac.stanford.edu>
wrote:
Hi Wesley,
Yes, thanks for bringing this up. We'll need to figure this
out. I had not
realized until last week that the users would not be logged
into the same
servers that we are using.
I am currently logged into lcls01 and I seem to have read-only
access to
the LCLS-II/LERF file system. The first couple things that
come to mind:
1. The users' environments will need to point to our displays,
scripts,
programs, etc.
2. Some scripts/programs may try to write files to these
read-only areas,
so we may need to handle that.
Sonya
No write access may be an issue, for example if users need to
execute
On Mon, 21 May 2018, Wesley Moore wrote:
Sonya, this isn?t directed at you
only, but maybe the front-runner for this.
Any updates on running GUIs, etc, as a normal non-laci user?
We don?t want that account to be requirement to run ops.
Users will run from lclsl01-03 and lcls-vdi01-10.
Wesley
Hi Wesley,
Yes, thanks for bringing this up. We'll need to figure this
out. I had not
realized until last week that the users would not be logged
into the same
servers that we are using.
I am currently logged into lcls01 and I seem to have read-only
access to
the LCLS-II/LERF file system. The first couple things that
come to mind:
1. The users' environments will need to point to our displays,
scripts,
programs, etc.
2. Some scripts/programs may try to write files to these
read-only areas,
so we may need to handle that.
Sonya
No write access may be an issue, for example if users need to
execute
On Mon, 21 May 2018, Wesley Moore wrote:
Sonya, this isn?t directed at you
only, but maybe the front-runner for this.
Any updates on running GUIs, etc, as a normal non-laci user?
We don?t want that account to be requirement to run ops.
Users will run from lclsl01-03 and lcls-vdi01-10.
Wesley
_______________________________________________
Mailing List: Lerftest-ctrls at jlab.org
https://mailman.jlab.org/mailman/listinfo/lerftest-ctrls
Wiki: https://wiki.jlab.org/lerf/index.php/Network
--
Bruce Hill
Member Technical Staff
SLAC National Accelerator Lab
2575 Sand Hill Road M/S 10
Menlo Park, CA 94025
_______________________________________________
Mailing List: Lerftest-ctrls at jlab.org
https://mailman.jlab.org/mailman/listinfo/lerftest-ctrls
Wiki: https://wiki.jlab.org/lerf/index.php/Network
--
Bruce Hill
Member Technical Staff
SLAC National Accelerator Lab
2575 Sand Hill Road M/S 10
Menlo Park, CA 94025
I should also point out that the ENVS.bash script sources epicsenv-3.15.5-1.0.bash.
ENVS.bash should only be run once from your .bashrc to avoid bloating your env path variables.
epicsenv-3.15.5-1.0.bash and it's variants for other base versions can be run as needed
to setup or switch your EPICS environment.
Cheers,
- Bruce
On 05/23/2018 05:20 PM, Bruce Hill wrote:
> Hi Sonya,
> Will the user's servers have access to the same NFS filesystem?
> If so, they should be able to source this file for EPICS setup.
> source /usr/local/lcls/epics/setup/epicsenv-3.15.5-1.0.bash
>
> Please note that this script only sets up EPICS related environment.
> For physics, matlab, python, etc, they should
> source /usr/local/lcls/tools/script/ENVS.bash
>
> Regards,
> - Bruce
>
> On 05/23/2018 11:28 AM, Sonya Hoobler wrote:
>> Hugo, Bruce, Patrick,
>>
>> Which EPICS setup file (path+filename) should the user servers use to pick up our EPICS environment variables, etc.?
>>
>> Thanks,
>> Sonya
>>
>>
>>
>> On Mon, 21 May 2018, Wesley Moore wrote:
>>
>>> Ive brought it uo before, but apparently in the wrong SLAC circle. r/w we can easily sort out.
>>>
>>>
>>>
>>>
>>> If there's a setup file we can source, we're golden.
>>>
>>>
>>>
>>>
>>> Wesley
>>>
>>>
>>>
>>>
>>> On Mon, May 21, 2018 at 5:29 PM -0500, "Sonya Hoobler" <sonya at slac.stanford.edu> wrote:
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Hi Wesley,
>>>
>>> Yes, thanks for bringing this up. We'll need to figure this out. I had not
>>> realized until last week that the users would not be logged into the same
>>> servers that we are using.
>>>
>>> I am currently logged into lcls01 and I seem to have read-only access to
>>> the LCLS-II/LERF file system. The first couple things that come to mind:
>>>
>>> 1. The users' environments will need to point to our displays, scripts,
>>> programs, etc.
>>>
>>> 2. Some scripts/programs may try to write files to these read-only areas,
>>> so we may need to handle that.
>>>
>>> Sonya
>>>
>>>
>>>
>>>
>>>
>>> No write access may be an issue, for example if users need to execute
>>>
>>> On Mon, 21 May 2018, Wesley Moore wrote:
>>>
>>>> Sonya, this isn?t directed at you only, but maybe the front-runner for this.
>>>>
>>>> Any updates on running GUIs, etc, as a normal non-laci user?
>>>>
>>>> We don?t want that account to be requirement to run ops. Users will run from lclsl01-03 and lcls-vdi01-10.
>>>>
>>>> Wesley
>>>>
>>>
>>>
>>>
>>>
>>>
>>> Hi Wesley,
>>>
>>> Yes, thanks for bringing this up. We'll need to figure this out. I had not
>>> realized until last week that the users would not be logged into the same
>>> servers that we are using.
>>>
>>> I am currently logged into lcls01 and I seem to have read-only access to
>>> the LCLS-II/LERF file system. The first couple things that come to mind:
>>>
>>> 1. The users' environments will need to point to our displays, scripts,
>>> programs, etc.
>>>
>>> 2. Some scripts/programs may try to write files to these read-only areas,
>>> so we may need to handle that.
>>>
>>> Sonya
>>>
>>>
>>>
>>>
>>>
>>> No write access may be an issue, for example if users need to execute
>>>
>>> On Mon, 21 May 2018, Wesley Moore wrote:
>>>
>>>> Sonya, this isn?t directed at you only, but maybe the front-runner for this.
>>>>
>>>> Any updates on running GUIs, etc, as a normal non-laci user?
>>>>
>>>> We don?t want that account to be requirement to run ops. Users will run from lclsl01-03 and lcls-vdi01-10.
>>>>
>>>> Wesley
>>>>
>>>
>>
>>
>> _______________________________________________
>> Mailing List:Lerftest-ctrls at jlab.org
>> https://mailman.jlab.org/mailman/listinfo/lerftest-ctrls
>> Wiki:https://wiki.jlab.org/lerf/index.php/Network
>
> --
> Bruce Hill
> Member Technical Staff
> SLAC National Accelerator Lab
> 2575 Sand Hill Road M/S 10
> Menlo Park, CA 94025
>
>
> _______________________________________________
> Mailing List: Lerftest-ctrls at jlab.org
> https://mailman.jlab.org/mailman/listinfo/lerftest-ctrls
> Wiki: https://wiki.jlab.org/lerf/index.php/Network
--
Bruce Hill
Member Technical Staff
SLAC National Accelerator Lab
2575 Sand Hill Road M/S 10
Menlo Park, CA 94025
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/lerftest-ctrls/attachments/20180523/c31f9158/attachment-0001.html>
-------------- next part --------------
_______________________________________________
Mailing List: Lerftest-ctrls at jlab.org
https://mailman.jlab.org/mailman/listinfo/lerftest-ctrls
Wiki: https://wiki.jlab.org/lerf/index.php/Network
More information about the Lerftest-ctrls
mailing list