and makes them active.
---
An exit code of 0 means an update was available, and was downloaded and
installed successfully if --checkonly was not specified.
---
Anyways, its nice to know how it works now :)
Thanks-
--
Lance Albertson
en't seeing the problem are running Solaris 10 on
AMD64's.
Guess I'll have to dig deeper.
--
Lance Albertson <[EMAIL PROTECTED]>
Unix System AdministratorKansas State Univers
7;m pretty sure I
know what you're talking about, but I wanted to make sure I understood
you correctly.
--
Lance Albertson <[EMAIL PROTECTED]>
Unix System AdministratorKansas State University
Computing & Telecommunicatio
at 16 seconds. I don't recall seeing these errors
before the upgrade.
Anyways, still puzzled. The two machines that have the newer perl
version seem to not show this error. I saw it happen a few times on one
of the machines, but not as many as the others.
Thanks-
--
Lance Albertson
Matthew Wilson wrote:
>> Ya, that was my last resort, but I'd rather avoid it if I could. I'll
>> post back with my results if I do see an improvement.
>
> Lance-
>
> I was getting identical Socket.pm errors. See
> http://issues.apache.org/SpamAssassin/
ines that are running the newer version of perl (5.8.8).
> I would *not* try to upgrade Perl. In doing so, you could cause you
> machine to laps in an error-log extravaganza.
Ya, that was my last resort, but I'd rather avoid it if I could. I'll
post back with my results if I d
anks!
[1] http://article.gmane.org/gmane.mail.spam.spamassassin.general/94500
[2] http://wiki.apache.org/spamassassin/DBIPlugin
--
Lance Albertson <[EMAIL PROTECTED]>
Unix System AdministratorKansas State University
Computing & Telecommunications Servic
re? --mbx/--mbox? I'm not sure
if there's a difference on how it learns or not or if it could result
in false positives if its not learning correctly.
lance
ed as spam.
thanks,
lance
