On 06/08/2010 12:22, Yann Berthier wrote:
> Hi Peter,
>
> On 2010-08-06, at 1:37 AM, Peter Haag wrote:
>
>   
>>> kernel: pid 82021 (perl5.10.1), uid 1008: exited on signal 11, every couple 
>>> of days or so
>>>       
>> Signal 11 means, your Perl crashed. My guess would be, there could be a 
>> Problem with Perl on the Pre-release. Perl
>> should never crash even with a faulty script.
>>     
> Thanks a lot for your feedback 
>
>  We may have picked a bad apple, let's hope that an upgrade will fix that.
>   
For what its worth, I upgraded my 8.0-RELEASE box running nfsen to a
8.1-RELEASE and havent seen any problems yet (only been 4 days so far
though)

[r...@seaurchin ~]# uname -a
FreeBSD seaurchin.the.namesco.net 8.1-RELEASE FreeBSD 8.1-RELEASE #0:
Mon Jul 19 02:55:53 UTC 2010    
[email protected]:/usr/obj/usr/src/sys/GENERIC  i386
[r...@seaurchin ~]# pkg_info -Ix rrd
rrdtool-1.4.3       Round Robin Database Tools
[r...@seaurchin ~]# pkg_info | egrep '^perl|^nfsen|^nfdump|^rrdtool'
nfdump-1.6.1        Command-line tools to collect and process NetFlow data
nfsen-1.3.2_1       Web based frontend to nfdump netflow collector
perl-5.8.9_3        Practical Extraction and Report Language
rrdtool-1.4.3       Round Robin Database Tools


Vince
> - y
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by 
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev 
> _______________________________________________
> Nfsen-discuss mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/nfsen-discuss
>   


------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
_______________________________________________
Nfsen-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nfsen-discuss

Reply via email to