I don't know of a way to do this but NFS could easily be used to
restrict user access to the source tree this if the machine that you
build from is not available or commonly used by the users. On the
machine hosing the NFS share change /etc/exports to look something like this
/usr/local/epics my.compile.node(rw) *.my.domain(ro)
This allows only my.compile.node to change things. Make sure to add in
other common options (like no_root_squash) if needed.
David Dudley wrote:
Is there a way to setup the build system so that the
O.<$EPICS_HOST_ARCH> directories are in another location?
I'm building for 3 different architectures, and I'd like to put the
EPICS source on a single (hopefully!) write protected NFS server, and
link to it when I need access to build, but would rather not have the
client machine writing directories on the server if I can get away with
it.
David
--
John Hammonds
Beamline and Data Acquisition Group
APS Engineering Support Division
Argonne National Laboratory
[email protected] <mailto:[email protected]>
(630)252-5317
- Replies:
- Re: Build Question Pete Jemian
- References:
- Build Question David Dudley
- Navigate by Date:
- Prev:
RE: Problems getting the Python module to work Matt Newville
- Next:
Re: Build Question Pete Jemian
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
<2008>
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Build Question David Dudley
- Next:
Re: Build Question Pete Jemian
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
<2008>
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|