 |
 |
On Mar 14, 2011, at 4:55 AM, Lukasz Janyst wrote: > Hi Brian, > > 2011/3/12 Brian Bockelman <[log in to unmask]>: >> Accordingly, in the separate packaging efforts of Lukasz and I, we have one one service per xrootd daemon: xrootd, cmsd, frm_purged, frm_xfrd. This, however, doesn't play nicely with multiple instances: it's not possible to have a server and a manager and a proxy all on one host. > > My scripts do support multiple instances of daemons. In the > sysconfig file you can define: XROOTD_SECOND_OPTIONS= and > XROOTD_THIRD_OPTIONS= or as many of them as you want and then you can > either add them to the XRD_INSTANCES list which makes it possible to > start them with classical: > > service xrootd start > > or you can just handle them by name: > > service xrootd start third second > service xrootd stop main > > The same goes for other daemons. > Ok, I missed that part. A few comments/questions: 1) Can you include an example of multiple instances in the sysconfig file? Even if it's commented out, it would be useful (if only for folks like me that didn't comprehend that multiple instances were supported in the first read-through). 2) Is this a correct description of the logic in xrootd.functions: - Each command (start/stop/status) is attempted once for each instance, regardless of the success with other instances. - Each command (start|stop|status) is successful only if each of the commands is successful. - For restart, the "start" command is attempted for all instances even if the "stop" command fails. ? If so, sounds good to me. Brian