From: Josh E. <jo...@en...> - 2005-03-08 14:36:11
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hey everyone, Maybe this is only a problem when installing from source (FreeBSD), but make install blindly overwrites /etc/sqlgrey/sqlgrey.conf. Is it possible to either check for a currently-existing file or dumping into a .conf-dist file? Thanks, Josh -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCLbfDV/+PyAj2L+IRAiFRAJ9AZey33TIcgYQbWMUTcdi68tQxDgCff7xA dFqDqm4dJ0ZI0K4p0yrWkTo= =sG1X -----END PGP SIGNATURE----- |
From: Lionel B. <lio...@bo...> - 2005-03-08 15:56:32
|
Josh Endries wrote the following on 08.03.2005 15:33 : > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hey everyone, > > Maybe this is only a problem when installing from source (FreeBSD), > but make install blindly overwrites /etc/sqlgrey/sqlgrey.conf. Is it > possible to either check for a currently-existing file or dumping > into a .conf-dist file? Usually package maintainers do mark these files as "conf" file with the appropriate package handling system. Gentoo and RPM based distribution have appropriate package description already. Could someone teach me how someone usually package software for FreeBSD ? Lionel |
From: Josh E. <jo...@en...> - 2005-03-08 16:33:16
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Lionel Bouton wrote: | Usually package maintainers do mark these files as "conf" file with the | appropriate package handling system. Gentoo and RPM based distribution | have appropriate package description already. Could someone teach me how | someone usually package software for FreeBSD ? Okay, I wasn't sure who that change was made by. Usually FreeBSD (as I know it) uses the ports tree, or packages created from these ports. Basically you maintain the port's Makefile, and any patches and extra stuff you need, and the Makefile fetches and installs the source. Information on creating a port can be found in the Porter's Handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/ I've never created a port, only used them, but since sqlgrey source compiles and installs almost perfectly out-of-the-box, I wouldn't think it would be too hard to make into a port. I can help you test it if you like. There are only a couple things in the Makefile that I need to tweak before installing (one path change and backup the config file :)). Josh -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCLdMsV/+PyAj2L+IRAg/+AKCxV+AxMzRUsrT/peANXjiDvUVPGgCfdblv ZuBoYlsLVm+OJH0kvadLYRU= =p5Go -----END PGP SIGNATURE----- |
From: Lionel B. <lio...@bo...> - 2005-03-09 00:09:11
|
Josh Endries wrote the following on 08.03.2005 17:30 : > 've never created a port, only used them, but since sqlgrey source > compiles and installs almost perfectly out-of-the-box, I wouldn't > think it would be too hard to make into a port. I can help you test > it if you like. There are only a couple things in the Makefile that > I need to tweak before installing (one path change and backup the > config file :)). The config file handling should be done outside SQLgrey's Makefile. Relying on the distribution to sorts things out with config files is the cleaner way. RPM-based distributions warn user when the config file changed since its installation and usually creates rpmnew/rpmsave files. Gentoo's Portage never overwrites config file unless explicitly told to and then helps the user interactively merge the old and new configuration files. FreeBSD ports should have one mechanism for that too (or the port maintainer should patch the Makefile), I don't want to force into the Makefile something tailored for FreeBSD. Lionel. |
From: Max D. <Max...@lr...> - 2005-03-10 13:25:15
|
Hi All, someone ever noticed occasional sqlgrey crashes (it happens one time in, say, 20 Mio transactions processed) with this log: Mar 10 13:24:35 lxmhs17 sqlgrey: fatal: Modification of a read-only value attempted at /usr/lib/perl5/5.8.0/i586-linux-thread-multi/Sys/Syslog.pm line 296. ?? Max Max Diehn ------------------------------------------------- Leibniz-Rechenzentrum ! <mailto:di...@lr...> Barer Str. 21 ! 80333 Muenchen, Germany ! Tel: +49 89 289-27823 |
From: Lionel B. <lio...@bo...> - 2005-03-10 16:55:05
|
Max Diehn wrote the following on 10.03.2005 14:25 : > Hi All, > > someone ever noticed occasional sqlgrey crashes (it happens one time > in, say, 20 Mio transactions processed) with this log: > > Mar 10 13:24:35 lxmhs17 sqlgrey: fatal: Modification of a read-only > value attempted at > /usr/lib/perl5/5.8.0/i586-linux-thread-multi/Sys/Syslog.pm line 296. Which sqlgrey version? What are the previous log lines? If not yet done can you reproduce it with debug in sqlgrey.conf? Cheers, Lionel. |
From: Max D. <Max...@lr...> - 2005-03-10 17:30:19
|
Lionel Bouton wrote: > Max Diehn wrote the following on 10.03.2005 14:25 : > >> Hi All, >> >> someone ever noticed occasional sqlgrey crashes (it happens one time >> in, say, 20 Mio transactions processed) with this log: >> >> Mar 10 13:24:35 lxmhs17 sqlgrey: fatal: Modification of a read-only >> value attempted at >> /usr/lib/perl5/5.8.0/i586-linux-thread-multi/Sys/Syslog.pm line 296. > > > > Which sqlgrey version? What are the previous log lines? If not yet done > can you reproduce it with debug in sqlgrey.conf? > Actually I didn't want to bother You with that, because I still had an older version of sqlgrey in production (1.4.1). Hence, if this is a non-issue to the other users up to now, I would say, for the moment: just forget about it - if it ever happens again with the 1.5.*, I'll tell You. I wasn't able to reproduce it - and I didn't find anything in the log, that looks interesting (I use debug as my log level anyway). Maybe it has something to do with perl 5.8.0, which, for some people, doesn't have the best reputation - I don't know. Here's the last lines from the log, anyway: Mar 10 13:24:34 lxmhs17 sqlgrey: new: 222.108.41.160: hmn...@fs... -> dal...@ju... Mar 10 13:24:34 lxmhs17 sqlgrey: request: client_address=222.108.41.160 client_name=[222.108.41.160] rec...@ju... request=smtpd_access_policy sen...@fs... action=defer_if_permit Greylisted for 14 minutes Mar 10 13:24:34 lxmhs17 sqlgrey: new: 221.212.232.138: su...@si... -> wm...@de... Mar 10 13:24:34 lxmhs17 sqlgrey: request: client_address=221.212.232.138 client_name=[221.212.232.138] rec...@de... request=smtpd_access_policy sen...@si... action=defer_if_permit Greylisted for 14 minutes Cheers, Max > Cheers, > > Lionel. > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Sqlgrey-users mailing list > Sql...@li... > https://lists.sourceforge.net/lists/listinfo/sqlgrey-users -- Max Diehn ------------------------------------------------- Leibniz-Rechenzentrum ! <mailto:di...@lr...> Barer Str. 21 ! 80333 Muenchen, Germany ! Tel: +49 89 289-27823 |
From: Dave P. <dav...@gm...> - 2005-03-10 20:38:50
|
I am running 1.4.5 out of the FreeBSD Ports collection. I run the latest 1.5 release on my main mail server and it runs great. On the FreeBSD box I keep getting these notifications: SQLgrey lost connection to: DBI:mysql:database=sqlgrey;host=localhost (max warn message rate hit, throttling) Is there a fix or something to tune for this? I would like to upgrade but1,5 isn't in the Ports collection yet and I don't want to foul anything up on the FreeBSD box by installing manually. Not sure if that would fou lup a future Port-based install anyway. Dave |
From: Lionel B. <lio...@bo...> - 2005-03-10 21:24:29
|
Dave Pascoe wrote the following on 10.03.2005 21:38 : >I am running 1.4.5 out of the FreeBSD Ports collection. I run the >latest 1.5 release on my main mail server and it runs great. > >On the FreeBSD box I keep getting these notifications: > >SQLgrey lost connection to: DBI:mysql:database=sqlgrey;host=localhost (max >warn message rate hit, throttling) > > If I'm not mistaken this is the 1.4.5-specific bug where all null-originated messages trigger a bug and make SQLgrey reconnect itself to the database. 1.4.6 and beyond include the fix. Lionel |