LISTSERV mailing list manager LISTSERV 16.5

Help for XROOTD-L Archives


XROOTD-L Archives

XROOTD-L Archives


XROOTD-L@LISTSERV.SLAC.STANFORD.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

XROOTD-L Home

XROOTD-L Home

XROOTD-L  August 2004

XROOTD-L August 2004

Subject:

Re: xrootd meeting - Tuesday, 17 August, 2004

From:

Fons Rademakers <[log in to unmask]>

Date:

19 Aug 2004 13:27:52 +020019 Aug 2004 13:27:52 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (144 lines)

Hi Andy,

 so when starting xrootd you specify the file space to be exported and
then you can only open files via full pathnames into that file space.
Correct?

Cheers, Fons.



On Wed, 2004-08-18 at 22:52, [log in to unmask] wrote:
> Hi Fons,
> 
> Yes, the security heads here are rather strict. No default should expose any
> data is the general rule. So, the only thing left to export is /tmp. As Pete
> pointed out, you can simply specify the path on the command line. If you
> want to export your home directory, then saying "xrootd ~" is sufficent (the
> shell expands the tilde). In general, no relative paths are allowed. Xrootd
> even prohibits clients from using relative paths to access data.
> Historically, that proved to be the easiest way of getting to data that you
> weren't supposed to get to.
> 
> Andy
> 
> ----- Original Message ----- 
> From: "Peter Elmer" <[log in to unmask]>
> To: "Fons Rademakers" <[log in to unmask]>
> Cc: <[log in to unmask]>; <[log in to unmask]>;
> <[log in to unmask]>; "Alvise Dorigo" <[log in to unmask]>;
> "Fulvio Galeazzi" <[log in to unmask]>; "Andrew Hanushevsky"
> <[log in to unmask]>; "Jean-Yves Nief" <[log in to unmask]>; "Akram Khan"
> <[log in to unmask]>; "Guglielmo De Nardo" <[log in to unmask]>;
> "Gerardo Ganis" <[log in to unmask]>
> Sent: Wednesday, August 18, 2004 5:39 AM
> Subject: Re: xrootd meeting - Tuesday, 17 August, 2004
> 
> 
> > On Wed, Aug 18, 2004 at 02:25:49PM +0200, Fons Rademakers wrote:
> > > Yes, I get an error message from TXUrl. Gerri can you maybe check this
> > > and fix it so that localhost works again in the rootd url?
> > >
> > > Other question, how do I start xrootd so that is assumes relative paths
> > > to start in the users home directory? Now default is /tmp.
> >
> >   Which user? The one which started xrootd or the one accessing files?
> >
> >   xrootd behaves differently that rootd in this respect. It doesn't assume
> > that paths start in /tmp by default, it only allows access to /tmp by
> default.
> > I've recently started to add some example configurations to describe some
> > things:
> >
> >   http://xrootd.slac.stanford.edu/examples/
> >
> > but the short answer is that you can export other area (e.g. like /data)
> with
> > either a line in the config file:
> >
> > xrootd.export /data
> >
> > or by starting xrootd as:
> >
> > xrootd /data
> >
> > I don't think it takes a "*" (obviously very insecure).
> >
> >   There is a separate option "oss.localroot" which allows for a _global_
> > server side prefix to all paths, i.e. a file at /mnt/temp/path/myfile.root
> > with:
> >
> > oss.localroot /mnt/temp
> >
> > will be accessed as
> >
> >    root://host:port//path/myfile.root
> >
> >   I'm not actually surt how it will behave for relative paths:
> >
> >    root://host:port/myfile.root                    *
> >
> > or for
> >
> >    root://host:port/~elmer/myfile.root
> >    root://host:port/~/myfile.root                  *
> >
> > This is what you are asking about, is that correct? Could you remind me
> > exactly what is done by rootd in the two cases marked with an "*"? (i.e.
> > relative path WRT what and "~" means which user?)
> >
> >                                    Pete
> >
> >
> >
> > > On Wed, 2004-08-18 at 11:24, Peter Elmer wrote:
> > > >   Hi Fons,
> > > >
> > > > On Tue, Aug 17, 2004 at 12:48:43PM +0200, Fons Rademakers wrote:
> > > > >   the rule in TFile::Open for opening via rootd currently is:
> > > > >
> > > > >     "If the url points to the localhost and the file will be opened
> in
> > > > >      readonly mode and the current user has read access or the
> specified
> > > > >      user is equal to the current user then open local TFile."
> > > > >
> > > > > This feature is specially important for PROOF where we access files
> > > > > always via rootd urls (so any worker can access any file) but where
> the
> > > > > packetizer optimizes the work so that the workers mostly will get
> local
> > > > > files. Using the above feature these local files will be opened
> directly
> > > > > as TFile's and won't go through rootd. To force a local file to be
> > > > > opened via rootd specify as host "localhost". If TXUrl this also
> > > > > supports then we will have the same behavior. If this "localhost"
> > > > > feature is supported by netx/xrootd then we can always use that as
> > > > > "backdoor" to test xrootd on the same machine as where the client
> runs.
> > > >
> > > >   Yes, the "localhost" option was in fact what Alvise and Fabrizio
> were
> > > > using themselves for this purpose. I've still not succeeded in
> building
> > > > the HEAD, but is the issue you are seeing related to the "in or out
> domain"
> > > > checks? That is what I was seeing with the last XTNetFile version
> before
> > > > they began the migration to TXNetFile.
> >
> >
> > -------------------------------------------------------------------------
> > Peter Elmer     E-mail: [log in to unmask]      Phone: +41 (22) 767-4644
> > Address: CERN Division PPE, Bat. 32 2C-14, CH-1211 Geneva 23, Switzerland
> > -------------------------------------------------------------------------
> >
-- 
Org:    CERN, European Laboratory for Particle Physics.
Mail:   1211 Geneve 23, Switzerland
E-Mail: [log in to unmask]              Phone: +41 22 7679248
WWW:    http://www.rademakers.org/fons/      Fax:   +41 22 7679480



Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

June 2024
May 2024
April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
July 2009
June 2009
May 2009
April 2009
March 2009
January 2009
December 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004

ATOM RSS1 RSS2



LISTSERV.SLAC.STANFORD.EDU

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager

Privacy Notice, Security Notice and Terms of Use