XROOTD-L Archives

Support use of xrootd by HEP experiments

XROOTD-L@LISTSERV.SLAC.STANFORD.EDU

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Adrian Sevcenco <[log in to unmask]>
Reply To:
Support use of xrootd by HEP experiments <[log in to unmask]>
Date:
Mon, 27 Feb 2017 17:32:48 +0200
Content-Type:
multipart/signed
Parts/Attachments:
text/plain (2889 bytes) , smime.p7s (2353 bytes)
On 02/25/2017 01:19 AM, Andrew Hanushevsky wrote:
> Hi Adrian,
Hi!

> We do try to minimize command line arguments that can come from the
> config file. However, certain information cannot come from the config
> file because it is needed way before the config file is read. For instance,
>
> -n established the instance and that is needed to create various
> directories at start-up time.
>
> -l establishedsthe log file and we reall need to write out errors we
> encounter before we even get to the config file.
>
> -s Well, that was put in there so that init_d could verify whether or
> not the server started and, while it can come from the config file,
> makes it easier to see what pid file should be checked by just looking
> at the init script.
>
> -b places the server in the background before the config file is read (I
> suppose that could come the config file), though using -b is a standard
> way of daemonizing servers.
>
> -d sets debugging at the earliest possible moment. Generally, one should
> not specify this option unless there is an aboslute reason to do so
> since it severly impacts server performance. Gentler tracing is
> available from the config file.

maybe a wrapper like this could be useful?
https://github.com/adriansev/alicexrd/blob/master/startXRD.sh

Thank you!
Adrian


>
> Andy
>
> On Sat, 25 Feb 2017, Adrian Sevcenco wrote:
>
>> Hi! We are starting the xrootd from a script like this :
>>
>> xrootd -n server -b $XRDDEBUG -l ${XRDRUNDIR}/logs/xrdlog -c
>> ${XRDCONFDIR}/server/xrootd.cf -s ${XRDRUNDIR}/admin/xrd_svr.pid
>>
>> cmsd   -n server -b $XRDDEBUG -l ${XRDRUNDIR}/logs/cmslog -c
>> ${XRDCONFDIR}/server/xrootd.cf -s ${XRDRUNDIR}/admin/cmsd_svr.pid
>>
>> this is kind of restrictive and the xrootd arguments change also
>> depending of the user that start the script or the normal system
>> service..
>>
>> are the exact correspondent of cli arguments in configuration format?
>> (i did not find so far)
>> i would like to have as single argument to xrootd the configuration file
>> and everything else to be set up in that configuration...
>>
>> I post this here first for a discussion before posting an enhancement
>> request issue on github.
>>
>> Thank you!!
>> Adrian
>>
>>
>> ########################################################################
>> Use REPLY-ALL to reply to list
>>
>> To unsubscribe from the XROOTD-L list, click the following link:
>> https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1
>>
>


-- 
----------------------------------------------
Adrian Sevcenco, Ph.D.                       |
Institute of Space Science - ISS, Romania    |
adrian.sevcenco at {cern.ch,spacescience.ro} |
----------------------------------------------


########################################################################
Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1


ATOM RSS1 RSS2