 |
 |
The details of what files are created anw where they are created can be found here: http://xrootd.org/doc/dev44/xrd_config.htm#_Toc448774978 In case that is not clear (and please let me know if it's not), some comments: 1) Unable to create home directory The home directory is whatever the current working directory is at start-up. If the '-n' option was specified, then a directory with the name matching the '-n' argument is created in that directory and xrootd makes it the home directory. This is part of automatic fencing which allows you to trivially run multiple xrootd's on the same machine. Fencing is described here: http://xrootd.org/doc/dev44/xrd_config.htm#_Toc448774975 In this case, it appears that a) the current working directory was "/" (bad idea) and "-n clustered" was specified as an argument. Obviously, one cannot create directories in "/" unless you are root. 2) Unable to create envfile The envfile is a file that contains the information about the running environment and can be used by external scripts to locate various adminitrative files xrootd creates. Where it's placed depends on what was specified by the pidpath directive (if any), the "-s" command line option option (is specified), and "-n" option. Whatever you specify the last component of that path (e.g. xrootd in this case) needs to have owner rwx permisions and be owned by the userid running the daemon. This seems to not have been the case here. Whether you shoose /var/runxrootd or /var/spool/xrootd is a site preference as xrootd doesn't care. In general, all directories you specify in the config file or command line options must be owned by xrootd with user permissions set to rwx (i.e. the last component). I am closing this ticket since it's not a bug but a configuration problem on how the directories were setup. If you feel otherwise, please re-open the thicket and let me know what you think is the endemic xrootd-specific problem here. --- 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/365#issuecomment-219145506 ######################################################################## 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