Re: upgrading methods
On Thursday 13 January 2005 03:44 pm, Thomas Arend wrote: Because SuSE stores spamd in /usr/sbin/spamd and the tarball stores it in /usr/bin/spamd the SA does not run. You could have put a symlink in /usr/bin ln -s /usr/sbin/spamd /usr/bin/spamd -- Top ten reasons to procrastinate. 1.
RE: upgrading methods
Phil Barnett wrote:
On Thursday 13 January 2005 03:44 pm, Thomas Arend wrote:
Because SuSE stores spamd in /usr/sbin/spamd and the tarball stores
it in /usr/bin/spamd the SA does not run.
You could have put a symlink in /usr/bin
ln -s /usr/sbin/spamd /usr/bin/spamd
I'm feeling puckish today so I'll say it.
Or even symlink /usr/sbin to /usr/bin (shock, horror) :-)
Matthew.van.Eerde (at) hbinc.com 805.964.4554 x902
Hispanic Business Inc./HireDiversity.com Software Engineer
perl -emap{y/a-z/l-za-k/;print}shift Jjhi pcdiwtg Ptga wprztg,
Re: upgrading methods
On Thursday 13 January 2005 07:19 pm, [EMAIL PROTECTED] wrote: Phil Barnett wrote: I'm feeling puckish today so I'll say it. Or even symlink /usr/sbin to /usr/bin (shock, horror) :-) Gasp, You've gone too far, now... ;-) -- Top ten reasons to procrastinate. 1.
Re: upgrading methods
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Mittwoch, 12. Januar 2005 21:42 schrieb Hans du Plooy: I was wondering what method you guys gals prefer for upgrading spamassassin on the more mainstream rpm based distros (MDK/Fedora/rh/SUSE). I have a SUSE 9.1 server, running spamassassin through amavisd-new. Works like a charm. I decided to give the CPAN thing a try. logged in, updated all the relevant perl things (acutally I was wishing to upgrade everything perl related listed in amavisd-new's logfile, sa being one of them). Somehow this broke spamassassin very badly. Couldn't even run sa-learn! So I downloaded the tarball and built rpms using the included spec file with rpmbuild - this fixed it nicely. I'm using SuSE 9.1 and have upgrade from 2.63 to 3.01 and 3.0.2 using the tarball. I'm not using CPAN. Because SuSE stores spamd in /usr/sbin/spamd and the tarball stores it in /usr/bin/spamd the SA does not run. Deleted /usr/sbin/spamd, update /etc/init.d/spamd to the new directory and delete -a param in /etc/sysconfg/spamd because it is deprecated in 3.0.x Now it works Just curious Thanks - -- icq:133073900 http://www.t-arend.de -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFB5t2RHe2ZLU3NgHsRAobLAJ9fve3cPRdsmwM+OXnZdzsxrBO1HgCbBGKC ezrYR3kTZ21YqR6VSJ3yrIw= =s5qy -END PGP SIGNATURE-
Re: upgrading methods
On Wed, Jan 12, 2005 at 10:42:42PM +0200, Hans du Plooy wrote: I was wondering what method you guys gals prefer for upgrading spamassassin on the more mainstream rpm based distros (MDK/Fedora/rh/SUSE). I have a SUSE 9.1 server, running spamassassin through amavisd-new. Works like a charm. I decided to give the CPAN thing a try. logged in, updated all the relevant perl things (acutally I was wishing to upgrade everything perl related listed in amavisd-new's logfile, sa being one of them). Somehow this broke spamassassin very badly. Couldn't even run sa-learn! So I downloaded the tarball and built rpms using the included spec file with rpmbuild - this fixed it nicely. Just curious Thanks -- Kind regards Hans du Plooy Newington Consulting Services hansdp at newingtoncs dot co dot za Hmm. I use CPAN all the time with no problems. I'm running (including clients) RedHat 9, Fedora Core 1, Fedora Core 2. Cheers, -- Bob McClure, Jr. Bobcat Open Systems, Inc. [EMAIL PROTECTED] http://www.bobcatos.com Wise men still seek Him.
Re: upgrading methods
Hans du Plooy wrote: I was wondering what method you guys gals prefer for upgrading spamassassin on the more mainstream rpm based distros (MDK/Fedora/rh/SUSE). I'm not running RedHat on my own systems any more, but I still have one legacy RH7.3 system at work. All of my own new installs have been White Box recently. (Head office is largely a Debian shop, with one or two lost souls preferring Solaris on x86 or Sun hardware, or *BSD.) I have a SUSE 9.1 server, running spamassassin through amavisd-new. Works like a charm. I decided to give the CPAN thing a try. logged in, updated all the relevant perl things (acutally I was wishing to upgrade everything perl related listed in amavisd-new's logfile, sa being one of them). Somehow this broke spamassassin very badly. Couldn't even run sa-learn! CPAN can be a bit tempermental - you might be better off using one of the .rpm-building wrappers for CPAN. (IIRC SuSE's packaging is a bit odd anyway.) So I downloaded the tarball and built rpms using the included spec file with rpmbuild - this fixed it nicely. For quite a while I used roll-your-own packages with my own .spec file, because none of the third-party packages I found would either a) install (in the case of provided binary RPMs) or b) build on my system from the .src.rpm. It also allowed me to include specific tweaks and packages - I patched the SURBL plugin into my last couple 2.64 packages, for instance. I never used the SA-provided .spec file as it wasn't bundled when I first went looking IIRC, and since then I've tried once or twice and gotten errors I didn't have the time to track down where my own spec file worked. In general, though, more recently I've found out about third-party repositories accessible via apt or yum. I haven't bothered using them for SpamAssassin (yet), but I am using them for a number of other packages, and for security support on the RH7.3 box. -kgd -- Get your mouse off of there! You don't know where that email has been!
Re: upgrading methods
On Wed, 2005-01-12 at 14:54 -0600, Bob McClure Jr wrote: On Wed, Jan 12, 2005 at 10:42:42PM +0200, Hans du Plooy wrote: I was wondering what method you guys gals prefer for upgrading spamassassin on the more mainstream rpm based distros (MDK/Fedora/rh/SUSE). I have a SUSE 9.1 server, running spamassassin through amavisd-new. Works like a charm. I decided to give the CPAN thing a try. logged in, updated all the relevant perl things (acutally I was wishing to upgrade everything perl related listed in amavisd-new's logfile, sa being one of them). Somehow this broke spamassassin very badly. Couldn't even run sa-learn! So I downloaded the tarball and built rpms using the included spec file with rpmbuild - this fixed it nicely. Just curious Thanks -- Kind regards Hans du Plooy Newington Consulting Services hansdp at newingtoncs dot co dot za Hmm. I use CPAN all the time with no problems. I'm running (including clients) RedHat 9, Fedora Core 1, Fedora Core 2. Cheers, I have also had no problems using CPAN, running FreeBSD 5.2.1-RELEASE and Fedora Core 3. Cheers, Craig.
Re: upgrading methods
I like to use RPMs from YUM or APT repositories where ever I can on RPM based distrabutions. But I think for spamassassin, you are better off going with CPAN to keep it up to date. Martin Hans du Plooy wrote: I was wondering what method you guys gals prefer for upgrading spamassassin on the more mainstream rpm based distros (MDK/Fedora/rh/SUSE). I have a SUSE 9.1 server, running spamassassin through amavisd-new. Works like a charm. I decided to give the CPAN thing a try. logged in, updated all the relevant perl things (acutally I was wishing to upgrade everything perl related listed in amavisd-new's logfile, sa being one of them). Somehow this broke spamassassin very badly. Couldn't even run sa-learn! So I downloaded the tarball and built rpms using the included spec file with rpmbuild - this fixed it nicely. Just curious Thanks
