Date: Wed, 29 Mar 1995 12:36:32 +1000 From: Stephen McKay <syssgm@devetir.qld.gov.au> To: Mark Murray <mark@grondar.za> Cc: Poul-Henning Kamp <phk@ref.tfs.com>, syssgm@devetir.qld.gov.au, freebsd-current@FreeBSD.org Subject: Re: To all the ctm'mers... Message-ID: <199503290236.MAA29753@orion.devetir.qld.gov.au>
next in thread | raw e-mail | index | archive | help
Mark Murray <mark@grondar.za> writes:
>> > Sure. But _where_? Where does sendmail get a path from?
>>
>> I use this:
>> ctm-cvs-cur: "| PATH=$PATH:/usr/sbin /usr/sbin/ctm_rmail -l /archive/CTM_m
>ail
>> /log -p /archive/CTM_mail -d /archive/CTM -b /home/ncvs"
>>
>> and it works, but is gross...
>>
>> I belive ctm_rmail should use an absolute path to the ctm program.
>
>How about assuming that ctm is in the same directory as ctm_rmail?
[Disclaimer: I've lost 4 days mail due to a tragic error, so I've missed the
start of this. I haven't found the mail archives either. FAQ maintainer,
wherefor art thou?]
As the ctm_rmail author, and the person who made Poul remove the absolute path
to ctm, I should explain myself. I think it is a trivial matter to arrange
for the PATH to be correct, and a non-trivial matter to change a builtin
pathname. I actually run the ctm system on a non-FreeBSD box (and NFS mount
the result to a test FreeBSD box), and therefore see the added flexibility
as well worth it.
My incoming mail situation isn't simple: my .forward calls MH slocal
which runs through my .maildelivery which calls /usr/syssgm/bin/ctm_incoming
which does the hard work.
So, translating, someone like yourself could use an entry in /etc/aliases:
ctm-cvs-cur: "| /foo/bar/ctm_incoming"
and have /foo/bar/ctm_incoming contain something like:
#! /bin/sh
PATH="your favourite path"
export PATH
cd /place/for/goodies || exit 1
exec ctm_rmail -f -l log -p pieces -d deltas -b /current/src
Now, that wasn't too hard, was it? :-)
Stephen.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199503290236.MAA29753>