2769:	if (limit != RLIM_INFINITY) {
2770:		if (pos >= limit) {
2771:			send_sig(SIGXFSZ, current, 0);
2772:			goto out;
2773:		}
The valus at this point are
limit:         0x7fffffff
RLIM_INFINITY: 0xffffffff
pos:           0x80004000
where limit comes from:
unsigned long	limit = current->rlim[RLIMIT_FSIZE].rlim_cur;
but I did not yet detected the point(s) where
current->rlim[RLIMIT_FSIZE].rlim_cur
is(are) set/changed.
Peter
On Thu, Nov 08, 2001 at 11:13:30AM +0200, Ville Herva wrote:
> On Thu, Nov 08, 2001 at 10:00:14AM +0100, you [Peter Seiderer] claimed:
> > Hello,
> > first thank you for your effort.
> > 
> > Did the diff: nearly no difference till the failure point (only pid, time
> > etc.). Peter
> 
> And there really are no resource limits nor quota?
> 
> At this point you'll propably have to dig into glibc / kernel source and try
> to find out what might cause that...
> 
> 
> -- v --
> 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/