Re: Strange trouble with clamd/greylist/mimedefang

2007-06-13 Thread BERTRAND Joël

BERTRAND Joël a écrit :

Clint Adams a écrit :

On Sat, Jun 09, 2007 at 08:46:53PM +0200, BERTRAND Joël wrote:
Right. For me, one think is very suspect. Milter-greylist nor 
clamd are not able to fork on kant.


What makes you think that they're unable to fork?


Because clamd uses multithread and multitask features.
When mimedefang send a mail to clamd socket, clamd forks itself to 
analyze this mail. On kant, clamd is not able to fork, or maybe is able 
to fork but cannot analyze any mail, and mimedefang aborts with a busy 
timeout. If I replace clamd by clamscan, mimedefang works (but alayze 
process take a very long time). When I try to replace clamscan by 
clamdscan that uses clamd, mimedefang hangs after a very short number of 
analyzes.


Maybe clamd implementation is broken with libc6 2.5.


The only significative difference for me is the libc release.

Root kant:[~]  dpkg-query -l libc6
...
ii  libc6  2.5-9  GNU C Library: Shared libraries

rayleigh:[~]   dpkg-query -l libc6
...
ii  libc6  2.3.6.ds1-13   GNU C Library: Shared libraries


2.5 gives you NPTL, which means that threaded programs can have real
threads instead of forking.



If you do a ps -eLf on a glibc2.5 system with numerous clamdscan
processes going, you will hopefully see multiple clamd lines
(same PID, different LWP number).

If you don't, maybe there's an issue with libpthread.


I see some clamd threads, but even with some threads, clamd cannot 
analyze inbound mails.


I have another question about threads. On a U80, with four 
UltraSparc processors, are two threads of one process limited to 
ressources given by one processor, or can they be shared on two 
processors (like regular process) ?


	Strange. Problem solved when I have rebooted my U80... I have seen a 
bind9 instability too that was solved by the same action...


Regards,

JKB


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: benchmarks

2007-06-13 Thread Martin
On Wed, 2007-06-13 at 00:38 +0100, andrew holway wrote:
 Hi,
 
 We've been doing some benchmarks, please make a visit to the two pages below.
 
 http://www.moopix.co.uk/bench.php - sunfire V210 2 gig ram dual 1.3
 ultrasparc IIIi (debian)
 http://www.moonet.co.uk/bench.php - celeron 1.6 512 gig ram (ubuntu)
 
 You can see that the sparc seems to be performing very badly. Would
 this be an expected result or have I made a mess of it.

That entirely depends on what you've done and how you've done it.  As
the pages contain no methodology it's impossible to give anything other
than generalities.  Doing benchmarking properly is difficult; I tend to
start by reading the section of Hennessey and Patterson relevant to what
I want to measure.

Cheers,
 - Martin



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



AW: [sun]debian

2007-06-13 Thread Jurzitza, Dieter
Hi folks,
in case of U60 I can only confirm what Steve said, U60 is a great box for 
installing Debian.
To connect a normal PC-Style monitor to your system you might want to 
consider a Raritan Sun VGA-Converter 13W3- D-Sub 15. Saves lots of headaches 
(though you won't get it for free). It is called Adapter:1395.
Hope this helps,
take care



Dieter


-Ursprüngliche Nachricht-
Von:Steve Pacenka [mailto:[EMAIL PROTECTED]
Gesendet:   Do 14.06.2007 02:59
An: debian-sparc@lists.debian.org
Cc: 
Betreff:Re: [sun]debian

On Wednesday 06 June 2007 05:23, Eric Rapilly wrote:
 I have some questions, may be you wille be able to answer me. I will
* 
 
***
Harman Becker Automotive Systems GmbH
Geschaeftsfuehrung:  Dr. Peter Geiselhart  -  Michael Mauser  -  William S. 
Palin -  Edwin Summers  -  Regis Baudot
Sitz der Gesellschaft: Karlsbad - Registergericht: Mannheim HRB 361395
 
***
Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte 
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail 
irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und 
loeschen Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe 
dieser Mail ist nicht gestattet.
This e-mail may contain confidential and/or privileged information. If you are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and delete this e-mail. Any unauthorized copying, 
disclosure or distribution of the contents in this e-mail is strictly forbidden.
***