kern/164793: 'write' system call violates POSIX standard

2012-02-05 Thread Nicolas Bourdaud
>Number: 164793 >Category: kern >Synopsis: 'write' system call violates POSIX standard >Confidential: no >Severity: serious >Priority: medium >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: s

Re: faxgetty 100%

2012-02-05 Thread Gabri Mate
On 12:07 Wed 01 Feb , mailingl...@modernbiztonsag.org wrote: > Dear List, > > i've upgraded a 8.2-STABLE system to 9.0-RELEASE, recompiled every package > and now faxgetty uses 100% CPU and cannot handle incoming connections > (under 8.2-STABLE everything was working OK). > > Sample output fr

bin/164802: Can't destroy zfs snapshots in 8-stable w/o -R

2012-02-05 Thread Daniel Hagerty
>Number: 164802 >Category: bin >Synopsis: Can't destroy zfs snapshots in 8-stable w/o -R >Confidential: no >Severity: serious >Priority: medium >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class:

misc/164803: Unclear manual page for mount_unionfs(8)

2012-02-05 Thread Twoje Radio
>Number: 164803 >Category: misc >Synopsis: Unclear manual page for mount_unionfs(8) >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: do

Re: kern/164793: 'write' system call violates POSIX standard

2012-02-05 Thread Bruce Evans
On Sun, 5 Feb 2012, Nicolas Bourdaud wrote: Description: When a write() cannot transfer as many bytes as requested (because of a file limit), it fails instead of transferring as many bytes as there is room to write. This is a violation of the POSIX standard: http://pubs.opengroup.org/onlinepub

Re: kern/164793: 'write' system call violates POSIX standard

2012-02-05 Thread Bruce Evans
The following reply was made to PR standards/164793; it has been noted by GNATS. From: Bruce Evans To: Nicolas Bourdaud Cc: freebsd-gnats-sub...@freebsd.org, freebsd-bugs@FreeBSD.org Subject: Re: kern/164793: 'write' system call violates POSIX standard Date: Mon, 6 Feb 2012 05:54:50 +1100 (EST)

Re: kern/164258: [mfi] mfi does not work with PERC5/i in AMD M350 motherboard

2012-02-05 Thread James Mansion
The following reply was made to PR kern/164258; it has been noted by GNATS. From: James Mansion To: bug-follo...@freebsd.org, ja...@mansionfamily.plus.com Cc: Subject: Re: kern/164258: [mfi] mfi does not work with PERC5/i in AMD M350 motherboard Date: Sun, 05 Feb 2012 21:06:43 + I have c

bin/164808: system crontab doesn't support usernames with spaces in them

2012-02-05 Thread Garrett Cooper
>Number: 164808 >Category: bin >Synopsis: system crontab doesn't support usernames with spaces in them >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required:

Re: docs/164803: Unclear manual page for mount_unionfs(8)

2012-02-05 Thread linimon
Synopsis: Unclear manual page for mount_unionfs(8) Responsible-Changed-From-To: freebsd-bugs->freebsd-doc Responsible-Changed-By: linimon Responsible-Changed-When: Mon Feb 6 01:28:12 UTC 2012 Responsible-Changed-Why: reclasssify http://www.freebsd.org/cgi/query-pr.cgi?pr=164803 _

Re: kern/139271: [pci] [patch] sysutils/hpacucli does not work on the amd64 kernel

2012-02-05 Thread Eugene Grosbein
The following reply was made to PR kern/139271; it has been noted by GNATS. From: Eugene Grosbein To: bug-follo...@freebsd.org Cc: Subject: Re: kern/139271: [pci] [patch] sysutils/hpacucli does not work on the amd64 kernel Date: Mon, 06 Feb 2012 12:36:29 +0700 This is a multi-part message in