On Mon, May 25, 2009 at 6:13 PM, Erik Wickstrom <e...@erikwickstrom.com> wrote: > Finally found it -- it was mesg in ~/.profile. I was just looking in > .bashrc... > > It's been a long weekend! :-)
Glad you found it, at any rate! Interesting that it's enabled in profiles by default. In my experience, most folks who need to talk between terminals just use 'talk', which can be invoked at any time and doesn't need to be "activated". Learn something new every day. I should probably start an FAQ for things like this, as it's bound to come up again in the future, if (I assume) rarely. Will make a note :) -Jeff > On Mon, May 25, 2009 at 10:46 AM, Christian Vest Hansen > <karmazi...@gmail.com> wrote: >> >> On Mon, May 25, 2009 at 6:45 PM, Erik Wickstrom <e...@erikwickstrom.com> >> wrote: >> > I haven't tried the "-i" option because of the side effects Jeff >> > mentioned. >> > I've had one hell of a time trying to find the item in my .bashrc file >> > (as >> > well as /etc/profile, /etc/bash*) -- nothing I remove seems to do the >> > trick. >> > >> > However if I login with a non-root account it seems to work without the >> > error. >> >> Hmm.... one would typically log in with a normal user and then sudo from >> there. >> >> Perhaps you have something in you /root/.profile or /root/.bashrc files? >> >> > >> > Erik >> > >> > On Mon, May 25, 2009 at 12:24 AM, Christian Vest Hansen >> > <karmazi...@gmail.com> wrote: >> >> >> >> A bit curious here. >> >> >> >> Erik, does adding -i change anything for you? I would have expected >> >> that the output pipes were inherited from the environment that we use >> >> to execute bash with in the first place, and that these somehow aren't >> >> ttys when we use SSH commands instead of SSH shell. >> >> >> >> On Mon, May 25, 2009 at 5:07 AM, Jeff Forcier <j...@bitprophet.org> >> >> wrote: >> >> > Hi Erik, >> >> > >> >> > Did a quick google and it sounds like you've got something in your >> >> > bashrc or other RCfile that expects an interactive shell, which >> >> > Fabric >> >> > doesn't do by default (it does a noninteractive login shell). >> >> > >> >> > See for example >> >> > http://platonic.techfiz.info/2008/10/13/stdin-is-not-a-tty/ . >> >> > >> >> > So there's two ways you can address this: >> >> > >> >> > * Figure out what the offending program is in your shell RCfile and >> >> > remove it or wrap it in an if statement that ensures it only runs if >> >> > the shell is in fact interactive; >> >> > * In your fabfile, tweak env.shell so that it says e.g. "/bin/bash >> >> > -li >> >> > -c" instead of "/bin/bash -l -c" (i.e. add a -i argument so that it's >> >> > interactive too). I don't recommend this since it may well introduce >> >> > other oddball side effects (using -i isn't, to my knowledge, well >> >> > tested), but it's an option; >> >> > >> >> > Best, >> >> > Jeff >> >> > >> >> > On Sun, May 24, 2009 at 10:47 PM, Erik Wickstrom >> >> > <e...@erikwickstrom.com> wrote: >> >> >> Hi, >> >> >> >> >> >> When I run a command on a remote host, Fabric always has this err. >> >> >> Do >> >> >> I >> >> >> have something mis-configured? >> >> >> >> >> >> [...@domain.com] run: cd /home/clm/crs/; git pull origin master >> >> >> [...@domain.com] err: stdin: is not a tty >> >> >> [...@domain.com] out: Already up-to-date. >> >> >> >> >> >> Thanks! >> >> >> Erik >> >> >> >> >> >> _______________________________________________ >> >> >> Fab-user mailing list >> >> >> Fab-user@nongnu.org >> >> >> http://lists.nongnu.org/mailman/listinfo/fab-user >> >> >> >> >> >> >> >> > >> >> > >> >> > _______________________________________________ >> >> > Fab-user mailing list >> >> > Fab-user@nongnu.org >> >> > http://lists.nongnu.org/mailman/listinfo/fab-user >> >> > >> >> >> >> >> >> >> >> -- >> >> Venlig hilsen / Kind regards, >> >> Christian Vest Hansen. >> > >> > >> >> >> >> -- >> Venlig hilsen / Kind regards, >> Christian Vest Hansen. > > _______________________________________________ Fab-user mailing list Fab-user@nongnu.org http://lists.nongnu.org/mailman/listinfo/fab-user
