Bug in pthread_cancel()
Hi, Any comments positive or negative to the patch in bin/37614 ? I'd like to commit this soon... http://www.freebsd.org/cgi/query-pr.cgi?pr=37614 Thanks, -Archie __ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
NFS Trouble : no replies from portmap
I use NFS on 2 hosts. The first is running FreeBSD 4.4 (not upgraded) (A) The second runs FBSD 4.5 (not upgraded). (B) On the B machine I can mount the part of the A machine but the B machine cant be mounted on the A machine because of a ' NFSPROC_NULL: RPC: Timed out ' error. Indeed, on the B host : I have 'portmap[10261]: connect from 217.128.180.74 to getport(nfs) server: about to do a switch' every time I try to mount from the A host. I should get a 'mountd successful' after this ... =( Maybe it has nothing to do with Versions of FBSD but I just can't understand why the portmap of the B machine doesn't reply ... portmap is not wrapped through hosts.access and no firewall are blocking pakets on the B host, I run the usual rpc services B# rpcinfo -p program vers proto port 102 tcp111 portmapper 102 udp111 portmapper 132 udp 2049 nfs 133 udp 2049 nfs 153 udp865 mountd 153 tcp990 mountd 151 udp865 mountd 151 tcp990 mountd To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
ipnat.conf syntax ?
Basicly, here is my trouble : mysticjah# cat ipnat.conf rdr ed0 192.168.1.1 port 21 -> 192.168.1.2 port 21 tcp mysticjah# ipnat -f ipnat.conf 1: syntax error in "rdr" What's wrong ? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Why won't bind 8.2.4-REL run properly as as user bind (4.5-REL-p3)not chrooted ?
On Sat, 27 Apr 2002, Stanley Hopcroft wrote: > Dear Ladies and Gentlemen, > > I am writing to ask you help with bind after a recent OS upgrade (from > an old 4.3-STABLE to 4.5-REL-p3). You should not be running a version of named that old. Go install the 8.3.1 version in ports, and change your /etc/rc.conf file to point to /usr/local/sbin/named instead of just 'named'. 8.3.1 has no problems running chroot'ed. Good luck, Doug -- "We have known freedom's price. We have shown freedom's power. And in this great conflict, ... we will see freedom's victory." - George W. Bush, President of the United States State of the Union, January 28, 2002 Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: change in UPDATING
alan> I think it would be a good idea to add a note (similar to the one alan> about using the new mergemaster (with -C option)) to UPDATING that alan> explains that you can use the same formula (cd alan> /usr/src/usr.sbin/mergemaster; make all install) followed by a alan> "mergemaster -p" to fixup the smmsp user/group. Done. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: postfix within jail under FreeBSD 4.5
On Mon, Apr 29, 2002 at 09:37:33AM -0500, Albert Everett wrote: > I while back someone wrote in that postfix doesn't work (without the > right patch) inside jails under FreeBSD 4.5. > > Has there been any change in status on this issue? > I'm running it in several jails under 4.4 as we speak. I did set inet_interfaces = $myhostname (leaving off localhost,) though. -- Denny Reiter [EMAIL PROTECTED] So I don't hurt your feelings:[EMAIL PROTECTED] www.scapegoats.org Have you reconsidered a computer career? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Dell Inspiron 8100 (was: ata (cd) troubles)
On Tue, 2002-04-30 at 19:50, JJ Behrens wrote: > > Works for me on my Dell Inspiron 8100. I have my DVD-ROM as a UDMA 33 > > device. > > Joe, > > What resolution are you using for your Dell Inspiron 8100? I had to build > a version of XFree86 out of CVS in order to get 1600x1200. I'm just wondering > what you did. 1600x1200. I wrote a tech tip at http://www.marcuscom.com/g2g-xfree86/article.html on how to build the necessary CVS components for getting the GeForce2 Go working. Joe > > -jj > > -- > Users of C++ should consider hanging themselves rather than shooting their > legs off--it's best not to use C++ simply as a better C. > -- PGP Key: http://www.marcuscom.com/pgp.asc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
RE: Why won't bind 8.2.4-REL run properly as user bind (4.5-REL-p3) not chrooted ?
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Doug Barton > Sent: Friday, April 26, 2002 8:09 PM > > On Sat, 27 Apr 2002, Stanley Hopcroft wrote: > > > Dear Ladies and Gentlemen, > > > > I am writing to ask you help with bind after a recent OS upgrade (from > > an old 4.3-STABLE to 4.5-REL-p3). > > You should not be running a version of named that old. Go install > the 8.3.1 version in ports, and change your /etc/rc.conf file to point to > /usr/local/sbin/named instead of just 'named'. 8.3.1 has no problems > running chroot'ed. > Stanley, are you sure you're upgrade went as planned? If you're running 4.5, you should be running 8.3.1-REL, which is in /usr/src/contrib/bind. Check the Version file in there. Bind 8.2.4-REL is relatively old, and may have some holes in it. I'm not sure if http://www.isc.org/products/BIND/bind-security.html is up to date or not, but ISC recommends 8.3.1 as well. Sameer To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: ASUS A7M266-D: enabling 'on board sound'
On Tue, 23 Apr 2002, John Utz wrote: > huh, bet this might be an smp problem > > works like a champ on my ASUS board. > > > On Tue, 23 Apr 2002, Marc G. Fournier wrote: > > > > > Morning all ... > > > > Just recently picked up an ASUS A7M266-D Motherboard with Dual: > > "(AMD Athlon(TM) MP Processor (1200.05-MHz 686-class CPU)" ... the system > > purrs like the proverbial kitten ... but the one thing that is eluding me > > so far is getting the onboard sound to work ... > > > > I think I've gone through just about everything ... I enabled > > PNPBIOS in my kernel, made sure the sound device was enabled in the BIOS > > ... nadda ... > > > > The error I'm seeing in dmesg is: > > > > pcm0: at device 4.0 on pci2 > > pcm0: cmi_attach: Cannot allocate bus resource > > device_probe_and_attach: pcm0 attach returned 6 > > this could be one of two things: > > 1. your version of the CMI8738 might have a new pnp number, but i sorta > doubt it because then you wouldnt get the 'CMedia CMI8738' string. that is kinda what I'm figuring too ... > 2. All Your Interrupts Are Belong To Somebody Else! > > the extra bits of tomfoolery involved in getting a second cpu to live in > an architecture than never imagined more than one (daisy chained 8259a's, > still?) may have consumed the available interrupts. Actually, I thought about this, and one problem with this theory ... right now, I have both serial ports and the parallel port disabled, which should free up 3/4 and 5 (or is it 7?) ... if I re-enable them, they come up fine with their respective IRQs ;( > 3. Other, more reasonable, but more subtle problems that i cant imagine > :-) > > > I'd suggest the ol' boot -v and see what you get for a dmesg. Will try this one tomorrow at the office ... > > > > I've tried manually setting in the kernel: > > > > > strings /kernel | grep pcm0 > > pcm0_resources > > ___device pcm0 at isa? irq 5 drq 1 flags 0x0 > > > > but that hasn't made any difference ... > > > > Anyone have any experience with this board, or this chipset, that > > might be able to suggest a course of action here? > > > > thanks ... > > > > > > > > > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-multimedia" in the body of the message > > > > -- > > John L. Utz III > [EMAIL PROTECTED] > > Idiocy is the Impulse Function in the Convolution of Life > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: ipnat.conf syntax ?
I may not be the foremost expert on this, but I'm going to take a swing at this one... If you take a look at man ipnat(5), all examples include the /mask. Try this and see if it brings joy: rdr ed0 192.168.1.1/32 port 21 -> 192.168.1.2 port 21 tcp (I tested one of my rdr lines without the mask, and got: 10: no netmask on LHS 10: syntax error in "rdr" when I tried to ipnat -f /etc/ipnat.rules. HTH, John Ricker Microsoft: "Where do you want to go today?" Linux: "Where do you want to go tomorrow?" FreeBSD:"Are you guys coming or what?" - Original Message - From: "fictif" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, April 30, 2002 8:22 PM Subject: ipnat.conf syntax ? Basicly, here is my trouble : mysticjah# cat ipnat.conf rdr ed0 192.168.1.1 port 21 -> 192.168.1.2 port 21 tcp mysticjah# ipnat -f ipnat.conf 1: syntax error in "rdr" What's wrong ? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Build sequence (was Re: mergemaster theory (was: Re:/etc/defaults/rc.conf theory) )
On Tue, 30 Apr 2002, Mike Meyer wrote: > What's missed here is that running an old kernel and a new userland is > more likely to screw things up. In fact this is now broken if you try to build -current on a -stable box. You can't run the -current userland on a -stable kernel to do an install anymore. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Bug in pthread_cancel()
On Tue, 30 Apr 2002, Archie Cobbs wrote:
> Hi,
> Any comments positive or negative to the patch in bin/37614 ?
> I'd like to commit this soon...
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=37614
The patch is for stable, but would need to be applied to -current
first (after some adjustment).
Hmm, what about just bypassing the pthread_cancel() if the
thread is already in the process of exiting?
Index: uthread_cancel.c
===
RCS file: /opt/d/CVS/src/lib/libc_r/uthread/uthread_cancel.c,v
retrieving revision 1.12
diff -u -r1.12 uthread_cancel.c
--- uthread_cancel.c6 Mar 2002 19:28:40 - 1.12
+++ uthread_cancel.c1 May 2002 02:35:23 -
@@ -20,7 +20,8 @@
if ((ret = _find_thread(pthread)) != 0) {
/* NOTHING */
- } else if (pthread->state == PS_DEAD || pthread->state == PS_DEADLOCK) {
+ } else if (pthread->state == PS_DEAD || pthread->state == PS_DEADLOCK
+|| (pthread->flags & PTHREAD_EXITING) != 0) {
ret = 0;
} else {
/* Protect the scheduling queues: */
--
Dan Eischen
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Heads Up: Accept filters fixed
Just a quick note for those of you using accept filters with a 4.4+ kernel
using the syncache: Your accept filters are broken, and easily DoSable.
The fix (attached) has now been committed to both 5.0 and 4.5, so I
recommend doing one of two things if you're using accept filters:
1. Stop using them.
2. Patch or cvsup and rebuild your kernel.
Mike "Silby" Silbersack
-- Forwarded message --
Date: Tue, 30 Apr 2002 20:27:35 -0700 (PDT)
From: Mike Silbersack <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: cvs commit: src/sys/kern uipc_socket.c uipc_socket2.c
silby 2002/04/30 20:27:35 PDT
Modified files:(Branch: RELENG_4)
sys/kern uipc_socket.c uipc_socket2.c
Log:
MFC:
Make sure that sockets undergoing accept filtering are aborted in a
LRU fashion when the listen queue fills up. Previously, there was
no mechanism to kick out old sockets, leading to an easy DoS of
daemons using accept filtering.
Revision ChangesPath
1.116 +1 -2 src/sys/kern/uipc_socket.c
1.87 +7 -1 src/sys/kern/uipc_socket2.c
Revision ChangesPath
1.68.2.21 +1 -2 src/sys/kern/uipc_socket.c
1.55.2.14 +7 -1 src/sys/kern/uipc_socket2.c
diff -u -r /usr/src/sys.old/kern/uipc_socket.c /usr/src/sys/kern/uipc_socket.c
--- /usr/src/sys.old/kern/uipc_socket.c Thu Apr 25 01:24:24 2002
+++ /usr/src/sys/kern/uipc_socket.c Thu Apr 25 01:28:40 2002
@@ -257,7 +257,6 @@
} else {
panic("sofree: not queued");
}
- head->so_qlen--;
so->so_state &= ~SS_INCOMP;
so->so_head = NULL;
}
@@ -1642,6 +1641,6 @@
{
struct socket *so = (struct socket *)kn->kn_fp->f_data;
- kn->kn_data = so->so_qlen - so->so_incqlen;
+ kn->kn_data = so->so_qlen;
return (! TAILQ_EMPTY(&so->so_comp));
}
diff -u -r /usr/src/sys.old/kern/uipc_socket2.c /usr/src/sys/kern/uipc_socket2.c
--- /usr/src/sys.old/kern/uipc_socket2.cThu Apr 25 01:24:24 2002
+++ /usr/src/sys/kern/uipc_socket2.cThu Apr 25 16:43:37 2002
@@ -123,6 +123,7 @@
head->so_incqlen--;
so->so_state &= ~SS_INCOMP;
TAILQ_INSERT_TAIL(&head->so_comp, so, so_list);
+ head->so_qlen++;
so->so_state |= SS_COMP;
sorwakeup(head);
wakeup_one(&head->so_timeo);
@@ -251,12 +252,17 @@
if (connstatus) {
TAILQ_INSERT_TAIL(&head->so_comp, so, so_list);
so->so_state |= SS_COMP;
+ head->so_qlen++;
} else {
+ if (head->so_incqlen >= head->so_qlimit) {
+ struct socket *sp;
+ sp = TAILQ_FIRST(&head->so_incomp);
+ (void) soabort(sp);
+ }
TAILQ_INSERT_TAIL(&head->so_incomp, so, so_list);
so->so_state |= SS_INCOMP;
head->so_incqlen++;
}
- head->so_qlen++;
if (connstatus) {
sorwakeup(head);
wakeup((caddr_t)&head->so_timeo);
Re: Heads Up: Accept filters fixed
At 11:07 PM -0500 4/30/02, Mike Silbersack wrote: >Just a quick note for those of you using accept filters with >a 4.4+ kernel using the syncache: Your accept filters are >broken, and easily DoSable. > >The fix (attached) has now been committed to both 5.0 and 4.5, >so I recommend doing one of two things if you're using accept >filters: How seriously are they broken? Should this be MFC'ed into RELENG_4_5 ? (security-patches branch) -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
