With any program that requires many configuration options be set, I have a
habit of just creating an 'ops' script. For sqwebmail, it's 'sqopts', and it
looks like this currently:
./configure \
--with-authshadow \
--without-authldap \
--without-authpwd \
--without-authpam \
--without-authuserdb \
--without-authvchkpw \
--without-authmysql \
--without-authldap \
--without-authdaemon \
--with-db=gdbm \
--enable-https=auto \
--enable-hardtimeout=86400 \
--enable-webpass=no \
--enable-softtimeout=86400 \
--enable-autopurge=5 \
--enable-maxpurge=14 \
--with-htmllibdir=/usr/local/sqwebmail \
--enable-imagedir=/usr/local/apache/cgi-bin/webmail \
--enable-cgibindir=/usr/local/apache/cgi-bin \
--enable-mimetypes=/usr/local/apache/conf/mime.types \
--with-maxargsize=100000000 \
--with-maxformargsize=100000000 \
--with-maxmsgsize=250000000 \
--with-ispell=/usr/local/bin/ispell
so when I run it, it takes care of all the options, and i have a tidy record
of exactly what I used when building it, which facilitates upgrading to
newer versions by just fine-tuning the file.
Sam Varshavchik writes:
> Benny Askham-S�rensen writes:
>
>> Hi.
>>
>> When I originally installed sqwebmail Ispent some time playing around
>> with various config options, before finally decding which to use.
>>
>> Now I need to change an option, but I am unsure of exactly how I ended up
>> configuring the system.
>>
>> Is there a way to figure out which config options where used on the
>> running system?
>>
>> Perhaps in a file somewhere in the build tree?
>
>
> Yes. config.status.
>
>
> --
> Sam
>
---------------------------------
Paul Theodoropoulos
[EMAIL PROTECTED]
Senior Unix Systems Administrator
Syntactically Subversive Services, Inc.
http://www.anastrophe.net
Downtime Is Not An Option
