On Fri, 16 Sep 2011, David Watson wrote:
So my question is how can I change the timer frequency of the kFreeBSD
kernel? Actually is there any way to confirm the timer frequency is the
issue? Does the FreeBSD kernel support the kernel parameter divider=N? If
so, how do I add that parameter? That
Accepted:
kfreebsd-9_9.0~svn225586-1.debian.tar.gz
to main/k/kfreebsd-9/kfreebsd-9_9.0~svn225586-1.debian.tar.gz
kfreebsd-9_9.0~svn225586-1.dsc
to main/k/kfreebsd-9/kfreebsd-9_9.0~svn225586-1.dsc
kfreebsd-9_9.0~svn225586.orig.tar.gz
to main/k/kfreebsd-9/kfreebsd-9_9.0~svn225586.orig.tar.gz
kfreebsd-9_9.0~svn225586-1_kfreebsd-amd64.changes uploaded successfully to
localhost
along with the files:
kfreebsd-9_9.0~svn225586-1.dsc
kfreebsd-9_9.0~svn225586.orig.tar.gz
kfreebsd-9_9.0~svn225586-1.debian.tar.gz
kfreebsd-source-9.0_9.0~svn225586-1_all.deb
kfreebsd-headers-9.0-0_9.0~s
Probably you are the uploader of the following file(s) in
the Debian upload queue directory:
kfreebsd-9_9.0~svn225586-1.debian.tar.gz
kfreebsd-9_9.0~svn225586-1.dsc
kfreebsd-9_9.0~svn225586.orig.tar.gz
This looks like an upload, but a .changes file is missing, so the job
cannot be processed.
Ah, now that makes sense. Kinda. It still doesn't explain why the result
is random. :-)
"true" sometimes exits too fast, "sleep 0.1" suffices.
Due to userspace implementation (via pthread_cond_timedwait),
/bin/true might end even before the signal is delivered.
BTW, I just verified, only kfreeb
On Fri, Sep 16, 2011 at 09:11:28PM +0200, Petr Salinger wrote:
fail on subsequent runs. Much smaller (order of magnitude) numbers seem
ok, and I haven't identified a specific bad number. In a loop, 8
seems ok, while 9 exhibits intermittant failure. Assuming that
holds true, we cou
fail on subsequent runs. Much smaller (order of magnitude) numbers seem
ok, and I haven't identified a specific bad number. In a loop, 8
seems ok, while 9 exhibits intermittant failure. Assuming that
holds true, we could set the max timeout to about 25 years (which should
suffice f
On Fri, Sep 16, 2011 at 07:24:41PM +0200, Petr Salinger wrote:
If any debian-bsd people could add some insight to this one, it would be
appreciated.
I've tried various test values, and it doesn't require the time be
exactly MAX_INT to fail (smaller values fail also).
Please which one ?
The 4
If any debian-bsd people could add some insight to this one, it would be
appreciated.
I've tried various test values, and it doesn't require the time be
exactly MAX_INT to fail (smaller values fail also).
Please which one ?
The 49711 days really overflows.
The prior version of timeout didn'
If any debian-bsd people could add some insight to this one, it would be
appreciated.
mstone@kfbsd:/tmp/coreutils-8.13/src$ ./timeout 49711d true ; echo $?
0
mstone@kfbsd:/tmp/coreutils-8.13/src$ ./timeout 49711d true ; echo $?
0
mstone@kfbsd:/tmp/coreutils-8.13/src$ ./timeout 49711d true ; ech
Hi I'm running Debian GNU/kFreeBSD (kernel: 8.2 amd64) as a guest using
VirtualBox (4.0.12) on a Windows 7 Professional host. I also have several
other vms, including Debian GNU/Linux (kernel: 3.0.0 amd64). My physical
machine is an AMD 64-bit hexa-core with 12GB ram.
Now normally, when I have no
11 matches
Mail list logo
