>Number:         161205
>Category:       amd64
>Synopsis:       Bug report freebsd 9.0 beta 3
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-amd64
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Oct 01 14:10:08 UTC 2011
>Closed-Date:
>Last-Modified:
>Originator:     dan
>Release:        freebsd 9.0 beta 3
>Organization:
sunsaturn
>Environment:
FreeBSD sunsaturn.com 9.0-BETA3 FreeBSD 9.0-BETA3 #0: Thu Sep 29 14:50:07 CDT 
2011     [email protected]:/usr/obj/usr/src/sys/MYKERNEL  amd64
>Description:
Multiple bugs from testing so far comming from a 8.2 rebuild of source to 9.0 
beta 3:

1) nfsv4 mounts, upon doing a "df -k" on a mount that no longer existed, system 
crashed.
2) were some problems copying various files using rsync off nfsv4 where there 
were no problems with nfsv3
3) pfsync option in kernel if not disabled crashed system soon as PF was loaded 
in rc.conf
4) upon not giving access to libnss-mysql to a certain mysql field, system 
crashed.
5) Not sure if this is proftpd related or freebsd, but when compiling mysql 
into proftpd, parent process will not stay alive more than 20-30 seconds upon 
receiving a SIGALRM, this is using even default config.

Other notes: I am using latest mysql 5.5.15 stable release from ports.

Other port issues unrelated to freebsd 9.0 stability:
1) various modules in apache 2.2 when reinstalled remain commented out in 
apache config:
LoadModule mysql_auth_module  libexec/apache22/mod_auth_mysql.so
LoadModule geoip_module       libexec/apache22/mod_geoip.so
LoadModule rpaf_module        libexec/apache22/mod_rpaf.so
2) chmod o+x /var/run/authdaemond is constantly needed when upgrading 
courier-authlib-base


Dan.





>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-amd64
To unsubscribe, send any mail to "[email protected]"

Reply via email to