Adding two cents here... while I can "fix" the proxy start-up (in a rather
internally ugly way) this is just the tip of the iceberg. I can foresee
cases (and they probably exist already) where a seemingly benign plugin
requires some information from a server in Novosibirsk to complete
initialization and the whole system hangs simply because that server is not
available. Things seem to be written this way because rarely one thinks that
start-up will be a serial process. And, in fact, it shouldn't be. So, to me
it's a clear case of forcing a square peg into a round hole; just because.
Andy
-----Original Message-----
From: Lukasz Janyst
Sent: Monday, May 16, 2011 12:48 AM
To: Andrew Hanushevsky ; Brian Bockelman ; Lukasz Janyst ; Doug Benjamin ;
[log in to unmask]
Subject: [bug #82184] Problem for startup using /etc/init.d and proxy
services
Follow-up Comment #3, bug #82184 (project xrootd):
The System-V init procedure in Unix is and always has been serial. I don't
think it's a big deal though and Brian is right by saying that it can easily
be handled by managing more carefully which procedures are handled before
and
which are handled after the child process detaches from the parent (this
should be minor change that requires no modification to the general design
of
xrootd).
When everyone migrates to upstart (http://upstart.ubuntu.com/) one could
start thinking of migrating to an event based startup, but until then the
serial one needs to be supported.
_______________________________________________________
Reply to this item at:
<http://savannah.cern.ch/bugs/?82184>
_______________________________________________
Message sent via/by LCG Savannah
http://savannah.cern.ch/
|