Re: [Sqlgrey-users] autoconf for SQLgrey

[Bruce B. <bb...@bo...>]

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