On Sat, May 13, 2006 at 06:16:36PM -0500, Timothy Brownawell wrote: > On Sat, 2006-05-13 at 12:22 -0300, Jeronimo Pellegrini wrote: > > Hi. > > I just compiled usher, and started it: > > > > $ ./usher -m "mtn -kmy_key" -a 127.0.0.1:10000 usher.cfg > > It treats the -m argument as an executable name, not a command line. So > it'll be looking for an execuable named "mtn -kmy_key", not looking for > an execuable named "mtn" and giving the "-kmy_key" argument. Really I > should probably replace this argument with a line in the config file, > which could allow for this.
Ah. I see... > I see it needs better documentation. > > It finds a matching server by first looking for one with a correct > 'host' line. If there isn't a matching host line, then it looks for a > matching 'pattern' line. > > The 'host' line is matched as a prefix of the hostname that the client > is given to talk to, and the 'pattern' line is matched as a prefix of > the include pattern. In each case, it takes the longest one that > matches. > > Note that the 'pattern' line is a string prefix of the include pattern, > not a glob. > > Also, you still have to provide the pattern argument that the serve > command requires in the 'local' line. And since it sounds like this > argument is going away soon, I'm not going to have it try to guess it. Well, I can see lots of problems with what I was doing! > This might be fixed now. Yep. It doesn't crash anymore! :-) Thanks a lot, Tim! Right now I just need to find out why usher can't find the server, but it will eventually work. :-) J. _______________________________________________ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel