[jp] Fixing A Broken Jpilot Installation

  • Previous message: [jp] Fixing A Broken Jpilot Installation
  • Next message: [jp] Fixing A Broken Jpilot Installation
  • Rich Shepard rshepard at appl-ecosys.com
    Mon Aug 7 20:06:26 EDT 2006

     

    On Mon, 7 Aug 2006, Judd Montgomery wrote:
    
    > MALOC_CHECK_=0 only ignores the problem.
    
    Judd,
    
       That's very true. But, ... it loads and allows me to use it. Until the
    Xrms developers get around to supporting postgres as well as mysql, my sales
    administration tools are jpilot and pine.
    
    > I know the exact offensive line of code now and can research it.
    
       Cool!
    
    > You had to specify /usr/bin/jpilot because the bash directory hash (yes,
    > the bash hash) knew about /usr/local/bin/jpilot already.  A "hash -r"
    > would have fixed that up, as well as opening a new shell would have.
    
       I never knew there was a bash hash. We users usually make a hash of our
    systems, however.
    
       Regardless, I thought the bash search path was /usr/local/bin, /usr/bin,
    /bin. So, regardless of directory hashes, if the binary is not in the first
    directory it would find it in the second one. I guessed wrong.
    
    Many thanks,
    
    Rich
    
    -- 
    Richard B. Shepard, Ph.D.               |    The Environmental Permitting
    Applied Ecosystem Services, Inc.(TM)    |            Accelerator
    <http://www.appl-ecosys.com>     Voice: 503-667-4517      Fax: 503-667-8863
    
    

     

     

    More information about the jpilot mailing list