On Tue, May 08, 2012 at 05:55:38PM -0400, Leo Razoumov wrote: > On Tue, May 8, 2012 at 4:09 PM, Lluís Batlle i Rossell <vi...@viric.name> > wrote: > > On Tue, May 08, 2012 at 01:04:08PM -0700, Matt Welland wrote: > >> On Tue, May 8, 2012 at 10:58 AM, Lluís Batlle i Rossell > >> <vi...@viric.name>wrote: > >> > fossil uses "ssh -T", which disables pty creation. But it should use "ssh > >> > host > >> > command", for the reasons I exposed in the just sent letter. :) > >> > > >> > >> This is actually what I originally assumed fossil was doing under the hood, > >> i.e. something like "ssh host fossil http". I'd like to experiment with > >> that possibility but is it a dead end? I.e. is there some reason why it > >> will never work? > > > > If I understand all right, it will fail to work for people that put their > > fossil > > binary into "~/bin", and their "~/bin" is loaded only by *login* startup > > scripts. And it will fail for people that have stdout messages in their > > *non-login* startup scripts. > > > > Not quit right. According to the sshd (8) man page a ssh login > sequence is as follows: > > 9. Runs user's shell or command.
If I add "echo a" at the top of my .bashrc, I see this: $ ssh localhost echo 1 a 1 And I can run "ssh localhost ulimit" fine. So ssh does not run the user command, but the user shell + its rc script + command. If it where not so, it wouldn't be possible to run: ssh host "cat < file" But I don't know why the sshd man page does not say that though. :) Regards, Lluís. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
