On Mon, 23 May 2005, Greg 'groggy' Lehey wrote:
[severely trimmed]
[severely trimmed again :)]
Now that I've had time to look at it, both problems appear to be
related to signals, but that's about as far as it goes. I wouldn't
expect any connection unless it's a general signal race
[severely trimmed]
On Friday, 13 May 2005 at 12:45:12 -0500, Sen C. Farley wrote:
On Fri, 13 May 2005, Hervé Kergourlay wrote:
Seán C. Farley a écrit :
On Thu, 12 May 2005, Seán C. Farley wrote:
On Thu, 12 May 2005, Hervé Kergourlay wrote:
4) wait() API
2 problems, the first is a ECHILD
Hervé Kergourlay wrote this message on Thu, May 12, 2005 at 09:37 +0200:
what about files more than 4GB, do I need to use specific APIs as
open64, stat64 or the current open and stat API are managing the big file ?
Nope... FreeBSD's off_t has been 64bits since 2.0... Just make sure
you use
John-Mark Gurney a écrit :
Hervé Kergourlay wrote this message on Thu, May 12, 2005 at 09:37 +0200:
what about files more than 4GB, do I need to use specific APIs as
open64, stat64 or the current open and stat API are managing the big file ?
Nope... FreeBSD's off_t has been 64bits since
[much irrelevant content removed]
On Friday, 13 May 2005 at 12:45:12 -0500, Sen C. Farley wrote:
On Fri, 13 May 2005, Hervé Kergourlay wrote:
did you have any idea if the problem will be solve by the FreeBSD team
or not ?
I updated my bug report and tried to notify David Xu but the e-mail
On Fri, 13 May 2005, Hervé Kergourlay wrote:
ACL_TYPE_ACCESS and ACL_TYPE_DEFAULT are the only implemented types. I
just removed the others from HEAD since they're unnecessary. I'll merge
that change to RELENG_5_4.
great, It's what I did
but I've a problem with the default Acl, the setfacl -d
Robert Watson a écrit :
On Thu, 12 May 2005, Hervé Kergourlay wrote:
2) ACLs
I'm using the API acl_get_file and family with success with
ACL_TYPE_ACCESS defined in /usr/include/sys/acl.h
#define ACL_TYPE_ACCESS 0x
#define ACL_TYPE_DEFAULT0x0001
#define ACL_TYPE_AFS
Seán C. Farley a écrit :
On Thu, 12 May 2005, Seán C. Farley wrote:
On Thu, 12 May 2005, Hervé Kergourlay wrote:
snip
4) wait() API
2 problems, the first is a ECHILD error on a wait call after a fork
fork The code is generic for most of unix system. Is there any
specific problems to manage the
On Fri, 13 May 2005, Hervé Kergourlay wrote:
Seán C. Farley a écrit :
On Thu, 12 May 2005, Seán C. Farley wrote:
On Thu, 12 May 2005, Hervé Kergourlay wrote:
snip
4) wait() API
2 problems, the first is a ECHILD error on a wait call after a fork
fork The code is generic for most of unix system. Is
On Fri, 13 May 2005, Seán C. Farley wrote:
On Fri, 13 May 2005, Hervé Kergourlay wrote:
or if there is a workarouund ?
Reapplying the sigsuspend() before each fork() may work.
I meant sigprocmask(SIG_BLOCK). Sleep deprivation by an infant destroys
the mind. :)
Seán
--
[EMAIL
we are porting our product on FreeBSD 5.3
it's a backup product which is still running on FreeBSD 4.0
here's a list of questions after checking the documentation
1) PAM
it's working, the only problem is with the null password users, the
answer is allways NO. the nullok doesn't seem active
here is
On Thu, 12 May 2005, Hervé Kergourlay wrote:
snip
4) wait() API
2 problems, the first is a ECHILD error on a wait call after a fork fork
The code is generic for most of unix system. Is there any specific problems
to manage the fork and wait APIs ?
the second problem with calls is a blocking
On Thu, 12 May 2005, Seán C. Farley wrote:
On Thu, 12 May 2005, Hervé Kergourlay wrote:
snip
4) wait() API
2 problems, the first is a ECHILD error on a wait call after a fork
fork The code is generic for most of unix system. Is there any
specific problems to manage the fork and wait APIs ?
the
On Thu, 12 May 2005, Hervé Kergourlay wrote:
2) ACLs
I'm using the API acl_get_file and family with success with ACL_TYPE_ACCESS
defined in /usr/include/sys/acl.h
#define ACL_TYPE_ACCESS 0x
#define ACL_TYPE_DEFAULT0x0001
#define ACL_TYPE_AFS0x0002
14 matches
Mail list logo
