RE: perlMX
Hi Arthur, We are about to begin testing PerlMx, more specifically for it's spam checking than for virus protection. So far it seems to have very similar features to some of the free packages like Spam Assassin. We are after something commercially supported though, that has some more mature management features. Either way it looks like we will have to do some custom Perl programming to get exactly what we are after, but, that remains to be seen... Sean Page Network Analyst Information Technology Services Edmonton Public Schools http://its.epsb.ca -Original Message- From: Arthur W. Neilson III [mailto:[EMAIL PROTECTED]] Sent: May 31, 2002 1:08 PM To: [EMAIL PROTECTED] Subject: perlMX Has anyone evaluated or purchased the new product PerlMX http://www.activestate.com/Products/PerlMX from ActiveState? We currently use Amavis with NAI's uvscan to scan mail being relayed by sendmail on our FreeBSD 4.4 mail exchangers. We plan to upgrade to 4-stable and use the 8.12.3 sendmail with the milter interface for either Amavis or a commercial product such as PerlMX. -- __ / )_/_ It is a capital mistake to theorise before one has data. /--/ __ /Insensibly one begins to twist facts to suit theories, / (_/ (_<__ Instead of theories to suit facts. -- Sherlock Holmes, "A Scandal in Bohemia" Arthur W. Neilson III, WH7N - FISTS #7448 Bank of Hawaii Network Services http://www.pilikia.net [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
RE: perlMX
I tried Version 1.x.x and found the exact same thing. Version 2 however, is much more of an "out of the box" solution. The product ships with their "SpamCheck" and "VirusCheck" filters and is ready to go literally within minutes of installation, depending on how much you like to tweak things (provided of course that you already have sendmail up and running with milter support). What might make this more advantageous than a free package is being able to use their pre-built tools for actually managing filtered mail (for those that will not tolerate lost mail in any shape or form). We may be finding that those tools are still too undeveloped to be worth paying for the entire package. If there is interest, I'll try to keep the list posted on our findings. I would like it if others who have tested PerlMx would share their feelings on it. Sean. -Original Message- From: Sam Leffler [mailto:[EMAIL PROTECTED]] Sent: June 4, 2002 2:23 PM To: Sean Page; [EMAIL PROTECTED] Subject: Re: perlMX FWIW, I tried PerlMX and discarded it. Unless the product has changed, it's more of a framework for implementing solutions. For SPAM filtering I use DNS black lists (MAPS, ORDB) and DCC. For anti-virus filtering I found the Trend Micro product to do ok (using it in evaluation mode right now under Solaris). Sam - Original Message - From: "Sean Page" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, June 04, 2002 1:07 PM Subject: RE: perlMX > Hi Arthur, > > We are about to begin testing PerlMx, more specifically for it's spam > checking than for virus protection. So far it seems to have very > similar features to some of the free packages like Spam Assassin. We > are after something commercially supported though, that has some more > mature management features. Either way it looks like we will have to > do some custom > Perl programming to get exactly what we are after, but, that remains > to be seen... > > > Sean Page > Network Analyst > Information Technology Services > Edmonton Public Schools > http://its.epsb.ca > > > -Original Message- > From: Arthur W. Neilson III [mailto:[EMAIL PROTECTED]] > Sent: May 31, 2002 1:08 PM > To: [EMAIL PROTECTED] > Subject: perlMX > > > Has anyone evaluated or purchased the new product PerlMX > > http://www.activestate.com/Products/PerlMX > > from ActiveState? We currently use Amavis with NAI's uvscan to scan > mail being relayed by sendmail on our FreeBSD 4.4 mail exchangers. We > plan to upgrade to 4-stable and use the 8.12.3 sendmail with the > milter interface for either Amavis or a commercial product such as > PerlMX. > -- > __ >/ )_/_ It is a capital mistake to theorise before one has data. > /--/ __ /Insensibly one begins to twist facts to suit theories, > / (_/ (_<__ Instead of theories to suit facts. > -- Sherlock Holmes, "A Scandal in Bohemia" > Arthur W. Neilson III, WH7N - FISTS #7448 Bank of Hawaii Network > Services http://www.pilikia.net [EMAIL PROTECTED], [EMAIL PROTECTED], > [EMAIL PROTECTED] > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Clockwork 24 hour crash in 4.5-RELEASE-p5
- Original Message - From: "Oliver Crow" <[EMAIL PROTECTED]> Newsgroups: local.freebsd.stable Sent: Sunday, June 02, 2002 4:05 PM Subject: Re: Clockwork 24 hour crash in 4.5-RELEASE-p5 > > On Sun, 2 Jun 2002, mikea wrote: > > > On Sat, Jun 01, 2002 at 08:37:21PM -0700, Oliver Crow wrote: > > > > > > I have a FreeBSD 4.5-p5 system that's crashing reliably every 24 hours +/- > > > a few minutes. It's been doing this ever since I compiled a 4.5-p4 kernel > > > on March 25th. I cvsup'd to 4.5-p5 and recompiled, but it's still > > > crashing. Interesting story but true: A few years back, a client of ours had a z80 based mpm based system with three vt100 terminals. SOMETIME AROUND 5:00PM, EACH DAY (give or take a fews mins) the vt100 terminal on the main system blinked a little and the whols system crashed, locking out whatever anyone was doing on the other two as well. They were on a ups, they were on surgr suppressors, the serial cables were clean, eiii specs, we slowd down the baud rate, still happened. guess what: there was a postage meter (read BIG MF MAGNET) on the other side of the wall. 5pm, just before going home, the receptionist whould 'ch-chunk' about 40 letters. -- Michael Scheidell SECNAP Network Security, LLC (561) 368-9561 [EMAIL PROTECTED] http://www.secnap.net > > > > Either I'm missing data showing the crash time, or you didn't > > include it. When does this crash happen? Is it during a burst > > of cron-spawned activity? > > It doesn't crash during a burst of cron activity, no. It doesn't occur at > exactly the same time each day, it moves around by a few minutes each > time. If you reboot manually it'll crash at the same time the next day > (ie, 24 hours after the reboot). > > Here's the log of reboots during April. You see it crashed every day > between the first and the 16th. Then it didn't crash for 10 days. I > rebooted manually on the 26th at 20:19, and it started crashing every > day again. > > # last -f /var/log/wtmp.1 reboot > reboot ~ Tue Apr 30 20:17 > reboot ~ Mon Apr 29 20:17 > reboot ~ Sun Apr 28 20:19 > reboot ~ Sat Apr 27 20:19 > reboot ~ Fri Apr 26 20:19 > reboot ~ Fri Apr 26 19:49 > reboot ~ Tue Apr 16 11:10 > reboot ~ Tue Apr 16 11:03 > reboot ~ Mon Apr 15 18:33 > reboot ~ Sun Apr 14 18:37 > reboot ~ Sat Apr 13 18:41 > reboot ~ Fri Apr 12 18:45 > reboot ~ Thu Apr 11 18:48 > reboot ~ Thu Apr 11 18:00 > reboot ~ Tue Apr 9 19:50 > reboot ~ Mon Apr 8 19:54 > reboot ~ Sun Apr 7 19:58 > reboot ~ Sat Apr 6 19:00 > reboot ~ Fri Apr 5 18:58 > reboot ~ Thu Apr 4 18:58 > reboot ~ Wed Apr 3 19:02 > reboot ~ Tue Apr 2 19:00 > reboot ~ Mon Apr 1 19:00 > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message > > --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
out of place syslog entries
Hi, Jun 5 00:22:47 root postfix/smtpd[57574] Jun 5 00:22:47 root postfix/qmgr[55069] Jun 5 00:22:47 root postfix/local[57577] Jun 5 00:22:48 root imapd[57576] Jun 5 00:22:48 root imapd[57576] Jun 5 00:22:49 root imapd[57576] Jun 5 00:22:55 root imapd[56177] Jun 5 00:22:58 root imapd[57629] Jun 5 00:23:00 root postfix/smtp[57515] Jun 5 00:23:00 root postfix/smtp[57515] Jun 4 22:25:25 root postfix/smtpd[57772] Jun 4 22:25:25 root postfix/smtpd[57772] Jun 4 22:25:25 root postfix/smtpd[57772] Jun 4 22:25:45 root postfix/smtpd[57772] Jun 4 22:25:46 root postfix/smtpd[57772] Jun 4 22:25:52 root postfix/smtpd[57772] Jun 4 22:30:19 root postfix/smtpd[58118] Jun 4 22:30:20 root postfix/smtpd[58118] Jun 4 22:30:20 root postfix/smtpd[58118] Jun 4 22:30:23 root postfix/smtpd[58118] Jun 4 22:30:23 root postfix/smtpd[58118] Jun 4 22:30:29 root postfix/smtpd[58118] Jun 5 00:42:03 root postfix/smtpd[58916] Jun 5 00:42:03 root postfix/smtpd[58916] Jun 5 00:42:03 root postfix/smtpd[58916] Jun 5 00:42:03 root postfix/smtpd[58916] Jun 5 00:42:03 root postfix/cleanup[58917] Jun 5 00:42:03 root postfix/qmgr[55069] Jun 5 00:42:03 root postfix/smtpd[58916] Jun 5 00:42:46 root postfix/smtp[58919] I've removed the actual message to protect the innocent. What I'm getting at is the log entry for 2 hours in the past being added in the middle of the present. Is this a bug or a feature? Thanks, Aragon To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
ports upgrade
Hi,
there has been discussions on this list re-upgrading with make world etc,
and there is an execellent section on the docs about how this is done.. I
haven't had any problems with this.
Is there a recommended procedure to upgrade various ports, eg all installed
ports on ones system.
I know about the ports-supfile and I use that before installing a new port
that I think I need. But for ports that I have already installed, is there
any set procedure to upgrade them all at once? or do a pkg_remove {port} and
re-install a fresh port individually for each port that is installed.
I hope this post is not too far out of the guidelines for freebsd-stable
Regards,
Allan McDonald
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: ports upgrade
The sysutils/portupgrade port handles this well.
--David Bushong
On Wed, Jun 05, 2002 at 08:53:28AM +1000, Allan McDonald wrote:
> Hi,
> there has been discussions on this list re-upgrading with make world etc,
> and there is an execellent section on the docs about how this is done.. I
> haven't had any problems with this.
>
> Is there a recommended procedure to upgrade various ports, eg all installed
> ports on ones system.
> I know about the ports-supfile and I use that before installing a new port
> that I think I need. But for ports that I have already installed, is there
> any set procedure to upgrade them all at once? or do a pkg_remove {port} and
> re-install a fresh port individually for each port that is installed.
>
> I hope this post is not too far out of the guidelines for freebsd-stable
>
>
> Regards,
>
> Allan McDonald
>
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-stable" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
RE: RE: Swap_pager error
I looked through all the periodic daily stuff. It doesn't seem that any of the scripts will trash NFS mounted partitions, almost everything I saw would only look at UFS mounted partitions. One thing I did notice is the security check was quite brutal. While any server should survive it I believe this is what is causing the system to crash. The security check seems to run a find on the NFS servers local UFS mounts. We have some very, very large volumes with hundreds of thousands of small files... (maildirs, boxes, webmail, web, etc). On this box, it seemed that the security check would take almost 3-4 minutes to complete with that find, and it just totally saturates the box in activity when it runs. So, I think there may be a loading issue with all these files/inodes in relation to the find process... Perhaps the SCSI or driver stuff in FreeBSD. If I can be of any help on this, I surely will led a hand. I would like to see FreeBSD be able to survive this without a hitch. Perhaps a suggestion to change the priority of the "find" tasks in those scripts with nice or something. I mean the box was really bogged down when we ran "periodic daily" by manually. As a work around, we moved periodic daily to run at 9:01am instead of 3:01am, and only on Monday - Friday. We don't need any more weekend surprise pages and then call-ins. :-) Since this box is an internal server only with no accounts on it, and it has no route to the outside + behind a firewall, we're going to go ahead and disable the security check all together. I'm hoping that this will provide a work around for this "loading" issue. If I can be any help to the core team to debug this problem, I'll do my best to do what I can. -- Robert Blayzor, BOFH INOC, LLC [EMAIL PROTECTED] One picture is worth 128K words. > -Original Message- > From: Matthew Dillon [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, June 04, 2002 1:49 PM > To: Robert Blayzor; [EMAIL PROTECTED] > Subject: Re: RE: Swap_pager error > > > I have one more idea... daily cron jobs tend to really > load down the > system for a short period of time, especially the disks. > In your case > the local daily cron is combinging with the daily cron > running on the > NFS clients. There could be a hardware problem with the > system that > is most likely to show up under heavy loads. > > It is also possible that this is revealing a driver bug somewhere. > For example, the extreme disk load could be revealing a bug in the > driver's tag handling or in the RAID card's tag handling. > The lack > of driver-based error messages is rather odd. I don't > see how that > can happen unless the RAID card itself is locking up. > > -Matt > > :: > ::Both times the box has crashed crashed at ~3:02am. I'm > thinking that > ::something in periodic daily is causing the crashes. > :: > ::Keep in mind, that this server serves several NFS clients > which mount > ::things such as FreeBSD ports and /usr/src. Those are soft > linked to on > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Intel Pro/100+ Dual Port NIC card (711269)
Alessandro de Manzano wrote: > > are these the 'server' versions or what ? Intel PRO/100 S Dual ? > > I would buy a Dell poweredge 350 (1U rack) but I'ld sure if such boards > are well supported :-) > Quick-specs on the DL360 can be found at: http://www.compaq.com/products/servers/proliantdl360/description.html#quickspecs Compaq lists the NIC as Two Compaq NC3163 Fast Ethernet NIC Embedded 10/100 WOL (Wake On LAN). So, they might just be seperate embedded nics. The dual-port card is Compaq's NC3134. Info on that can be found at: http://www.compaq.com/products/servers/networking/NC3134/index.html My DL360 is a little older than the currently available model and the dual-port card is something I "salavaged" from another older machine. From the boot-up messages it looks like all four ports are using Intel's 82555 ASIC. I'm not sure which ASIC/chipset is on the latest Intel PRO/100 S Dual. According to the specs on the NC3134, the latest Intel ASIC is 82559. Maybe see if you get an eval unit of the Intel PRO/100 S Dual? Here is the boot-up message involving the nics. fxp0: port 0x4000-0x403f mem 0xc6a0-0xc6af,0xc6bff000-0xc6bf irq 7 at device 4.0 on pci3 fxp0: Ethernet address 00:02:a5:8b:d4:dd inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp1: port 0x4040-0x407f mem 0xc680-0xc68f,0xc69ff000-0xc69f irq 10 at device 5.0 on pci3 fxp1: Ethernet address 00:02:a5:8b:d4:dc inphy1: on miibus1 inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pcib2: at device 6.0 on pci3 pci4: on pcib2 fxp2: port 0x5000-0x503f mem 0xc6e0-0xc6ef,0xc6fff000-0xc6ff irq 11 at device 4.0 on pci4 fxp2: Ethernet address 00:02:a5:5c:f6:78 inphy2: on miibus2 inphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp3: port 0x5040-0x507f mem 0xc6c0-0xc6cf,0xc6dff000-0xc6df irq 11 at device 5.0 on pci4 fxp3: Ethernet address 00:02:a5:5c:f6:79 inphy3: on miibus3 inphy3: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Cheers, Greg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: ports upgrade
Some suggestions on your script. On Wed, Jun 05, 2002 at 08:14:02AM +0200, The Unicorn wrote: > I use the following script I once wrote. It is still not perfect and I > know it can be highy optimised, but most (99.999%) of the time it just > does the job. I have a similar script to cvsup and build the whole > world, create a new kernel and run mergemaster as well. It just makes > life easier. > > ... > > cvsup -g -L 2 /etc/cvsup-file 2>&1 && \ > If you set up /etc/make.conf right, you can make that: cd /usr/ports && make update > > ... > > pkgdb -F < /dev/tty > /dev/tty && \ > If you have any held ports, this will quietly (in the lines whirring past) skip them, and you won't necessarily have a fixed pkgdb; pkgdb -Ff is usually what I want. > > ... > > portversion -c | tee /root/tmp/do_update&& \ > Given how long your script will take to run, I'm not sure there's any reason not to just: portupgrade -Ra If for some reason you don't want to, you might want to at least: portupgrade -C -R -c ... This will help keep the pkgdb in order for ports that depend on other ports that they didn't used to depend on. Just some thoughts. --David Bushong To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
