6.1 libpthread: pthread_create and _pq_insert_tail: Already in priority queue
A rather largish application (the most recent version of GHC, see lang/ghc) fails in its runtime system with: _pq_insert_tail: Already in priority queue Basically some threads and mutexes are involved, then the application forks, some more threads are created and then I get this error on a pthread_create(). If I use libmap.conf to map libpthread to either libthr or libc_r, the error doesn't occur. I'm a bit baffled by this...any pointers are welcome! This is mentioned on some MySQL-lists as well, but never with an explanation :| Maybe the runtime is violation some assumptions on what it should be able to do with threads, but I couldn't find anything interesting. Cheers, Volker -- http://www-i2.informatik.rwth-aachen.de/stolz/ *** PGP *** S/MIME All the excitement lies in pattern matching. (SPJ et al.) pgp5nA256gLN4.pgp Description: PGP signature
Re: Article on Sun's DTrace
In local.freebsd-hackers, you wrote: I haven't seen above well yet. But A article says that DTrace sounds like 30,000 lines of debug print. No, already the first article tells you that they use a VM with byte-code for the C-like language D. And it's not compiled into the kernel but hooked in and removed on-the-fly. Volker -- http://www-i2.informatik.rwth-aachen.de/stolz/ *** PGP *** S/MIME Neu! Ändern Sie den Anfangstag Ihrer Woche ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: unexpected trafic
In local.freebsd-hackers, you wrote: My freebsd5.1 emits some trafic: 20:32:41.496039 129dial.supernet.kz.52075 GATEKEEPER.MCAST.NET.1718: udp 31 H.323 (VoIP) Gatekeeper Discovery http://www.cs.columbia.edu/~hgs/rtp/h323.html -- http://www-i2.informatik.rwth-aachen.de/stolz/ *** PGP *** S/MIME Neu! Ändern Sie den Anfangstag Ihrer Woche ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ipfw/ipf IP filtering thoughts
In local.freebsd-hackers, you wrote: In ipchains and iptables you have a sequential list of rules, very much like in ipfw and ipf, but you can have several different lists which have symbolic names and you can make calls from lists to other lists based on normal packet criteria. If the list is exchausted, the scan returns to the previous list. You should be able to accomplish the same -- although in a more convoluted way -- with ipf[w]. You might want to use a higher-level tool though instead of writing all the rules by hand. Try using fwbuilder or code your own ab- straction which translates to ipfw rules. Volker -- http://www-i2.informatik.rwth-aachen.de/stolz/ *** PGP *** S/MIME rage against the finite state machine ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
ITIMER_VIRTUAL running in child after fork()?
The man page for fork() says: · All interval timers are cleared; see setitimer(2). So clearly ITIMER_VIRTUAL should be cleared as well, but a quick test showed that a fork()ed child still has the VIRTUAL ( PROF) timer running. Is this right? -- http://www-i2.informatik.rwth-aachen.de/stolz/ *** PGP *** S/MIME rage against the finite state machine ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Are write() calls guaranteed atomic?
In local.freebsd-hackers, you wrote: Thanks for the info, very helpful! What reference did you get that from? I searched high and low to find a definitive answer (like the one above) before posting. You can find an online version of the Single Unix Specification v3 at http://www.unix-systems.org/version3/online.html (although it's kind of hard to guess that you need that document from the write(2) man page). -- http://www-i2.informatik.rwth-aachen.de/stolz/ *** PGP *** S/MIME rage against the finite state machine ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP Client DoS
In local.freebsd-hackers, you wrote: We've recently found a problem with dhclient that can DoS a DHCP server. If you have schg flags set on /etc/resolv.conf to stop dhcp overwriting your existing nameservers, the problem occurs. Basically, the client just keeps rejecting the IP details it has received from the server and requesting another. The server marks the record as used, and moves onto the next one. Over the course of a couple of minutes, you can pretty much mark an entire class C as in use. The problem of read-only resolv.conf is already documented in the PR database and I think recently somebody started thinking about a solution. Check http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/38778 That the server runs out of IPs is his probably his own fault. It should be configured to not eat up all IPs when a host which already has obtained a lease requests another one but simply hand out the old one or deny the request... Stijn: Could you add your suggestion to the above PR? -- http://www-i2.informatik.rwth-aachen.de/stolz/ *** PGP *** S/MIME rage against the finite state machine To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Bad crash with if_bge when loaded as module in loader.conf
In local.freebsd-hackers, you wrote: Even more bad is that there is no escape from serial console, I can do what I like, call boot(), panic() etc. I get a endless loop. This is 4.7 STABLE from today. It panics when I try to ifconfig the bge0 interface. Wild guess: You have miibus compiled into the kernel and it gets pulled in a second time when kldloading if_bge? -- http://www-i2.informatik.rwth-aachen.de/stolz/ *** PGP *** S/MIME rage against the finite state machine To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: idprio
In local.freebsd-hackers, you wrote: Speaking of idprio... I liked the good old days (3.x) when you didn't have to be root to use the command. Given that idprio can be used to raise priorities as well as lower them, I can see the point of having some restrictions, but shouldn't it be possible to structure the code such that a non-root user can lower but not raise the priority on a process they own? It's in the BUGS section: BUGS ... Under FreeBSD system calls are currently never preempted, therefore non- realtime processes can starve realtime processes, or idletime processes can starve normal priority processes. -- Wonderful \hbox (0.80312pt too nice) in paragraph at lines 16--18 Volker Stolz * [EMAIL PROTECTED] Please use PGP or S/MIME for correspondence! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: PAM, setusercontext, kdm and ports/32273
In local.freebsd-hackers, you wrote: I'll accept that there might be bad interactions between PAM and setusercontext() that I haven't considered. I'm not familiar enough with PAM to know what those would be. For example you have to think about which flags to pass to setusercontext() and when to call it. Doing it whit LOGIN_SETALL *after* pam_setcred is definitely the wrong choice. In any case, hacking kdm is considerably less work, so I might as well do that first. But beware of those convoluted #ifdefs. In gdm, things where much easier. -- Wonderful \hbox (0.80312pt too nice) in paragraph at lines 16--18 Volker Stolz * [EMAIL PROTECTED] Please use PGP or S/MIME for correspondence! To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: login(1) now forks the shell instead of exec'ing it ?
In local.freebsd-stable, you wrote: Anyway, I am a bit sad after losing the traditional login(1) behavior. :-) You're right, it even makes things harder to understand ( verify). There do exist other languages which will allow you to do something similar to calling login, but returning to your code afterwards. But I'm really oversimplyfying things and you surely don't want to use these programming languages for OS binaries (yet!) :-) OTOH, how about passing on PAM-credentials on to login and telling it via a switch to close PAM on termination? Of course this would imply some magic, I'm sure. [F'Up to -hackers. Maybe someone has a flash of inspiration?] -- Volker Stolz * [EMAIL PROTECTED] * PGP + S/MIME To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: DRI, XFree86-4.0.3 and -current.
In local.freebsd-hackers, you wrote: On Thu, Sep 06, 2001 at 12:16:19PM -0700, Eric Anholt wrote: I have a page about the DRI for FreeBSD at=20 http://gladstone.uoregon.edu/~eanholt/dri/. The current DRI CVS works on= I had a look at that, but it wasn't too clear what I needed to do. I suspect that I'm expecting to checkout the DRI tree _over_ the top of the XFree86-4 tree but perhaps I don't need to do that. Neither was I. Could you clarify on merging XFree from the ports and the CVS? I tried copying the CVS-stuff over the port, but the build stopped with: cleaning in programs/Xserver/hw/xfree86/input/calcomp... cd: can't cd to calcomp [Might be my fault, after-all. R-To: -multimedia?] -- Neues aus Genua? http://germany.indymedia.org/ Volker Stolz * [EMAIL PROTECTED] * PGP + S/MIME To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: licq socks5 (fwd)
In freebsd-hackers, you wrote: i`m trying to compiling licq with socks5 support, but i`d received following message: -Wl,--export-dynamic -L/usr/local/lib -lsocks5 -lssl -lcrypto -lc_r -lc_r socket.o: In function `INetSocket::SetLocalAddress(bool)': socket.o(.text+0x6d6): undefined reference to `SOCKSgetsockname' socket.o: In function `INetSocket::OpenConnection(void)': Which FreeBSD version are you running? Are you using the port in /usr/ports/net/licq, as you should? This doesn't cause any trouble for me. LDFLAGS=-L/usr/local/lib CPPFLAGS=-I/usr/local/include make WITH_SOCKS=1: ... c++ -O -pipe -march=pentium -fno-exceptions -fno-check-new -pthread -o licq licq.o main.o icqpacket.o socket.o icqd.o icqd-udp.o icqd-tcp.o icqd-threads.o remoteserver.o icqevent.o buffer.o user.o history.o utility.o countrycodes.o log.o translate.o file.o message.o support.o pthread_rdwr.o onevent.o plugind.o sar.o languagecodes.o icqd-chat.o sighandler.o icqd-filetransfer.o hebrev.o icqcolor.o -Wl,--export-dynamic -L/usr/local/lib -lsocks5 -lssl -lcrypto -lc_r -lc_r gmake[2]: Leaving directory `/opt/ports/net/licq/work/licq-1.0.3/src' FreeBSD monster.ikea.net 4.4-PRERELEASE FreeBSD 4.4-PRERELEASE #27: Sun Aug 12 16:42:41 CEST 2001 [EMAIL PROTECTED]:/opt/obj/opt/src/sys/MONSTER i386 -- Neues aus Genua? http://germany.indymedia.org/ Volker Stolz * [EMAIL PROTECTED] * PGP + S/MIME To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: [RFC] whois(1) - recursive IP searches
In local.freebsd-hackers, you wrote: I would appreciate comments on the following patch: http://testbed.q9media.net/freebsd/whois.20010622.patch o Implement recursive IP Address searches based on the results of a query to ARIN. This allows a user to type 'whois 210.139.255.223' and get the expected results. [Requested by joe and phk] This and some of the other stuff discussed recently looks like what other people have been building into whois-*servers* like whois.thur.de by [EMAIL PROTECTED] (just try 'whois -h whois.thur.de 210.139.255.223'). Why not keep whois(1) lean and put the custom stuff in a port? On the other hand, I fully understand that people might disagree :) -- Abstrakte Syntaxträume. Volker Stolz * [EMAIL PROTECTED] * PGP + S/MIME To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: smbfs: disconnected servers
In local.freebsd-stable, you wrote: However, the problems begin when somebody whose share I mounted decides to switch off his computer: I (obviously) cannot read from the mountpoint anymore, but there also is _no way_ of forcefully unmounting the share anymore. Maybe smbfs should be ported to userland (portal) somehow? I'm not saying im volunteering, though ;) But I'd like to know if there are any limitations which might prevent this from working... I think I ran into the same troubles with sharity-light, because of the usual lock-ups when NFS become unavailable. -- Abstrakte Syntaxträume. Volker Stolz * [EMAIL PROTECTED] * PGP + S/MIME To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: ping over IPSEC works in only one direction
In local.freebsd-hackers, you wrote:
spdadd 192.168.1.1 192.168.1.101 any -P out ipsec esp/transport//use
ah/transport//use;
spdadd 192.168.1.101 192.168.1.1 any -P out ipsec esp/transport//use
ah/transport//use;
I can see no corresponding "... any -P in" rules. Did you forget them only
in the posting? If not, this is likely to be a source of confusion.
--
\usepackage[latin1]{inputenc}!
Volker Stolz * [EMAIL PROTECTED] * PGP + S/MIME
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Questions on i2c
Hi, is someone working actively on new i2c-stuff?
I´d be interested in talking to someone who could take a short peek at
http://www2.lm-sensors.nu/~lm78/info.html, a Linux-site providing
i2c-drivers to various things, and could comment on the feasibility of
using their stuff to implement FreeBSD-drivers.
Devices include video-devices like TV-Out on the Voodoo3 which could
seemingly be enabled using i2c.
FreeBSD´s bktr-driver seems too big for me to get me started on trying
to attach only a driver which would look for the Voodoo.
Is there any further documentation on what I can do with /dev/iic*?
Regards,
Volker
--
\usepackage[latin1]{inputenc}!
Volker Stolz * [EMAIL PROTECTED] * PGP + S/MIME
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: waiting for new files in a directory
Am 28. Dec 2000 um 10:33 MET schrieb Dan Langille:
What about a daemon signalling a waiting perl script?
Is it an issue if the daemon signals the perl script when it's already
processing? Could a signal be missed?
How about using a FIFO (maybe in /tmp) and let the daemon printf,echo,cat,...
control-msgs into the FIFO and have a perl script sitting on the other end?
Signals suck. Another advantage would be that the perl script could choose
it´s own pace and let things queue up in the FIFO. However, a FIFO only
has limited capacity. If I´d be using Haskell (http://www.haskell.org), I´d
throw in a forkIO() and would get a neatly multi-threaded solution where one
thread reads the FIFO and queues up requests while the other thread queries
him for more work -- I don´t know about threaded perl, though.
--
\usepackage[latin1]{inputenc}!
Volker Stolz * [EMAIL PROTECTED] * PGP + S/MIME
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: waiting for new files in a directory
On Thu, Dec 28, 2000 at 01:35:08PM +0100, Dag-Erling Smorgrav wrote:
What are you guys smoking?
*shrug* Can you spell "event-driven"? There are ways to do things much
more elegantly today (see all the references to kevent()).
--
\usepackage[latin1]{inputenc}!
Volker Stolz * [EMAIL PROTECTED] * PGP + S/MIME
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
$CDB in /usr/src/usr.sbin/pw/Makefile
Does someone know what the variable CDB is doing in
/usr/src/usr/sbin/pw/Makefile? I was using this variable for my
own purposes and thus it caused minor havoc when building world:
CFLAGS+= -W -Wall $(CDB) $(RND)
I couldn´t find any other reference to the variable. Any suggestions?
Otherwise I´d suggest a PR for removing the variable or at least
setting it to "" in a top-level makefile.
--
\usepackage[latin1]{inputenc}!
Volker Stolz * [EMAIL PROTECTED] * PGP + S/MIME
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Broken PCI-IDE RZ1000 ata
The RZ1000 PCI-IDE controller found on at least one Intel board is severely broken and requires a workaround which is available for Linux (at least it turned up in the config for 2.4.0, though the board should be a couple of years old, it's for regular Pentium-I). Could anyone comment on this to get it working with FreeBSD? sysinstalls gets write-errors after a couple of kilobytes, and when running an already installed system, mount/fsck bomb with sig 11, after that you find yourself in single-user mode with every command (including 'reboot'!) yielding a SIGILL. Funny sight, though. -- Volker Stolz * [EMAIL PROTECTED] * PGP + S/MIME To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Virus alerts messages
On Thu, Nov 02, 2000 at 10:11:02AM +0100, Arjan Knepper wrote: Anyone else receiving about 50 virus alerts messages in 30 minutes? Stopped a minute ago here -- procmail's your friend ;). Okay, this doesn't keep your MDA from receiving them in the first place. I guess someone's going to get their heads washed. -- Volker Stolz * [EMAIL PROTECTED] * PGP + S/MIME To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Broken PCI-IDE RZ1000 ata
Am 02. Nov 2000 um 16:42 MET schrieb Terry Lambert: The RZ1000 PCI-IDE controller found on at least one Intel board is Well, that chip is so broken by design, no software workaround can help its misery, a hardware fix exists, but cant (easily) be retrofitted. Forget about it, buy a new Promise or whatever if you really need that board, a software only fix is _not_ possible, no matter what linux might tell you Are you sure that you aren't just not setting the right flags on the device? This workaround used to be on by default in GENERIC. Hm...You could set flags on wd?, but not on ata/ad. And this beast is so broken you never reach rc.sysctrl for setting pio. -- Volker Stolz * [EMAIL PROTECTED] * PGP + S/MIME To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Broken PCI-IDE RZ1000 ata
Am 02. Nov 2000 um 17:15 MET schrieb Soren Schmidt: ... the "new and improved" ATA driver states the fact that this chip is broken and can corrupt your data, end of story. Nope, I didn't find any references on this controller. -- Volker Stolz * [EMAIL PROTECTED] * PGP + S/MIME To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Broken PCI-IDE RZ1000 ata
Am 02. Nov 2000 um 17:58 MET schrieb Soren Schmidt: Nope, I didn't find any references on this controller. The ATA driver states the buggyness in the probe. How about putting this in the man-page ;) But why will 4.1-RELEASE happily use WDMA2? -- Volker Stolz * [EMAIL PROTECTED] * PGP + S/MIME To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: high speed timestamp counter
Am 02. Nov 2000 um 19:00 MET schrieb Hao Zhang: I am trying to read the on board Pentium Time Stamp Counter. Is there an API in Unix that allows me to read it directly? Try 'man 4 perfmon'. Remember it requires an option in the kernel, though. -- Volker Stolz * [EMAIL PROTECTED] * PGP + S/MIME To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: [mount.c]: Option user-patch
I suppose there already was a rather lengthy discussion about a "user"-option. I hope this sysctl-thing will make it into the mount-manpage, because if not, it might turn out to be a really FAQ :) -- Volker Stolz * [EMAIL PROTECTED] * PGP To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: [mount.c]: Option user-patch
I suppose there already was a rather lengthy discussion about a user-option. I hope this sysctl-thing will make it into the mount-manpage, because if not, it might turn out to be a really FAQ :) -- Volker Stolz * st...@pool.informatik.rwth-aachen.de * PGP To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
[mount.c]: Option user-patch
Hi, I whacked mount and umount into shape for using an option "user" in /etc/fstab which allows normal users to mount/umount devices. Both programs have to be set-uid-root. I´d like that someone reviews the patches (and includes them :). The diffs are at http://www-i2.informatik.rwth-aachen.de/~stolz/mount.diff http://www-i2.informatik.rwth-aachen.de/~stolz/umount.diff. Discussion welcome! Regards, Volker (not subscribed to the list) -- Volker Stolz * [EMAIL PROTECTED] * PGP To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
[mount.c]: Option user-patch
Hi, I whacked mount and umount into shape for using an option user in /etc/fstab which allows normal users to mount/umount devices. Both programs have to be set-uid-root. I´d like that someone reviews the patches (and includes them :). The diffs are at http://www-i2.informatik.rwth-aachen.de/~stolz/mount.diff http://www-i2.informatik.rwth-aachen.de/~stolz/umount.diff. Discussion welcome! Regards, Volker (not subscribed to the list) -- Volker Stolz * st...@pool.informatik.rwth-aachen.de * PGP To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
