On Jun 20, 2007, at 1:54 AM, Murali Vilayannur wrote:
Hi Sam,
I see..So do you wish that we fallback to parsing from server config
file if that were to be specified in place of a server-alias string in
command line..
That shouldn't be too hard, no?
Hmm...well if the server config file isn't specified, why can't the
server just get the hostname instead of requiring an alias?
Yeah I was thinking that if a server config was specified as the
second argument to the pvfs2-server, the server would go ahead and
use those values for endpoint, storage location, logfile, etc.
Any updates on what the current stance on zero-conf based server
startups, i.e. is there still any interest and/or preferred
approaches? :)
Definitely still interest. I'm not sure we've come up with an
approach yet. I would argue a first step toward zero conf would be
encoding/decoding the config using the lebf encoding layer. This
would give us a more efficient representation of the config, as well
as make it easier to modify at runtime.
-sam
thanks,
Murali
On 6/19/07, Sam Lang <[EMAIL PROTECTED]> wrote:
Hi Murali,
Just never got around to commit it. My only complaint is that it
doesn't allow the server to optionally take a server config file (for
legacy scripts, etc.). I think that might be hard to implement
though...
-sam
On Jun 20, 2007, at 1:19 AM, Murali Vilayannur wrote:
> Hey Sam,
> Any interest in merging this patch to unify config files while
> starting up pvfs2 servers?
> I have reworked it against HEAD..
> Relevant thread..
> http://www.beowulf-underground.org/pipermail/pvfs2-developers/2007-
> February/003209.html
> thanks,
> Murali
> <unify-config-files.patch>
_______________________________________________
Pvfs2-developers mailing list
Pvfs2-developers@beowulf-underground.org
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
