Re: 2.4.0.Beta1 available

From: Steve Jenkins <stevejenkins_at_gmail.com>
Date: Sun, 5 Jun 2011 12:13:23 -0400

On Tue, May 10, 2011 at 10:50 AM, Murray S. Kucherawy <msk_at_cloudmark.com> wrote:
>> -----Original Message-----
>> From: opendkim-dev-bounce_at_lists.opendkim.org [mailto:opendkim-dev-bounce_at_lists.opendkim.org] On Behalf Of Steve Jenkins
>> Sent: Monday, May 09, 2011 9:42 PM
>> To: Murray S. Kucherawy
>> Cc: opendkim-dev_at_lists.opendkim.org
>> Subject: Re: 2.4.0.Beta1 available
>>
>> Thanks, Murray. This compiles MUCH better on RedHat flavors that don't
>> have libmemcached installed. :)
>>
>> Can someone help me understand what all the different files in the
>> contrib/init/redhat/ dir are for? I copied the plain "opendkim" file
>> from that dir to /etc/init.d/ but then noticed the config file
>> location line had been changed to /usr/local/etc/opendkim.conf instead
>> of /etc/opendkim.conf. My original version of this startup script had
>> the conf just in /etc/. Is there a preference (or a standard practice
>> I'm probably unaware of) to put the conf file in /usr/local/etc/
>> instead?
>
> The new script uses values provided by ./configure, i.e., it's auto-generated based on autoconf options.  The source form can be found in contrib/init/redhat/opendkim.in where it uses the --prefix value to build the path.
>
> I had --sysconfdir in there too, but that produces something like ${prefix}/etc, and ${prefix} isn't defined so that didn't work.  So maybe the simplest solution is to import ${prefix} first so that does work, and then your script will be generated to match your configuration.  So if you do:
>
>        ./configure --sysconfdir=/etc --prefix=/usr/local
>
> ...then you should get binaries in /usr/local/sbin and opendkim.conf in /etc.
>
> I'll send you a replacement Makefile.in offlist to try.
>

I'm actually testing with Beta 6, but wanted to reply to this thread
for context. I realize that Daniel prefers to build RPMs, but I'd
still like to think there's a straightforward method to be able to do
"configure, make, make install" and then copy the RedHat init script
to the appropriate directory and it just WORKS. However, even with the
configure options you mentioned above, Murray, if I copy the default
init script to /etc/init.d/ and try to start OpenDKIM I get this
error:

Jun 3 15:44:36 tapper opendkim[25590]: can't write pid to
/usr/local/var/run/opendkim/opendkim.pid: No such file or directory
Jun 3 15:44:36 tapper opendkim[25591]: OpenDKIM Filter v2.4.0
starting (args: -x /etc/opendkim.conf -P
/usr/local/var/run/opendkim/opendkim.pid)

The only way to get things working properly again is to use my default
init script (which is the same as the last version I submitted).

Again, I'm way more script-kiddie than programmer, so maybe I'm
missing something. When ./configure is run with those options, does
that affect the startup script? Or does it affect the location that
the binaries get copied to? Why was the prefix support stuff added in
the first place? Is it because the "roll your own RPM and install it"
method sticks the files in different locations than the "configure,
make, make install" method?

SteveJ
Received on Sun Jun 05 2011 - 16:13:39 PST