On Wed, Jul 16, 2008 at 02:05:14PM -0700, Danek Duvall wrote:
> 
> You need two slashes after the hostname.  This is weird, but well
> established, ssh syntax.  If you specify one slash, then it's relative to
> your home directory.  If you specify two slashes, then it's relative to /.
> Obviously, the intuitive thing to do would be to use one fewer slash in
> each case, but you can't have zero slashes.  :)

Yep, that worked.  I guess all the examples on all the wikis assumed
relative paths to your home directory, which is not the case for the
internal gate machines.  I think it would be worth documenting this.

> This definitel shouldn't be mandatory, and it really shouldn't even be
> suggested except as a hacky workaround.  It's dangerous -- you can end up
> running untrusted code as yourself just by accessing someone else's
> mercurial workspace.

So what is the internal policy w.r.t. access to elpaso.eng?  The flag
day said to use NFS, but that seems to raise a few issues, and the
workarounds don't seem to be viable - either you have to put up with
annoying noise or you open yourself up to security risks.  Nor is it
obvious if refusing to run the gate's .hg stuff actually impacts
development.   Should we be exposing these gates over NFS at all?  I
assume the plan is to put the open portion of ON outside of SWAN, but at
least the closed version will have to have a home somewhere on SWAN.  

> It's gotta go stat the entire workspace (all the directories, at least) to
> make sure that nothing's changed.  If you use cadmium, it does as wx did,
> and keeps track of the files you're intentionally changing, and will give
> you that list very quickly.
> 
> One alternative is to get the inotify extension working with the
> appropriate subsystem on Solaris, but I've no idea how much work that is.

After editing a single file and switching to SSH, I now get the
following times:

        hg status:      14 seconds
        hg list:        29 seconds
        hg pdiffs:      41 seconds

I don't see how this is viable as an everyday development tool.

Thanks,

- Eric

--
Eric Schrock, Fishworks                        http://blogs.sun.com/eschrock

Reply via email to