On Thu, Oct 8, 2009 at 4:59 PM, Michael <[email protected]> wrote: > On Thu, Oct 08, 2009 at 03:30:26PM -0400, Woodchuck wrote: >> On Thu, Oct 8, 2009 at 3:04 PM, Michael <[email protected]> wrote: >> > I can't get lbdbq to work alone, inside mutt, or with lbdb-fetchaddr. Here >> > is what I get when I type "lbdbq mike": >> > ksh: lbdbq: No such file or directory >> >> This tells me that lbdbq is not in your PATH. >> >> echo $PATH and see if /usr/local/bin is part of PATH. >> >> The failure in the .procmailrc may be part of the same problem. >> >> My habit is to put full pathnames in such scripts, >> such as >> >> :0hc >> | /usr/local/bin/lbdb-fetchaddr -a >> >> I hope it's this simple. >> >> Dave >> _______________________________________________ >> Openbsd-newbies mailing list >> [email protected] >> http://mailman.theapt.org/listinfo/openbsd-newbies > > Yes, it is. I forgot to show that part of my .profile: > echo $PATH > /home/mike/bin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin:/usr/local/bin:/usr/local/sbin:/usr/games:. > _______________________________________________
This PATH may not be active in jobs that are not started from an interactive shell -- procmail is one such type of job. .profile, I believe, is sourced only for interactive jobs, i.e. from a "login" shell. Try specifying the complete path names, or setting PATH in the scripts themselves, if this is allowed. I admit I'm guessing here. Anyone else have clues? Dave -- Caution, this account is hosted by gmail. Strangers scan the content of all mail transiting such accounts. _______________________________________________ Openbsd-newbies mailing list [email protected] http://mailman.theapt.org/listinfo/openbsd-newbies
