 |
 |
> IIRC, Xrootd 4.9 allows config.d-style directories. That would allow a packager drop-in a override of the `all.adminpath` without having to do this inside systemd configs. well, thats a very good news but is somehow beside the point i try to make. i was trying to make an argument that any service should also have a cli switch to specify the location of runtime generated files (pid, sockets etc...). adminpath is such a location and IMHO the service should have an cli option to specify it. > > I agree on the comment about splitting out persistent-vs-transient files, but that seems to be a completely different ticket, no? yes, that would be another issue, but i think a lot more complex than to add an "-a adminpath" (-s for pidfile was taken) as argument of xrootd/cmsd > What are you trying to fix, exactly? The fact that the various admin files appear to be incorrectly placed? well, the issue of redundant (and inconsistent) contents of adminpath is another thing. i am just trying to ask a feature that consist of an argument of executable that would set the location of the sockets used by the service... Thank you! -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/803#issuecomment-428167860 ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the XROOTD-DEV list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1