The need for rebooting the xrootd / olbd services

[pfernandez]

Hi,

Does anybody know if, after a change in either xpd.cf or proof.conf files, any of the daemons (xrootd or olbd) should be restarted? I’ve read somewhere it’s not necesary, but I wanted to be sure if that’s the case with all the possible directives.

I imagine there’s no way of rebooting the servers without killing active sessions, right?

Thanks,
Pablo

[ganis]

Hi,

Does anybody know if, after a change in either xpd.cf or proof.conf files, any of the daemons (xrootd or olbd) should be restarted? I’ve read somewhere it’s not necesary, but I wanted to be sure if that’s the case with all the possible directives.

Changes are automatically picked-up: this works fine for ‘proof.conf’ but for ‘xpd.cf’ it may lead to hangs.

I imagine there’s no way of rebooting the servers without killing active sessions, right?

Right.
Support for sessions resiliance to xrootd reboots is planned but not yet there.

Gerri