t could be relaxed and just do a single scan over the list.
> Unfortunately I haven't a testcase to prove the effectiveness (or
> non-effectiveness) of the approach but I think either Ivan or Peter
> could be able to give it a spin, maybe.
>
I gave this patch a spin
rnel
- anything accessing /dev/mem or /dev/kmem (which implies anything that
uses libkvm) probably needs to match the kernel.
Has anyone investigated this approach?
--
Peter Jeremy
pgpxr8ZptU2HX.pgp
Description: PGP signature
s (which
should be done automatically via IRQ harvesting) and junk into
/dev/random.
--
Peter Jeremy
pgpeZ4geVWmT_.pgp
Description: PGP signature
On 2013-Apr-09 11:05:56 -0700, Freddie Cash wrote:
>You have to look at the in-memory sizes, not the on-disk sizes.
Or, even better, look at the difference between installed physical RAM
and how much RAM is available to userland processes.
--
Peter Jeremy
pgpOHqKqYTU0M.pgp
Description:
gt;printf("Total VM Memory: %i\n",vmsize.t_vm);
>printf("Total Real Memory: %i\n",vmsize.t_rm);
>printf("shared real memory: %i\n",vmsize.t_rmshr);
>printf("active shared real memory: %i\n",vmsize.t_armshr);
>printf("Total Fr
rives weighs in at 36 hours or so.
>
>which is funny as ZFS is marketed as doing this efficient (like checking
>only used space).
It _does_ only check used space but it does so in logical order rather
than physical order. For a fragmented pool, this means random accesses.
>Even better
ance.
Apart from continuous whinging and whining on mailing lists, what have
you done to add support for queuing?
--
Peter Jeremy
pgpPelv8iAQPo.pgp
Description: PGP signature
ivers causing the system to lockup. And I
don't recall (offhand) seeing other reports of it. This again points
to a problem with your particular configuration, rather than FreeBSD.
>And other, non-disk drivers have the same problem of locking out
>other drivers, even during normal operation. And this happens on
>yet other drivers on other people's hardware, not just mine.
Can you provide mailing list or PR references to these.
--
Peter Jeremy
pgpxxy322gDTO.pgp
Description: PGP signature
Hello,
Mark Saad longcount.org> writes:
>
> All
> I am wondering if anyone has seen this. I pulled down the 9.1-RELEASE
> install media and did a clean install . After installing some ports from
> the packages on
> ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9-stable
>
> I noticed t
a way to boot from different partitions, much less
>>> different disks with GPT.
Yes, this is a limitation of FreeBSD's GPT loader. So far, no-one has
written the code to support multiple boot partitions or disks. Note
that most BIOS's allow you to select the boot disk - which is a
workaround.
--
Peter Jeremy
pgpgEyjjmIWvx.pgp
Description: PGP signature
wait a bit.
>>
>> Normally it takes about 15 minutes for it to sync and cron to catch
>> up.Something else is going on here. Clusteradm, can you comment?
>
> It took almost an hour on Sunday, FYI.
> -Garrett
cvsup and cvsupd started giving SIGBUS after the last inst
into the cache/free page queues than M_WAITOK does and
> > reintroduce a M_USE_RESERVE-like flag that says dig deep into the
> > cache/free page queues. The trouble is that we then need to identify all
> > of those places that are implicitly depending on the current behavior o
so they all SIGCONT their children. Repeat. (Note
that any scheduler changes also need to cope with this).
[*] Typical cc1/cc1plus behaviour is to steadily grow as the input is
processed. At higher optimisation levels, parse trees are not
freed at the end of a function to all
ure as a whole then the scheduler just stops scheduling some of
them until the pressure reduces (effectively swap them out). (Yes,
that's vague and lots of hand-waving that might not be realisable).
--
Peter Jeremy
pgpOxQEkEC3S2.pgp
Description: PGP signature
the result to the output file in order.
Of course, this would incur a small penalty in that the dictionary would
not be reused between blocks, but it might still be worth it.
G'luck,
Peter
--
Peter Pentchev r...@ringlet.net r...@freebsd.org pe...@packetscale.com
PGP key:http://people.F
erent, is that both -g and other debugging options will
>generally cause compiling and linking to take longer, since these stages
>will have to process the additional debug information.
As well as being much larger - several times larger is not uncommon.
This further slows things down due to t
are not encoded in
>reverse form).
I suggest you look at xdr(3) and rpcgen(1)
--
Peter Jeremy
pgpSy5s1R6Dmk.pgp
Description: PGP signature
dmamem tag when it starts). It all seemed to work OK.
I haven't tried it on the box where I originally saw the problem
because that's running 8.x. I'll have a look at backporting your
and alc@'s fixes when I get some spare time.
--
Peter Jeremy
pgpNNsdrw2Bk7.pgp
Description: PGP signature
age
rate should be very close to that requested.
--
Peter Jeremy
pgpaFY3z3IfaV.pgp
Description: PGP signature
the following be installed as /usr/bin/nslookup:
#!/bin/sh
echo "nslookup is no longer supported. Please see drill(1) or host(1)" >&2
exit 1
--
Peter Jeremy
pgpP08j1bRN4J.pgp
Description: PGP signature
Firstly, I should note that I'm not against removing bind from base.
I'm merely saying that users are going to need some guidance during
the transition.
On 2012-Jul-09 13:52:15 -0700, Doug Barton wrote:
>On 07/09/2012 13:47, Peter Jeremy wrote:
>> On 2012-Jul-09 14:15:1
for handling the private hosts in a SOHO environment?
--
Peter Jeremy
pgpJAciudHfKN.pgp
Description: PGP signature
On 2012-Jul-03 21:17:53 +1000, Peter Jeremy wrote:
>I have a reasonably recent 8-stable/amd64 system (r237444) with a "ATI
>Radeon HD 2400 Pro", xorg-server-1.10.6,1 and xf86-video-ati-6.14.3_1
>8GB RAM and ZFS. I'm seeing fairly consistent problems with Xorg
...
>H
ND }
wired into gcc to help people migrating from Algol and Pascal.
--
Peter Jeremy
pgp8dpJReQa4x.pgp
Description: PGP signature
their .profile/.login/.[t]cshrc files.
Note that I'm not currently interested in this functionality and am
not volunteering to implement it.
--
Peter Jeremy
pgpLiwmiVDNPP.pgp
Description: PGP signature
On 2012-Jul-03 21:17:53 +1000, Peter Jeremy wrote:
>Does anyone have a tool that can display physical RAM allocation?
>This would at least allow me to identify offending allocations.
>http://lists.freebsd.org/pipermail/freebsd-hackers/2011-February/thread.html
>asks the same quest
sts.freebsd.org/pipermail/freebsd-hackers/2011-February/thread.html
asks the same question but just peters out.
--
Peter Jeremy
pgpuclQzdFSg9.pgp
Description: PGP signature
his).
>there is IMHO already too much automata in default FreeBSD:
>default /etc/crontab, /etc/newsyslog.conf and /etc/periodic directory.
>
>All gets deleted by me as soon as i install FreeBSD.
You are free to disable or delete as much of FreeBSD as you like but I
personally prefer my systems to reduce my workload by automating normal
maintenance tasks.
--
Peter Jeremy
pgp749EyaVr0n.pgp
Description: PGP signature
On 2012-Jun-21 10:09:01 -0700, Doug Barton wrote:
>On 06/21/2012 05:28 AM, Peter Jeremy wrote:
>> 32.0s - rc scripts ("mounting root" through VTY login prompt)
>
>I think that there is some confusion about what I wrote originally, so
>let me clarify. From the time tha
for input"
timeouts. The kernel amounts for 10% of the total time and 50% of
that is 4 devices. I intend to work through the rc process in more
detail to see where I can reduce the elapsed time.
--
Peter Jeremy
pgpfk36pZhHvM.pgp
Description: PGP signature
rc scripts. I know dougb@ regularly picks up
issues with new & updated ports but it's not realistic to rely on him
manually picking up every rc script error.
--
Peter Jeremy
pgpvt6oBaRAkM.pgp
Description: PGP signature
explained.
You are the only person that is claiming that 8.x is EOL. I have not
seen any official announcement to that effect. The absence of an
announcement of 8.4-release does not make it EOL.
--
Peter Jeremy
pgpxLxs9FqeLP.pgp
Description: PGP signature
On 2012-Jun-13 21:55:22 +0200, Hans Petter Selasky wrote:
>Try setting:
>
>sysctl hw.usb.no_boot_wait=1
Note that this is a tunable and will need to be specified in /boot/loader.conf
to have any effect.
--
Peter Jeremy
pgpojiOBCDYfk.pgp
Description: PGP signature
er-process level. Unfortunately, the only documentation appears to
be the source (sys/fs/procfs/procfs_map.c)
--
Peter Jeremy
pgpPIwypWnWVm.pgp
Description: PGP signature
- firefox generates quite a heavy write load
during normal use. Moving the cache to /tmp will help but I don't
think there's any complete solution.
Also, you're probably better off running a traditional lightweight
window manager than something like KDE or Gnome.
--
Peter Jeremy
pgpxd8fhB1HUY.pgp
Description: PGP signature
On 2012-May-18 22:54:43 +0200, Dimitry Andric wrote:
>Be sure to use "-t enable" when creating the filesystem:
Only if your SSD supports TRIM. Some consumer-grade SSDs don't and
get very confused if sent TRIM commands.
--
Peter Jeremy
pgp2LuXn5iRWb.pgp
Description: PGP signature
synchronous write to disk before it can return the acknowledgement
back to the client.
--
Peter Jeremy
pgpDukb68dqQA.pgp
Description: PGP signature
OS provide a mode that suits your monitor, you
will need custom driver code.
--
Peter Jeremy
pgpavw3qB3HKy.pgp
Description: PGP signature
t; 4BSD(I had gotten the impression that once TSF_AFFINITY is set it
> >> could never be cleared).
> >
> > Do you have a pathological test-case for it? Are you going to test the
> > patch?
>
> BTW, I've just now updated the patch i
current driver, or who is
having a serious issue with the current driver will want the update.
Someone who isn't having problems won't want to touch their driver in
case it introduces problems with their system.
--
Peter Jeremy
pgpVm8HHD84Kg.pgp
Description: PGP signature
up enough to return to that state.
If you really want to trim low-hanging fruit, try disposing of libtool
and GNU configure instead - their overheads are _many_ orders of
magnitude higher than make exec()ing gcc.
--
Peter Jeremy
pgpi5RM6Xcqpb.pgp
Description: PGP signature
sure
how practical it would be. http://www.raspberrypi.org/archives/28
makes it fairly clear that the multimedia side will be all closed
source and relevant datasheets will not be available.
--
Peter Jeremy
pgpjYASZmxhP3.pgp
Description: PGP signature
he best interface on
FreeBSD would be kvm_getprocs(3).
BTW, since you mention heap objects, I presume you are aware that
malloc() uses mmap(), rather than sbrk() to obtain memory.
--
Peter Jeremy
pgphug33XKVIW.pgp
Description: PGP signature
at new line, like .Xr and .Nm make editing
> these files in generic-purpose text editor very uncomfortable, IMHO.
Vim seems to automagically switch into 'nroff mode' and editing is
actually quite nice and easy, IMHO.
G'luck,
Peter
--
Peter Pentchev r...@ringlet.net r...@freeb
hat may not be as accurate as the author intended. I think a better
way of looking at the problem is that some code was designed on the
assumption that certain operations were cheap and therefore uses those
operations more freely than it would have had those operations been
more expensive.
--
Peter Jer
On Thu, Sep 8, 2011 at 3:25 PM, Peter Grehan wrote:
>> I'm proposing an extension framework for the bootinfo structure used
>> to pass information from the bootstrap/loader to the kernel. Although
>> I'm only proposing this for the MIPS bootinfo, it's comple
nsion structure:
bootinfo_pext, surrounded by #ifdef BOOTINFO_PEXT
Any reason not to put the vendor bits into another piece of loader
metadata ? That seems the extensible way to add additional info from the
loader, rather than extending bootinfo (as was the case pre-loader days).
ick but there is no standard for this.
--
Peter Jeremy
pgpvoAwjmooj4.pgp
Description: PGP signature
d out from CVS
467 485 509557656 /usr/src 8-stable checkout from CVS
Note that the ports tree grew by 50% going from 1K to 2K frags and
will grow by another 70% going to 4KB frags. Similar issues will
be seen when you have lots of small file.
--
Peter Jeremy
pgp3V7msgMGk0.pgp
Description: PGP signature
of_fds[i], &readfds);
> }
--
Peter Jeremy
pgpdiN44x0CiJ.pgp
Description: PGP signature
end-pr to
formally log them so they don't get lost.
--
Peter Jeremy
pgpfo8hhIEWmy.pgp
Description: PGP signature
#x27;s boot
>code sees that slice 4 is active and boots slice 4.
Multibooting worked correctly when I last used it (a few years ago).
Have you raised this as a PR?
>RS-232 console + hardware modem + POTS = remote console
And even that doesn't fully work unless you have a serial-aware
x27;m not sure if you've take into account is process-
initiated library loading (using dlopen(3) and friends). Note that
even /bin/sh can do this through things like locale handling.
--
Peter Jeremy
pgpj6ptimMgB2.pgp
Description: PGP signature
bably some others as well).
r217151 for amd64 and r217400 for ppc. It doesn't appear to be
supported on other platforms. My reading of the code is that there is
a single shared page used by all processes/CPUs. In order to support
non-synchronised TSCs, this would need to be changed to per-CPU.
--
rent CPU, resulting in an incorrect page being accessed.
--
Peter Jeremy
pgpHImAnkRcSI.pgp
Description: PGP signature
mand as a session group leader
in the style of daemon(8) (but without detaching or daemonizing :)
I think it might not be too hard to implement it under FreeBSD.
G'luck,
Peter
--
Peter Pentchev r...@ringlet.net r...@freebsd.org pe...@packetscale.com
PGP key:http://people.FreeBSD.
stack probing? Is alloca used? Are variable length arrays used?
Peter
On 1/14/11 13:11 PM, "Ryan Stone" wrote:
> On Fri, Jan 14, 2011 at 3:52 AM, Peter Blok wrote:
>> > Hi,
>> >
>> > I¹m probably missing something but if you require a stack variab
Hi,
I¹m probably missing something but if you require a stack variable to be
aligned why not use a type attribute like __attribute__ ((aligned (8)))
Peter
On 1/14/11 00:34 AM, "Warner Losh" wrote:
> On 01/13/2011 13:28, Kostik Belousov wrote:
>> > On Thu, Jan 13, 20
On Sat, Dec 18, 2010 at 09:24:31PM +, Alexander Best wrote:
> On Sat Dec 18 10, Peter Pentchev wrote:
> > On Sat, Dec 18, 2010 at 08:09:37PM +, Alexander Best wrote:
> > > hi there,
> > >
> > > i just stumbled over these lines:
> > >
>
ign the debug flags to both CFLAGS *and*
> CXXFLAGS?
Uhm... yes, so they can be used in both C and C++ programs :)
...or are you making the mistake I've made too many times (and still
make sometimes) of confusing CXXFLAGS with CPPFLAGS? :)
G'luck,
Peter
--
Peter Pentchev
its my skill set.
I suggest you have a read through http://www.freebsd.org/projects/ideas/
to find something that sounds interesting to you and then contact the
relevant person. If no contact is shown then ask about it here.
--
Peter Jeremy
pgpa6M4hDHi0x.pgp
Description: PGP signature
a descriptor of the file. This
> >>> approach, however, have a side effect that other processes would not be
> >>> able to access the file via its name.
G'luck,
Peter
--
Peter Pentchev r...@space.bgr...@ringlet.netr...@freebsd.org
PGP key:http://peop
ed the
architecture from AMD and renamed it. By the time Intel had called it
EM64T, the FreeBSD Project decided it was too late to rename its port.
That said, this has caused a degree of confusion over the years.
--
Peter Jeremy
pgp8z2gUE46vO.pgp
Description: PGP signature
On 2010-Oct-27 20:17:06 +0200, Dag-Erling Smørgrav wrote:
>Peter Jeremy writes:
>> I've mostly convered to ZFS but still have UFS root (which is basically
>> a full base install without /var but including /usr/src - 94k inodes
>> and 1.7GB). I've run both the
MaxMedian AvgStddev
x 4 9413 9673 95689555.5 107.12143
+ 4 15359 15359 15359 15359 0
Difference at 95.0% confidence
5803.5 +/- 131.063
60.7347% +/- 1.3716%
(
), this
> > should still work. Depending on the setup of the aliases,
> > backup-aliases will still work too. I haven't checked for the other
> > ones.
>
> If you want to keep some "old" files, you just need to press `n' instead of
> `y'
> when
:
>
> trap '/path/to/script' EXIT
>
> > Should execute the contents of that script on every logout. Whether that
> > script is a line by line action or a fully qualified script with
> > functions to call different actions are up to you.
...but, of co
gt;how do I read the battery-backed clock on FreeBSD?
There is no managed access to the RTC in FreeBSD. Your only option to
read the RTC is to directly access its IO port registers via io(4) or
i386_set_ioperm(2)
--
Peter Jeremy
pgpi50bk1nXdH.pgp
Description: PGP signature
for quite a while. Are the comments still valid and, if so,
should BKVASIZE be doubled to 32768 and a suitable note added to newfs(8)
regarding the maximum block size?
--
Peter Jeremy
pgp33d0jx50sK.pgp
Description: PGP signature
t in, although
I myself am quite used to typing HTML.
G'luck,
Peter
--
Peter Pentchev r...@space.bgr...@ringlet.netr...@freebsd.org
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553
This senten
oking, right?
Of all the supposedly "portable" build environment tools I've used,
GNU autotools is by far the slowest, most bloated and least portable.
And when you run into problems, you are faced with trying to follow
hundreds of KB of opaque shellscript and obfuscated makefiles.
hand,
and your choice is honored even if later a package with an even higher
priority is installed.
G'luck,
Peter
--
Peter Pentchev r...@space.bgr...@ringlet.netr...@freebsd.org
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint FDBA FD79 C26F 3C51 C95E DF
ot guaranteeing that the code below doesn't have bugs in it as
> I'm not the original author and the tests were originally written and
> targeted towards Linux.
Do you have the P1003_1B_MQUEUE option in your kernel config?
G'luck,
Peter
--
Peter Pentchev r...@space
re not present in my environment, I can avoid the
issue by just commenting out the offending lines. Someone with more
expertise in magic(5) might be able to suggest a better fix.
--
Peter Jeremy
pgpkae67IVhm4.pgp
Description: PGP signature
fferent from
>their predecessors in one way or another.
As an example of an increasingly common CPU that gcc 4.2 doen't
support, consider the Intel Atom. It supports the 'Core' (ie up to
SSSE3) instructions but only does in-order execution (like the
Pentium 1).
--
Peter Jeremy
I've mentioned above, just because some ports
> don't compile, it doesn't affect this project too much.
Well said, well meant. Kudos. Thanks for your work so far, and thanks
for taking up that GSoC project.
G'luck,
Peter
--
Peter Pentchev r...@ringlet.netr...@space.bg
ctory - unless you require from the user to
specify a temporary directory you can use on the same filesystem).
Then, read the original file, write into the new one, and when
you're ready, do a rename(tempfile, realfile).
Hope that helps.
G'luck,
Peter
--
Peter Pentchev r...@space.bgr...@ringlet.netr...@freebsd.org
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553
signature.asc
Description: Digital signature
sctl's and new ones shouldn't be added for trifles,
but still... :)
G'luck,
Peter
--
Peter Pentchev r...@ringlet.netr...@space.bgr...@freebsd.org
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF
On 2010-Mar-27 01:38:36 +0100, Dag-Erling Smørgrav wrote:
>Peter Jeremy writes:
>> It's not especially important how regularly the RTC is updated, just
>> that it _is_ updated. This suggests that an alternative approach
>> would be for adjtime() / ntp_adjtime() to di
ll resettodr()
whilst thread A is doing so, thread B can just skip the call because
calling resettodr() twice in quick succession has no benefit. This
means the serialisation can be a simple atomic_readandclear_int().
--
Peter Jeremy
pgpKIlf9OHHpi.pgp
Description: PGP signature
>As stated in a earlier message. This may help get the information you need.
>Just more of a automated approach to compiling these.
Thanks for the script; I'll definitely archive it. Unfortunately, our window
for investigating this problem further is over as this customer is upgrading
their sys
>Also, you should see if
>__svfscanf() calls __srget(). The __svfscanf() call frame may not show up in
>gdb if the compiler re-used the callframe from vsscanf for __svfscanf() as an
>optimization.
I just checked--it does not call __srget()...
___
fr
>Are you absolutely sure the machine you ran gdb on has the exact same libc
>etc. as the customer's machine?
I just connected to the customer's box and generated the stack trace directly
on their box. It looks identical to the one I posted in my original message.
Something's not right here...
>Type "frame 9" and see what it says. If the bug is easily reproducable, try
>reproducing it with a debugging version of libc (buildworld with
>DEBUG_FLAGS=-g)
This crash happened at a production customer site--we have the core and the
matching binary and our logs for the application that crash
I'm reposting this here since it's a pretty low-level discussion. Hopefully
someone here can explain what's going on.
We had an app crash and the resulting core dump produced a very puzzling stack
trace:
#0 0x0008011d438c in thr_kill () from /lib/libc.so.7
#1 0x0008012722bb in abort
uild) and was evolving at a rate incompatible
with the base system.
>As a possible alternative, or at least to learn about others' opinion on
>the subject, I'd like to suggest Lua (http://www.lua.org/).
As someone who has never used Lua, how well does it meet the
requirements above?
--
Peter Jeremy
pgpLSK4hUsCTp.pgp
Description: PGP signature
>So this is arguably a Python bug. Did you contacted anybody who cares about
>the Python ?
I did not, mainly because this link:
http://bugs.python.org/msg61870
seems to imply they are already aware of the problem. I agree it must be a
Python bug though. It worked in 2.5.1 but not in 2.5.5 and
> We'll likely go with this solution instead of downgrading Python and the
> related libraries.
In fact I came up with another solution. I realized that since the problem was
related to the process signal mask, instead of called ntpd directly, wrap it up
in a C app that resets the signal mask t
>Very wild guess, check the process signal mask of the child for both methods
>of spawning.
I'm running ntpd through Python. How do I check the process signal mask? I did
some quick searches and it seems Python does not support sigprocmask().
In my searches I came across this link:
http://bug
a Python thread class. The exception is Python
2.5.1; this succeeds 100% of the time.
>Peter, what platform You use? I use MIPS BCM5354.
We have a variety of 1U and 3U boxes. They all hang the same way.
___
freebsd-hackers@freebsd.org mailing list
ht
>> make install should be done with DEBUG_FLAGS containing -g too, otherwise
>> strip(1) is called on the installed binary.
>
>Doh, yes.
I did not do this; that's likely my problem. Thanks.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freeb
>I bet ntpd doesn't call select() in all that many places. Instead of going to
>all this trouble to build a debugging libc, you could just
>grep for select() and place breakpoints on all occurrences. (It might also be
>obvious from looking at them which one is the offender.)
I just checked--th
>> How do I get libc built with full debug symbols?
>
>I haven't tried it by myself but think here is the way to go: put the
>following to /etc/make.conf and recompile needed libraries / ports.
>WITH_DEBUG=yes
>DEBUG_FLAGS=-g
That didn't seem to have any effect. I still see -O2 being used instea
>> What's the proper way to build a debug version of libc and the other
>> libraries? I tried this:
>
>You can just do this:
>
>cd /usr/src/lib/libc
>make clean
>make DEBUG_FLAGS=-g
>make install
When I tried this the make actually failed with various errors. So I decided to
do a full "make buil
>You're going to need a debug version of libc, too. gdb won't be able to find
>a backtrace out of a libc function without it.
What's the proper way to build a debug version of libc and the other libraries?
I tried this:
export CFLAGS="-O0"
make buildworld
make installworld DESTDIR=/mydir
and
>You're going to need a debug version of libc, too. gdb won't be able to find
>a backtrace out of a libc function without it.
Yeah, you're right. This is definitely an annoying bug...
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.o
>Just out of curiosity, can you attach to the process via gdb and get a
>backtrace? This smells like a locked pthread_join I hit in my own code a few
>weeks ago
I'm not using the debug version of ntpd so the backtrace isn't too useful, but
here's what I get:
(gdb) bt
#0 0x000800d52bfc in
I posted this originally on the -questions list but did not make any headway.
We have an application where the user can change the date/time via a GUI. One
of the options the user has is to specify that the time is to be synced using
ntp. Our coding worked fine under BSD 7 but since we've moved
me years ago that they would be doubling the number
of threads per CPU socket every 2 years or so.
--
Peter Jeremy
pgpetUC0u65iK.pgp
Description: PGP signature
>>> So, more precisely, if I wanted to boot from drive 1, I'd use this?
>>>
>>> 1:ad(1p3)/boot/loader
>>
>>Yes, unless there are more bugs hiding. :-) I fixed a few in August last year.
>
>Well, I'll give it a try and let you know if I find new bugs... :-)
I just tried this and it works as advert
1 - 100 of 1693 matches
Mail list logo
