Menu
▾
▴
sqlgrey-users
|
From: Steve M. <st...@pl...> - 2010-01-31 16:56:45
|
I get the following error when trying to install the latest sqlgrey. MacOS X 10.5.8. mail2:sqlgrey-1.8.0-rc1 cheezmo$ sudo make install perldoc -u sqlgrey | pod2man -n sqlgrey > sqlgrey.1 sed -i 's/^my $VERSION = .*;/my $VERSION = "1.8.0-rc1";/' sqlgrey sed: 1: "sqlgrey": unterminated substitute pattern make: *** [update-version] Error 1 -- Steve Martin st...@pl... |
|
From: Richard <in...@ri...> - 2010-01-31 19:56:57
|
Steven, Have you tried these instructions? http://diymacserver.com/installing-the-mailserver/setting-up-greylisting-with-sqlgrey/ They worked for me. Richard On 31 Jan 2010, at 5:40 PM, Steve Martin wrote: > I get the following error when trying to install the latest sqlgrey. MacOS X 10.5.8. > > > mail2:sqlgrey-1.8.0-rc1 cheezmo$ sudo make install > perldoc -u sqlgrey | pod2man -n sqlgrey > sqlgrey.1 > sed -i 's/^my $VERSION = .*;/my $VERSION = "1.8.0-rc1";/' sqlgrey > sed: 1: "sqlgrey": unterminated substitute pattern > make: *** [update-version] Error 1 > > -- > Steve Martin > st...@pl... > > > > ------------------------------------------------------------------------------ > The Planet: dedicated and managed hosting, cloud storage, colocation > Stay online with enterprise data centers and the best network in the business > Choose flexible plans and management services without long-term contracts > Personal 24x7 support from experience hosting pros just a phone call away. > http://p.sf.net/sfu/theplanet-com > _______________________________________________ > Sqlgrey-users mailing list > Sql...@li... > https://lists.sourceforge.net/lists/listinfo/sqlgrey-users > |
|
From: Steve M. <st...@pl...> - 2010-01-31 20:08:13
|
Yes, in fact I've had a working install of 1.7.6 for some time. The problem is when I get here... -- If youve downloaded SQLGrey from sourceforge please unpack it and ‘cd’ into the directory and run the following commands: make sudo make install -- The "sudo make install" fails as I described. On Jan 31, 2010, at 1:39 PM, Richard wrote: > Steven, > > Have you tried these instructions? > http://diymacserver.com/installing-the-mailserver/setting-up-greylisting-with-sqlgrey/ > > They worked for me. > > Richard > > On 31 Jan 2010, at 5:40 PM, Steve Martin wrote: > >> I get the following error when trying to install the latest sqlgrey. MacOS X 10.5.8. >> >> >> mail2:sqlgrey-1.8.0-rc1 cheezmo$ sudo make install >> perldoc -u sqlgrey | pod2man -n sqlgrey > sqlgrey.1 >> sed -i 's/^my $VERSION = .*;/my $VERSION = "1.8.0-rc1";/' sqlgrey >> sed: 1: "sqlgrey": unterminated substitute pattern >> make: *** [update-version] Error 1 >> >> -- >> Steve Martin >> st...@pl... >> >> >> >> ------------------------------------------------------------------------------ >> The Planet: dedicated and managed hosting, cloud storage, colocation >> Stay online with enterprise data centers and the best network in the business >> Choose flexible plans and management services without long-term contracts >> Personal 24x7 support from experience hosting pros just a phone call away. >> http://p.sf.net/sfu/theplanet-com >> _______________________________________________ >> Sqlgrey-users mailing list >> Sql...@li... >> https://lists.sourceforge.net/lists/listinfo/sqlgrey-users >> > > > ------------------------------------------------------------------------------ > The Planet: dedicated and managed hosting, cloud storage, colocation > Stay online with enterprise data centers and the best network in the business > Choose flexible plans and management services without long-term contracts > Personal 24x7 support from experience hosting pros just a phone call away. > http://p.sf.net/sfu/theplanet-com > _______________________________________________ > Sqlgrey-users mailing list > Sql...@li... > https://lists.sourceforge.net/lists/listinfo/sqlgrey-users > -- Steve Martin st...@pl... |
|
From: Richard <in...@ri...> - 2010-01-31 20:11:20
|
I had not tried the latest version, will take a look at it. If no one else finds the answer first ;-0 R On 31 Jan 2010, at 9:08 PM, Steve Martin wrote: > Yes, in fact I've had a working install of 1.7.6 for some time. The problem is when I get here... > > -- > If youve downloaded SQLGrey from sourceforge please unpack it and ‘cd’ into the directory and run the following commands: > > make > sudo make install > -- > > The "sudo make install" fails as I described. > > > On Jan 31, 2010, at 1:39 PM, Richard wrote: > >> Steven, >> >> Have you tried these instructions? >> http://diymacserver.com/installing-the-mailserver/setting-up-greylisting-with-sqlgrey/ >> >> They worked for me. >> >> Richard >> >> On 31 Jan 2010, at 5:40 PM, Steve Martin wrote: >> >>> I get the following error when trying to install the latest sqlgrey. MacOS X 10.5.8. >>> >>> >>> mail2:sqlgrey-1.8.0-rc1 cheezmo$ sudo make install >>> perldoc -u sqlgrey | pod2man -n sqlgrey > sqlgrey.1 >>> sed -i 's/^my $VERSION = .*;/my $VERSION = "1.8.0-rc1";/' sqlgrey >>> sed: 1: "sqlgrey": unterminated substitute pattern >>> make: *** [update-version] Error 1 >>> >>> -- >>> Steve Martin >>> st...@pl... >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> The Planet: dedicated and managed hosting, cloud storage, colocation >>> Stay online with enterprise data centers and the best network in the business >>> Choose flexible plans and management services without long-term contracts >>> Personal 24x7 support from experience hosting pros just a phone call away. >>> http://p.sf.net/sfu/theplanet-com >>> _______________________________________________ >>> Sqlgrey-users mailing list >>> Sql...@li... >>> https://lists.sourceforge.net/lists/listinfo/sqlgrey-users >>> >> >> >> ------------------------------------------------------------------------------ >> The Planet: dedicated and managed hosting, cloud storage, colocation >> Stay online with enterprise data centers and the best network in the business >> Choose flexible plans and management services without long-term contracts >> Personal 24x7 support from experience hosting pros just a phone call away. >> http://p.sf.net/sfu/theplanet-com >> _______________________________________________ >> Sqlgrey-users mailing list >> Sql...@li... >> https://lists.sourceforge.net/lists/listinfo/sqlgrey-users >> > > -- > Steve Martin > st...@pl... > > > > ------------------------------------------------------------------------------ > The Planet: dedicated and managed hosting, cloud storage, colocation > Stay online with enterprise data centers and the best network in the business > Choose flexible plans and management services without long-term contracts > Personal 24x7 support from experience hosting pros just a phone call away. > http://p.sf.net/sfu/theplanet-com > _______________________________________________ > Sqlgrey-users mailing list > Sql...@li... > https://lists.sourceforge.net/lists/listinfo/sqlgrey-users > |
|
From: Richard <in...@ri...> - 2010-02-01 00:52:23
|
Allright found the error but don't know how to solve it in the intended manner. Replace in the makefile this part: update-version: sed -i 's/^my $$VERSION = .*;/my $$VERSION = "$(VERSION)";/' sqlgrey sed -i 's/^%define ver .*/%define ver $(VERSION)/' sqlgrey.spec sed -i 's/^my $$VERSION = .*;/my $$VERSION = "$(VERSION)";/' sqlgrey-logstats.pl With the same code but not so elegant from an older version like 1.7.6: update-version: cat sqlgrey | sed 's/^my $$VERSION = .*;/my $$VERSION = "$(VERSION)";/' > sqlgrey.new mv sqlgrey.new sqlgrey chmod a+x sqlgrey cat sqlgrey.spec | sed 's/^%define ver .*/%define ver $(VERSION)/' > sqlgrey.spec.new mv sqlgrey.spec.new sqlgrey.spec cat sqlgrey-logstats.pl | sed 's/^my $$VERSION = .*;/my $$VERSION = "$(VERSION)";/' > sqlgrey-logstats.pl.new mv sqlgrey-logstats.pl.new sqlgrey-logstats.pl chmod a+x sqlgrey-logstats.pl I'm not an expert on sed but somehow the workings of sed on a Mac are different. That's why you can't get it installed. Hope this helps. Richard On 31 Jan 2010, at 9:10 PM, Richard wrote: > I had not tried the latest version, will take a look at it. If no one else finds the answer first ;-0 > > R > > On 31 Jan 2010, at 9:08 PM, Steve Martin wrote: > >> Yes, in fact I've had a working install of 1.7.6 for some time. The problem is when I get here... >> >> -- >> If youve downloaded SQLGrey from sourceforge please unpack it and ‘cd’ into the directory and run the following commands: >> >> make >> sudo make install >> -- >> >> The "sudo make install" fails as I described. >> >> >> On Jan 31, 2010, at 1:39 PM, Richard wrote: >> >>> Steven, >>> >>> Have you tried these instructions? >>> http://diymacserver.com/installing-the-mailserver/setting-up-greylisting-with-sqlgrey/ >>> >>> They worked for me. >>> >>> Richard >>> >>> On 31 Jan 2010, at 5:40 PM, Steve Martin wrote: >>> >>>> I get the following error when trying to install the latest sqlgrey. MacOS X 10.5.8. >>>> >>>> >>>> mail2:sqlgrey-1.8.0-rc1 cheezmo$ sudo make install >>>> perldoc -u sqlgrey | pod2man -n sqlgrey > sqlgrey.1 >>>> sed -i 's/^my $VERSION = .*;/my $VERSION = "1.8.0-rc1";/' sqlgrey >>>> sed: 1: "sqlgrey": unterminated substitute pattern >>>> make: *** [update-version] Error 1 >>>> >>>> -- >>>> Steve Martin >>>> st...@pl... >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> The Planet: dedicated and managed hosting, cloud storage, colocation >>>> Stay online with enterprise data centers and the best network in the business >>>> Choose flexible plans and management services without long-term contracts >>>> Personal 24x7 support from experience hosting pros just a phone call away. >>>> http://p.sf.net/sfu/theplanet-com >>>> _______________________________________________ >>>> Sqlgrey-users mailing list >>>> Sql...@li... >>>> https://lists.sourceforge.net/lists/listinfo/sqlgrey-users >>>> >>> >>> >>> ------------------------------------------------------------------------------ >>> The Planet: dedicated and managed hosting, cloud storage, colocation >>> Stay online with enterprise data centers and the best network in the business >>> Choose flexible plans and management services without long-term contracts >>> Personal 24x7 support from experience hosting pros just a phone call away. >>> http://p.sf.net/sfu/theplanet-com >>> _______________________________________________ >>> Sqlgrey-users mailing list >>> Sql...@li... >>> https://lists.sourceforge.net/lists/listinfo/sqlgrey-users >>> >> >> -- >> Steve Martin >> st...@pl... >> >> >> >> ------------------------------------------------------------------------------ >> The Planet: dedicated and managed hosting, cloud storage, colocation >> Stay online with enterprise data centers and the best network in the business >> Choose flexible plans and management services without long-term contracts >> Personal 24x7 support from experience hosting pros just a phone call away. >> http://p.sf.net/sfu/theplanet-com >> _______________________________________________ >> Sqlgrey-users mailing list >> Sql...@li... >> https://lists.sourceforge.net/lists/listinfo/sqlgrey-users >> > > > ------------------------------------------------------------------------------ > The Planet: dedicated and managed hosting, cloud storage, colocation > Stay online with enterprise data centers and the best network in the business > Choose flexible plans and management services without long-term contracts > Personal 24x7 support from experience hosting pros just a phone call away. > http://p.sf.net/sfu/theplanet-com > _______________________________________________ > Sqlgrey-users mailing list > Sql...@li... > https://lists.sourceforge.net/lists/listinfo/sqlgrey-users > |
|
From: Karl O. P. <ko...@me...> - 2010-02-01 03:04:05
|
On 01/31/2010 06:33:40 PM, Richard wrote:
> Allright found the error but don't know how to solve it in the
> intended manner.
>
> Replace in the makefile this part:
> update-version:
> sed -i 's/^my $$VERSION = .*;/my $$VERSION = "$(VERSION)";/'
> sqlgrey
> sed -i 's/^%define ver .*/%define ver $(VERSION)/'
> sqlgrey.spec
> sed -i 's/^my $$VERSION = .*;/my $$VERSION = "$(VERSION)";/'
> sqlgrey-logstats.pl
>
> With the same code but not so elegant from an older version like
> 1.7.6:
> update-version:
> cat sqlgrey | sed 's/^my $$VERSION = .*;/my $$VERSION =
> "$(VERSION)";/' > sqlgrey.new
> mv sqlgrey.new sqlgrey
> chmod a+x sqlgrey
> cat sqlgrey.spec | sed 's/^%define ver .*/%define ver
> $(VERSION)/' > sqlgrey.spec.new
> mv sqlgrey.spec.new sqlgrey.spec
> cat sqlgrey-logstats.pl | sed 's/^my $$VERSION = .*;/my
> $$VERSION = "$(VERSION)";/' > sqlgrey-logstats.pl.new
> mv sqlgrey-logstats.pl.new sqlgrey-logstats.pl
> chmod a+x sqlgrey-logstats.pl
Looks like sed -i isn't portable. It's probably a gnu extension.
You don't find it in openbsd's sed.
I'd say the makefile should be more portable.
How about?:
( ;# Run in a subshell just to cleanup early.
tfile=sqlgrey.$$
function cleanup () rm -f $tfile
trap cleanup EXIT
sed 's/^my $$VERSION = .*;/my $$VERSION =
"$(VERSION)";/' sqlgrey > $tfile \
&& cat $tfile > sqlgrey
sed 's/^%define ver .*/%define ver
$(VERSION)/' sqlgrey.spec > $tfile \
&& cat $tfile > sqlgrey.spec
sed 's/^my $$VERSION = .*;/my
$$VERSION = "$(VERSION)";/' sqlgrey-logstats.pl > $tfile \
&& cat $tfile > sqlgrey-logstats.pl
)
Note also that it's probably not a good idea to rely
on the file permissions in the tarball. The better
approach is to use the install program and set the
bits as desired on install. (But the above code
does preserve all permissions.) If this was cleaned
up I'd get rid of the whole $tfile thing and have
the input files named autoconf-ish: sqlgrey.in,
sqlgrey.spec.in, etc. and just sed right into the
target file (sqlgrey, sqlgrey.spec, etc.).
Karl <ko...@me...>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
|
|
From: Michal L. <ml...@lo...> - 2010-02-01 08:14:07
|
Karl O. Pinc wrote: > Looks like sed -i isn't portable. It's probably a gnu extension. I just tried to install sqlgrey on my HP-UX box and indeed there are more problems than just sed -i For instance the Makefile alone requires GNU make (gmake), the original HP-UX make didn't like it. How's it on Solaris? Do you guys install it with make or with gmake? A while later it fails on "install -d -m ...". Apparently my 'install' requires different options to GNU install. So ... do we aim to be completely installable without GNU tools? At the moment we're failing regardless whether I revert the change or not (I did, don't worry ;-) Michal |
|
From: Karl O. P. <ko...@me...> - 2010-02-01 16:54:03
|
On 02/01/2010 02:17:01 AM, Michal Ludvig wrote:
> Karl O. Pinc wrote:
>
> > Looks like sed -i isn't portable. It's probably a gnu extension.
>
> I just tried to install sqlgrey on my HP-UX box and indeed there are
> more problems than just sed -i
>
> For instance the Makefile alone requires GNU make (gmake), the
> original
> HP-UX make didn't like it.
> So ... do we aim to be completely installable without GNU tools?
IMO there's a difference between having to install something
like gmake, which does not overwrite anything in the existing
command namespace, and having to replace something like sed.
Karl <ko...@me...>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
|
|
From: LEVEAU S. <sta...@ac...> - 2010-02-03 17:13:34
|
Hello Is it possible to have a whitelist of user only with sqlgrey? User who does not want to be greylist Thank you in advance |
|
From: Winfried N. <win...@ne...> - 2010-02-03 17:31:41
|
Hi, put the email address of the use into the "optout_email" table and set "optmethod = optout" in your sqlgrey.conf Winni _____ From: LEVEAU Stanislas [mailto:sta...@ac...] Sent: Wednesday, February 03, 2010 6:13 PM To: SQLgrey users mailing-list Subject: [Sqlgrey-users] whitelist of user Hello Is it possible to have a whitelist of user only with sqlgrey? User who does not want to be greylist Thank you in advance |
|
From: LEVEAU S. <sta...@ac...> - 2010-02-04 10:40:36
|
ok thanks for your answer Stan Winfried Neessen a écrit : > Hi, > > put the email address of the use into the "optout_email" table and set > "optmethod = optout" > in your sqlgrey.conf > > > Winni > > ------------------------------------------------------------------------ > *From:* LEVEAU Stanislas [mailto:sta...@ac...] > *Sent:* Wednesday, February 03, 2010 6:13 PM > *To:* SQLgrey users mailing-list > *Subject:* [Sqlgrey-users] whitelist of user > > Hello > > Is it possible to have a whitelist of user only with sqlgrey? > User who does not want to be greylist > > Thank you in advance > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > The Planet: dedicated and managed hosting, cloud storage, colocation > Stay online with enterprise data centers and the best network in the business > Choose flexible plans and management services without long-term contracts > Personal 24x7 support from experience hosting pros just a phone call away. > http://p.sf.net/sfu/theplanet-com > ------------------------------------------------------------------------ > > _______________________________________________ > Sqlgrey-users mailing list > Sql...@li... > https://lists.sourceforge.net/lists/listinfo/sqlgrey-users > -- *LEVEAU Stanislas** *Rectorat de Caen SIAC 168, rue Caponière B.P. 6184 14061 CAEN Cedex / Service Informatique de l'académie de Caen Département Systèmes & Réseaux/ Tel : 02.31.30.17.86 |
|
From: Kyle L. <la...@uc...> - 2010-02-01 03:55:12
|
I've got a basic GNU autoconf scheme working with sqlgrey-1.8.0-rc1. It solves problems like this, in that it eliminates the need to use sed as part of the build process. I'm hoping to make a few more refinements, and then pass it on for scrutiny. In particular, I want to add in testing for the relevant perl modules. Shouldn't take too long to work out, since someone already did the hard part: http://www.nongnu.org/autoconf-archive/ac_perl_module_version.html --Kyle |
|
From: Kyle L. <la...@uc...> - 2010-02-01 20:25:34
|
I wrote:
> I've got a basic GNU autoconf scheme working with sqlgrey-1.8.0-rc1.
...and here it is. There's a fair number of steps involved.
* The following files need to be renamed from 'filename'
to 'filename.in':
Makefile
sqlgrey-logstats.pl
sqlgrey
sqlgrey.spec
tester.pl
update_sqlgrey_config
* The attached patch needs to be applied, which modifies
all of the above-listed files to use @macro_definitions@
instead of hard-coded path names.
* There are three new files that land in the top-level source
directory (attached):
aclocal.m4
configure.ac
install-sh
* The 'VERSION' file should be removed. The only place that the
version needs to be set is in configure.ac. If you really felt
like keeping the VERSION file around, rename it to VERSION.in,
etc. etc. etc.
I would suggest invoking autoconf, and committing the resulting configure
script as part of the distributed source code, in addition to the above.
Yes, it doubles the total size of the package, and is amusing for that
reason.
I did not do an exhaustive search through the source code base for
other hard-coded paths, so there may yet be more files that would
benefit from adopting this scheme.
I also used arbitrary version numbers in configure.ac for the required
perl modules. Those are by no means real requirements. Someone that is
familiar with the usage of these modules might want to suggest more
realistic lower-bounds.
The version requirement in configure.ac for a specific version of
autoconf (2.60), however, should be real. I confirmed that it does
not work with autoconf 2.59, but did my testing with autoconf 2.65.
It looks like 2.62 also works.
I think these modifications (once properly thrashed around, of course)
would be very helpful to include with the 1.8.0 release.
--Kyle
|
|
From: Kyle L. <la...@uc...> - 2010-02-01 23:53:02
Attachments:
configure.ac
|
Here's a newer version of configure.ac that does sensible things when one of the required programs is not found. --Kyle |
|
From: Michal L. <ml...@lo...> - 2010-02-02 00:02:30
|
Hi Kyle, whether or not your patches are approved at the end please make sure 'make dist' works with them and creates a usable distribution tarball. At the moment it checks out a tagged revision from GIT and packs that up. However I don't think we should have the autoconf-generated files in GIT so you may want to add those to the tarball manually. Let me know should you need any help with it. That said you should consider getting the git repo clone and work on sqlgrey "the git way" instead of manually creating patches ;-) Michal On 02/02/2010 12:52 PM, Kyle Lanclos wrote: > Here's a newer version of configure.ac that does sensible things when > one of the required programs is not found. > > --Kyle > > > > ------------------------------------------------------------------------------ > The Planet: dedicated and managed hosting, cloud storage, colocation > Stay online with enterprise data centers and the best network in the business > Choose flexible plans and management services without long-term contracts > Personal 24x7 support from experience hosting pros just a phone call away. > http://p.sf.net/sfu/theplanet-com > > > > _______________________________________________ > Sqlgrey-users mailing list > Sql...@li... > https://lists.sourceforge.net/lists/listinfo/sqlgrey-users |
|
From: Lionel B. <lio...@bo...> - 2010-02-01 20:50:28
|
Kyle Lanclos a écrit, le 02/01/2010 09:25 PM : > I wrote: > >> I've got a basic GNU autoconf scheme working with sqlgrey-1.8.0-rc1. >> > > ...and here it is. There's a fair number of steps involved. > > * The following files need to be renamed from 'filename' > to 'filename.in': > > Makefile > sqlgrey-logstats.pl > sqlgrey > sqlgrey.spec > tester.pl > update_sqlgrey_config > > * The attached patch needs to be applied, which modifies > all of the above-listed files to use @macro_definitions@ > instead of hard-coded path names. > > * There are three new files that land in the top-level source > directory (attached): > > aclocal.m4 > configure.ac > install-sh > > * The 'VERSION' file should be removed. The only place that the > version needs to be set is in configure.ac. If you really felt > like keeping the VERSION file around, rename it to VERSION.in, > etc. etc. etc. > > I would suggest invoking autoconf, and committing the resulting configure > script as part of the distributed source code, in addition to the above. > Yes, it doubles the total size of the package, and is amusing for that > reason. > > I did not do an exhaustive search through the source code base for > other hard-coded paths, so there may yet be more files that would > benefit from adopting this scheme. > > I also used arbitrary version numbers in configure.ac for the required > perl modules. Those are by no means real requirements. Someone that is > familiar with the usage of these modules might want to suggest more > realistic lower-bounds. > > The version requirement in configure.ac for a specific version of > autoconf (2.60), however, should be real. I confirmed that it does > not work with autoconf 2.59, but did my testing with autoconf 2.65. > It looks like 2.62 also works. > Isn't it a little too much work to get portability ? There was a temporary problem with a sed -i call, but are there any other portability problems (that can't be solved by installing the GNU tools or documenting some dependencies) ? What worries me is that autoconf would be another thing to master in order to contribute to the project (after a quick look I don't really understand much of the content of the added files). Lionel |
|
From: Kyle L. <la...@uc...> - 2010-02-01 21:10:34
|
Lionel Bouton wrote: > Isn't it a little too much work to get portability ? There was a > temporary problem with a sed -i call, but are there any other > portability problems (that can't be solved by installing the GNU tools > or documenting some dependencies) ? It was a real hassle to work around all the hard-coded paths in SQLgrey. Honestly, cooking up this autoconf config took me less time than trying to work out the dependencies the hard way (try, fail, fix, try, fail...). > What worries me is that autoconf would be another thing to master in > order to contribute to the project (after a quick look I don't really > understand much of the content of the added files). I didn't understand autoconf to any useful degree before I started working on the autoconf config I just submitted. It looks worse than it is. --Kyle |
|
From: Bruce B. <bb...@bo...> - 2010-02-01 21:17:49
|
On Feb 1, 2010, at 3:10 PM, Kyle Lanclos wrote: > Lionel Bouton wrote: >> Isn't it a little too much work to get portability ? There was a >> temporary problem with a sed -i call, but are there any other >> portability problems (that can't be solved by installing the GNU >> tools >> or documenting some dependencies) ? > > It was a real hassle to work around all the hard-coded paths in > SQLgrey. > Honestly, cooking up this autoconf config took me less time than > trying > to work out the dependencies the hard way (try, fail, fix, try, > fail...). And speaking of both hard-coding AND running on a Mac in the same day, please allow me to share this recent post that I wrote on the "Do It Yourself Mac Server" blog at www.diymacserver.com: == To follow up on my earlier post of 24 Dec 09 wherein I reported a small anomaly regarding sqlgrey behavior when started from launchd… The sqlgrey author decided that when sqlgrey is NOT started as a daemon it should log to STDOUT as opposed to syslog, the way we Mac users want it. A few small code edits will get sqlgrey back to logging to mail.log and creating its pid file. Whether you’re using v1.6.8 or v1.7.6, load the sqlgrey executable into your favorite code editor. 1. To get logging back into mail.log, search for log_file => $opt{daemonize} ? 'Sys::Syslog' : undef, and change it to log_file => 'Sys::Syslog', 2. To get sqlgrey to write it’s pid file, necessary to allow the update_sqlgrey_config script to force re-reading it’s config files, search for pid_file => $opt{daemonize} ? $dflt{pidfile} : undef, and change it to pid_file => $dflt{pidfile}, Another benefit of the above code edits is that sqlgrey-logstats.pl will, once again, find its log entries in mail.log in the format that it is expecting. == Just thought the timing was right :-) B. Bodger Oklahoma City, OK |
|
From: Karl O. P. <ko...@me...> - 2010-02-02 03:29:48
|
On 02/01/2010 03:10:27 PM, Kyle Lanclos wrote:
> Lionel Bouton wrote:
> > Isn't it a little too much work to get portability ?
> I didn't understand autoconf to any useful degree before I started
> working
> on the autoconf config I just submitted. It looks worse than it is.
Autoconf does look worse than it is. I don't understand autoconf
enough to cook up something from scratch but have never had
any problems hacking around in projects that use autoconf
and autoconf does seem to make both portability and end-user
customized installation (much) easier.
Karl <ko...@me...>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X