On 6 Feb, 08:26, Jamis Buck <[EMAIL PROTECTED]> wrote: > On Feb 5, 2007, at 2:32 PM, Erik Kastner wrote: > > > > > perfered is to edit your shell's startup scripts (.bash_login, > > .bash_profile, .profile, etc) to get them in your path AHEAD of > > /usr/bin and others. > > Well, that's preferred, only if your sshd is configured to load those > when spawning a shell. The problem is that most are not, by default. > Thus, the _actual_ preferred method is (c), adjust the :svn variable > so it points to where your svn lives. :) > > - Jamis
I've been following along. I had a similar problem last year. For posterity's sake and those of us that are not experienced sysadmins here's what I did on an XServe: I added the appropriate $PATH to ~/.ssh/environment on the app server and then edited /etc/sshd_config (again on the app server) to set 'PermitUserEnvironment yes' (uncommented that line, add it if your sshd_config does not have it.) This may help you use tools other than svn successfully with capsitrano. Tom > > > > > On 2/5/07, CK <[EMAIL PROTECTED]> wrote: > > >> I found (and fixed) the problem on my end. And I have to admit it was > >> *not* related to date. If I had looked further up I would have seen > >> the following clear error message: > > >> ** [out :: app] bash: line 2: svn: command not found > > >> The problem was related to the path configuration. To be more > >> specific, all the tools (svn, rake, ...) were installed in /usr/ > >> local/ > >> bin folder, which was not in the path. > > >> Options to fix the problem are: > > >> a) Add /usr/local/bin to path. > >> b) Put tools into folder that is in path > >> c) Adjust capistrano deployment recipe variable (set :svn, "/path/to/ > >> svn") > > >> Please feel free to add any opions that I might have missed or > >> suggest > >> the 'prefered' solution. > > >> On Feb 5, 12:31 pm, "CK" <[EMAIL PROTECTED]> wrote: > >>> To add more to the confusion, I tried the same on my trusty MacMini > >>> running Mac OS 10.4 too, and it works fine! > > >>> Since I have a system that show that behavior (and ones that does > >>> not :)), I'll try to investigate further. Any suggestions what to > >>> look > >>> for is greatly appreciated. > > >>> On Feb 5, 10:07 am, Jamis Buck <[EMAIL PROTECTED]> wrote: > > >>>> Very interesting. I'm afraid I don't have an OS X Server > >>>> instance to > >>>> play with, so I can't duplicate this. Anyone want to try and dig in > >>>> to figure out what's going on? > > >>>> - Jamis > > >>>> On Feb 5, 2007, at 6:10 AM, CK wrote: > > >>>>> I have the same strange thing happening on my system. > > >>>>> If I run 'cap datetest': > > >>>>> task :datetest, :roles => :app do > >>>>> run "echo `date +\"%Y-%m-%d %H:%M:%S\"` $USER 6 20070205130022" > >>>>> end > > >>>>> with :app being the (remote) application server (Apple OS X Server > >>>>> 10.4 - Darwin Kernel Version 8.8.4) it works fine: > > >>>>> * executing task datetest > >>>>> * executing "echo `date +\"%Y-%m-%d %H:%M:%S\"` $USER 6 > >>>>> 20070205130022" > >>>>> servers: ["app"] > >>>>> [app] executing command > >>>>> ** [out :: app] 2007-02-05 08:06:52 ck 6 20070205130022 > >>>>> command finished > > >>>>> But if I run 'cap cold_deploy' or 'cap deploy' for that matter, it > >>>>> fails as described above. > > >>>>> Executing 'run "echo $SHELL"' reveals that it uses > > >>>>> ** [out :: app] /bin/bash > > >>>>> Any suggestions are welcome. > > >>>>> On Feb 4, 5:25 pm, Jamis Buck <[EMAIL PROTECTED]> wrote: > >>>>>> David, > > >>>>>> What shell are you using on the OS X server? Also, what > >>>>>> version of > >>>>>> OS X? > > >>>>>> I just created a simple capfile to test this with: > > >>>>>> role :local, "localhost" > >>>>>> task :datetest do > >>>>>> run "date +\"%Y-%m-%d %H:%M:%S\"" > >>>>>> end > > >>>>>> And running it seems to work fine on my OS X machine: > > >>>>>> pemba> cap datetest > >>>>>> * executing task datetest > >>>>>> * executing "date +\"%Y-%m-%d %H:%M:%S\"" > >>>>>> servers: ["localhost"] > >>>>>> [localhost] executing command > >>>>>> ** [out :: localhost] 2007-02-04 15:24:13 > >>>>>> command finished > > >>>>>> - Jamis > > >>>>>> On Feb 3, 2007, at 7:40 PM, David Bock wrote: > > >>>>>>> I have a project that has been deploying successfully to a linux > >>>>>>> box for months. I am now trying to deploy it to an OS X server, > >>>>>>> and I am getting a problem on the update command in > >>>>>>> particular. I > >>>>>>> have created the simplest thing that could possibly work, and > >>>>>>> I can > >>>>>>> successfully reproduce the problem. > > >>>>>>> First problem: > >>>>>>> When trying to run update to the mac server, the command echoed > >>>>>>> back from the server has escaped the '\n' characters so that > >>>>>>> they > >>>>>>> are '\\\n', and the command syntax is hosed. > > >>>>>>> So I copy the command, tweak it by hand, and then I get the > >>>>>>> second > >>>>>>> problem... the date command, which looks like this in the cap > >>>>>>> output: > > >>>>>>> date +\"%Y-%m-%d %H:%M:%S\" > > >>>>>>> come back with: > > >>>>>>> date: illegal time format > > >>>>>>> Given that I have been able to reproduce this problem on two > >>>>>>> different macs with two different projects (one of which has the > >>>>>>> simplest deploy.rb that could possibly work), I'm at a loss > >>>>>>> as to > >>>>>>> how to fix this, or why I haven't been able to find other people > >>>>>>> experiencing the same problem. > > >>>>>>> and suggestions for resolving either of these issues? > > >>>>>>> Thanks, > > >>>>>>> -db --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
