In that case, maybe it is better to put something like:
all.adminpath=/var/spool/xrootd
all.pidpath=/var/run/xrootd
in /etc/xrootd/xrootd-clustered.cfg
Otherwise, with the default location in /tmp, the /etc/init.d/xrootd setup will break if one changes the user/group of xrootd.
regards,
Wei Yang | [log in to unmask] | 650-926-3338(O)
On Jun 6, 2011, at 12:19 AM, Andrew Hanushevsky wrote:
> Ho Wei,
>
> No they cannot be. The -s option is there only for the init script so that
> it knows the pid id without having to parse the config file. Other parts
> of the system that rely on the config file to figure out where the pid
> file is do not know anything about the -s option. The -s should be
> treated as an internal option only not to be used by anyone but the init
> script.
>
> Andy
>
> On Sun, 5 Jun 2011, Yang, Wei wrote:
>
>> It seems when -s option is specified, xrootd/cmsd each creates two pid files:
>>
>> 1. a pid file at the path specified by -s option.
>> 2. a pid file at the path specified by all.adminpath (default is /tmp). here, the pid file for cmsd contains extra info about the cluster.
>>
>> Can these be consolidated? I especially want the -s option to overwrite all.adminpath so that we can define pid files in /etc/sysconfig/xrootd. and have "/etc/init.d/{xrootd,cmsd} setup" able to change the ownership.
>>
>> For admin path, there is no command line option. So one has to specified all.adminpath in the configuration file if the default (/tmp) is not acceptable. We should remind users to put the in /var/spool/xrootd, etc.
>>
>>
>> regards,
>> Wei Yang | [log in to unmask] | 650-926-3338(O)
>>
>>
>>
>>
>>
