From owner-freebsd-stable Sun Nov 1 00:47:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA29345 for freebsd-stable-outgoing; Sun, 1 Nov 1998 00:47:09 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA29337 for ; Sun, 1 Nov 1998 00:47:06 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0zZtA3-0002se-00; Sun, 1 Nov 1998 00:46:59 -0800 Date: Sun, 1 Nov 1998 00:46:55 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Morgan Davis cc: freebsd-stable@FreeBSD.ORG Subject: Re: pw touches mailbox file In-Reply-To: <199811010629.WAA23256@io.cts.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 31 Oct 1998, Morgan Davis wrote: > The 'pw useradd' function includes an undocumented feature of creating > a mailbox file in /var/mail. There is no flag for disabling this, nor > is it really necessary since it'll get created by sendmail anyway. > But alas, it's there. Depends. Some local delivery agents run as the id of the user it is delivering to. In this case, the mailbox needs to be created. > Unfortunately, the assumption about /var/mail being the location for > mailboxes is problematic if /usr/libexec/mail.local has been modified > to use an alternate location (e.g., to support Qualcomm Popper's > hashed spool directory feature -- /var/mail/j/s/jsmith). Yes, or even Cyrus which doesn't use bezerk mailboxes at all, or some form that puts the mailbox within every users home directory. > Suggestion: If pw must create a mailbox file, it should provide an > option for specifying where that file is, or at least write through > mail.local to honor any local configuration changes. At the very > least, it should have a flag for disabling mailbox creation > altogether. At best, there should be "create_mailbox.sh" shell script that it should run. If you use a local delivery agent that doesn't need it, the script will be empty. If Cyrus, the appropiate cyradm command can be in there. > --Morgan Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 1 01:18:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA02583 for freebsd-stable-outgoing; Sun, 1 Nov 1998 01:18:44 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from luke.cpl.net (luke.cpl.net [209.150.92.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA02577 for ; Sun, 1 Nov 1998 01:18:43 -0800 (PST) (envelope-from shawn@luke.cpl.net) Received: (from shawn@localhost) by luke.cpl.net (8.8.8/8.8.8) id BAA17863; Sun, 1 Nov 1998 01:18:32 -0800 (PST) Message-ID: <19981101011831.B8957@cpl.net> Date: Sun, 1 Nov 1998 01:18:31 -0800 From: Shawn Ramsey To: najib@csi-x.net, freebsd-stable@FreeBSD.ORG Subject: Re: Problem compiling -STABLE References: <363c1632.2da2.0@csi-x.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <363c1632.2da2.0@csi-x.net>; from Muhammad Najib on Sun, Nov 01, 1998 at 04:05:06PM +0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I was wondering .. before this I could compile 2.2.7-STABLE .. but then recently > I did cvsup for RELENG_2_2's src-sys and I got this message when I config the > config file > > csi-x# config JeEbSioN > Unknown % construct in generic makefile: %VERSREQ= 220000 > Kernel build directory is ../../compile/JeEbSioN > csi-x# I don't know if this is the problem, but i've always gotten this error when using an older config. You might want to try updating config and see what happens. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 1 08:25:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA28050 for freebsd-stable-outgoing; Sun, 1 Nov 1998 08:25:06 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.gtn.com (mail.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA28010 for ; Sun, 1 Nov 1998 08:24:54 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by mail.gtn.com (8.8.6/8.8.6) with UUCP id RAA05580 for stable@FreeBSD.ORG; Sun, 1 Nov 1998 17:15:05 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.8) id QAA20159 for stable@FreeBSD.ORG; Sun, 1 Nov 1998 16:59:56 +0100 (CET) (envelope-from andreas) Message-ID: <19981101165956.A20151@klemm.gtn.com> Date: Sun, 1 Nov 1998 16:59:56 +0100 From: Andreas Klemm To: stable@FreeBSD.ORG Subject: make rerelease fails at ===> ja/man/man1 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 2.2.7-STABLE SMP Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ===> ja/FAQ cd /usr/doc/ja/FAQ ; make install DESTDIR=/R/stage/trees/doc SHARED=copies install -c -o bin -g bin -m 444 FAQ*.html /R/stage/trees/doc/usr/share/doc/ja/F AQ if [ -f /usr/doc/ja/FAQ/FAQ.ln ]; then (cd /R/stage/trees/doc/usr/share/doc/ja/ FAQ; sh /usr/doc/ja/FAQ/FAQ.ln); fi install -c -o bin -g bin -m 444 FAQ.roff /R/stage/trees/doc/usr/share/doc/ja/F AQ ===> ja/man cd /usr/doc/ja/man ; make afterdistribute DESTDIR=/R/stage/trees/bin ===> ja/man/man1 cd /usr/doc/ja/man/man1 ; make install DESTDIR=/R/stage/trees/bin SHARED=copies install -c -o bin -g bin -m 444 a2p.1.gz addftinfo.1.gz addr2line.1.gz..... [... very long command line shortened ...] .....yes.1.gz ypcat.1.gz ypmatch.1.gz ypwhich.1.gz yyfix.1.gz zdiff.1.gz zforce .1.gz zmore.1.gz znew.1.gz /R/stage/trees/bin/usr/share/man/ja/man1 usage: install [-CcDps] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 install [-CcDps] [-f flags] [-g group] [-m mode] [-o owner] file1 ... fileN directory install -d [-g group] [-m mode] [-o owner] directory ... *** Error code 64 Stop. *** Error code 1 -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 1 09:15:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA04534 for freebsd-stable-outgoing; Sun, 1 Nov 1998 09:15:23 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from cassiopeia.caprica.com ([207.137.48.14]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA04528 for ; Sun, 1 Nov 1998 09:15:22 -0800 (PST) (envelope-from frank@exit.com) Received: from exit.com by cassiopeia.caprica.com (8.6.10/95022701) id HAA12354; Sun, 1 Nov 1998 07:15:05 -0800 Received: (from frank@localhost) by exit.com (8.8.8/8.7.3) id IAA03008; Sun, 1 Nov 1998 08:37:15 -0800 (PST) From: Frank Mayhar Message-Id: <199811011637.IAA03008@exit.com> Subject: Re: Problem compiling -STABLE To: najib@csi-x.net Date: Sun, 1 Nov 1998 08:37:15 -0800 (PST) Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: <363c1632.2da2.0@csi-x.net> from Muhammad Najib at "Nov 1, 98 04:05:06 pm" X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Muhammad Najib wrote: > I was wondering .. before this I could compile 2.2.7-STABLE .. but then recently > I did cvsup for RELENG_2_2's src-sys and I got this message when I config the > config file > > csi-x# config JeEbSioN > Unknown % construct in generic makefile: %VERSREQ= 220000 > Kernel build directory is ../../compile/JeEbSioN > csi-x# > > hence ... I just ignore this particular problem .. but then when I finished > doing make depend .. and I start doing make ... half way it stop with this error(s) > > > cc -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -nostdinc -I- -I. > -I../.. -I/usr/include -DAPM_BROKEN_STATCLOCK -DIPDIVERT -DFAILSAFE -DCOMPAT_43 > -DMSDOSFS -DNFS -DFFS -DIPFILTER -DINET -DKERNEL -c vers.c > loading kernel > isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > isa.o: Undefined symbol `_isa_devtab_cam' referenced from text segment > *** Error code 1 > > Stop. > csi-x# > > I wonder ... what I did wrong here .... please point me :) > Thanx in advance ... You need to go into /usr/src/usr.sbin/config and do a 'make install'. Config has changed recently, making it necessary to update it before trying to build a kernel. I found out the hard way myself, but in general when something like this happens, updating config first is usually a good thing to try. If that fails, _then_ ask the list. -- Frank Mayhar frank@exit.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 1 11:54:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25525 for freebsd-stable-outgoing; Sun, 1 Nov 1998 11:54:37 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dt053n18.san.rr.com (dt053n18.san.rr.com [204.210.34.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25519 for ; Sun, 1 Nov 1998 11:54:35 -0800 (PST) (envelope-from Studded@gorean.org) Received: from gorean.org (Studded@localhost [127.0.0.1]) by dt053n18.san.rr.com (8.8.8/8.8.8) with ESMTP id LAA01875; Sun, 1 Nov 1998 11:54:05 -0800 (PST) (envelope-from Studded@gorean.org) Message-ID: <363CBC5D.58BC293@gorean.org> Date: Sun, 01 Nov 1998 11:54:05 -0800 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 2.2.7-STABLE-1101 i386) X-Accept-Language: en MIME-Version: 1.0 To: Frank Mayhar CC: najib@csi-x.net, freebsd-stable@FreeBSD.ORG Subject: Re: Problem compiling -STABLE References: <199811011637.IAA03008@exit.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Frank Mayhar wrote: > You need to go into /usr/src/usr.sbin/config and do a 'make install'. Config > has changed recently, making it necessary to update it before trying to build > a kernel. > > I found out the hard way myself, but in general when something like this > happens, updating config first is usually a good thing to try. If that > fails, _then_ ask the list. It would be more correct to say that you should never update kernel sources without an accompanying make world. The fact that it sometimes works is purely accidental. Doug -- *** Chief Operations Officer, DALnet IRC network *** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 1 17:00:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA09475 for freebsd-stable-outgoing; Sun, 1 Nov 1998 17:00:47 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ice.cold.org (cold.org [206.81.134.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA09467 for ; Sun, 1 Nov 1998 17:00:41 -0800 (PST) (envelope-from root@ice.cold.org) Received: (from root@localhost) by ice.cold.org (8.8.8/8.8.5) id SAA15038; Sun, 1 Nov 1998 18:00:22 -0700 (MST) Date: Sun, 1 Nov 1998 18:00:22 -0700 (MST) Message-Id: <199811020100.SAA15038@ice.cold.org> Subject: ERRATA NOTICE: FreeBSD 3.0-RELEASE From: freebsd-errata-update@roguetrader.com To: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ****************************************************************** ** THIS IS AN AUTOMATIC ERRATA UPDATE FOR FREEBSD 3.0-RELEASE ** ****************************************************************** You can retrieve the complete ERRATA from: ftp://ftp.freebsd.org/pub/FreeBSD/3.0-RELEASE/ERRATA.TXT The last update was sent: Sun Oct 18 07:05:05 1998 This update is sent: Sun Nov 1 18:00:22 1998 ------------------------------------------------------------------ ---- SYSTEM ERRATA INFORMATION: o DOS partition installs fail to find the installation bits. Fix: Rename C:\FREEBSD to C:\3.0-RELEASE and retry the installation. The naming syntax was changed to make DOS more like the other types of installation media but the docs on DOS installation were not updated properly to reflect this. The current sysinstall now accepts both locations, as it should have to begin with. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 2 01:29:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA09587 for freebsd-stable-outgoing; Mon, 2 Nov 1998 01:29:35 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from internationalschool.co.uk (intschool.easynet.co.uk [194.72.37.214]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA09571 for ; Mon, 2 Nov 1998 01:29:31 -0800 (PST) (envelope-from stuart@internationalschool.co.uk) Received: from internationalschool.co.uk (bamboo [10.0.0.70]) by internationalschool.co.uk (8.8.8/8.8.8) with ESMTP id JAA00117; Mon, 2 Nov 1998 09:25:03 GMT Message-ID: <363D7A8D.7C2B09E5@internationalschool.co.uk> Date: Mon, 02 Nov 1998 09:25:33 +0000 From: Stuart Henderson Organization: http://ints.ml.org/ X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 2.2.7-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Frank Mayhar CC: najib@csi-x.net, freebsd-stable@FreeBSD.ORG Subject: Re: Problem compiling -STABLE References: <199811011637.IAA03008@exit.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Frank Mayhar wrote: > You need to go into /usr/src/usr.sbin/config and do a 'make install'. Config > has changed recently, making it necessary to update it before trying to build > a kernel. ...and ipfw as well, if you use it. and the snmpd port, if you use that. and probably some others... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 2 02:10:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA14290 for freebsd-stable-outgoing; Mon, 2 Nov 1998 02:10:05 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from infowest.com (ns1.infowest.com [204.17.177.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA14202; Mon, 2 Nov 1998 02:10:00 -0800 (PST) (envelope-from agifford@infowest.com) Received: from infowest.com (eq.net [207.49.60.250]) by infowest.com (8.8.8/8.8.8) with ESMTP id DAA13710; Mon, 2 Nov 1998 03:09:56 -0700 (MST) Message-ID: <363D84EE.A4E3FB51@infowest.com> Date: Mon, 02 Nov 1998 03:09:50 -0700 From: "Aaron D. Gifford" X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 2.2.7-STABLE i386) MIME-Version: 1.0 To: questions@FreeBSD.ORG, stable@FreeBSD.ORG Subject: IPFW question and fetch (Weird, just plain weird!) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FreeBSD 2.2.7-STABLE system (as of 31 Oct. 1998) running ipfw and I noticed something REALLY WEIRD: fetch http://some.site.blah/file.tar.gz ...It would fail with an error like: fetch: sendmsg: www.php.net: Permission denied Checked my ipfw rules. NOTHING should have prevented it from working. Normal web browsing (Netscrape) can access the exact same URL just fine. Here's basically what I've got (omitting a few spoof logging lines): ipfw add 100 permit ip from any to any via lo0 ipfw add 200 permit tcp from MY-IP-ADDR to any xmit tun0 setup ipfw add 300 permit tcp from any to MY-IP-ADDR recv tun0 established ipfw add 400 permit tcp from MY-IP-ADDR to any xmit tun0 established ipfw add 1000 deny log all from any to any Further analysis reveals the problem: fetch is sending a TCP packet with the FIN flag set but no ACK flag set, and thus is filtered out by my ipfw rule that only permits ESTABLISHED connections or NEW connections. So... What's up with fetch?????? Why is it doing this weirdness?? Is it doing some sort of connect test before it opens the real connection that requires the FIN packet??? I've never encountered this problem with ANY other software I've used on FreeBSD. I had to add a new line JUST so fetch would work: ipfw add 500 permit tcp from MY-IP-ADDR to any xmit tun0 tcpflags fin Yuck. I hate having to add special rules just for one piece of software. Puzzled, Aaron out. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 2 11:46:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA23900 for freebsd-stable-outgoing; Mon, 2 Nov 1998 11:46:27 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from assurance.rstcorp.com ([206.29.49.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA23893 for ; Mon, 2 Nov 1998 11:46:24 -0800 (PST) (envelope-from vshah@rstcorp.com) Received: (from uucp@localhost) by assurance.rstcorp.com (8.8.8/8.8.8) id OAA21002 for ; Mon, 2 Nov 1998 14:46:17 -0500 Received: from sandbox.rstcorp.com(206.29.49.63) by assurance.rstcorp.com via smap (V2.0) id xma020987; Mon, 2 Nov 98 14:45:34 -0500 Received: from jabberwock.rstcorp.com (jabberwock [206.29.49.98]) by sandbox.rstcorp.com (8.8.8/8.8.8) with ESMTP id OAA07686 for ; Mon, 2 Nov 1998 14:45:32 -0500 (EST) Received: (from vshah@localhost) by jabberwock.rstcorp.com (8.9.1/8.8.8) id OAA19170; Mon, 2 Nov 1998 14:45:33 -0500 (EST) Date: Mon, 2 Nov 1998 14:45:33 -0500 (EST) Message-Id: <199811021945.OAA19170@jabberwock.rstcorp.com> From: "Viren R. Shah" To: freebsd-stable@FreeBSD.ORG Subject: df hangs on 2.2.6-BETA X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: "Viren R. Shah" X-Face: )~y+U*K:yzjz{q<5lzpI_SVef'U.])9g[C9`1N@]u3,MHY7f*l7C)[_NjM4y4K8$uIUh|\u (K&&HS6,M!61&GMTk'mqmB/Qg]]X}"?TzsFl]"2v!bl8']dma.:^IY^a[lbOI>U:b<~FyK3q-p{HmZ mn~g.`~BE!5{2D:}Yi+\_KkWe?XaHj9$ko1k8iKLYv5*_2c8"G=?Up[}hn+7RNM(bzBZ_wWk6!Pf&B ?3Tcm7M7B~W%K/I0aX3]*=jP?aM]H6HBPT`oLk+0n^_;N\2\%|Rhy;p}34Q.jEsM\qtnxcm;ag%Nq Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is on an NFS server: [vshah@hal] ~> uname -a FreeBSD hal 2.2.6-BETA FreeBSD 2.2.6-BETA #0: Thu Mar 12 14:11:10 EST 1998 toor@hal:/var/src/sys/compile/HAL_TWO i386 Whenever I do a "df" on the system, the df process hangs, and can't be killed. Has anyone seen this before? The system still does everything else fine. So now I have: USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND vshah 21694 0.0 0.2 636 272 p0 R+ 2:42PM 0:00.00 ps -gu vshah 21201 0.0 0.0 188 52 p1- D 11:44AM 0:00.00 df vshah 21228 0.0 0.0 188 52 p0- D 11:46AM 0:00.00 df . vshah 21289 0.0 0.0 188 52 p0- D 11:51AM 0:00.00 df vshah 21392 0.0 0.0 188 52 p3- D 1:13PM 0:00.00 df vshah 21618 0.0 0.0 188 52 p0- D 2:11PM 0:00.00 df vshah 21670 0.0 0.7 1112 956 p0 Ss 2:38PM 0:00.33 -tcsh (tcsh) vshah 21191 0.0 0.0 188 52 p0- D 11:43AM 0:00.00 df Any ideas? The box has been up for a while: [vshah@hal] ~> uptime 2:43PM up 149 days, 3:55, 2 users, load averages: 0.20, 0.15, 0.12 And, unless it is absolutely necessary, we don't want to reboot it. Thanks Viren -- Viren R. Shah, viren @ rstcorp . com, http://www.rstcorp.com/~vshah/ If you understand what you're doing, you are not learning anything To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 2 12:29:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA29711 for freebsd-stable-outgoing; Mon, 2 Nov 1998 12:29:44 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA29704 for ; Mon, 2 Nov 1998 12:29:42 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA122948451; Mon, 2 Nov 1998 15:27:31 -0500 Date: Mon, 2 Nov 1998 15:27:31 -0500 (EST) From: Bill Fumerola To: "Viren R. Shah" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: df hangs on 2.2.6-BETA In-Reply-To: <199811021945.OAA19170@jabberwock.rstcorp.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 2 Nov 1998, Viren R. Shah wrote: > > This is on an NFS server: > > [vshah@hal] ~> uname -a > FreeBSD hal 2.2.6-BETA FreeBSD 2.2.6-BETA #0: Thu Mar 12 14:11:10 EST 1998 toor@hal:/var/src/sys/compile/HAL_TWO i386 Perhaps you'd like to CVSup and upgrade to 2.2.7-STABLE, it can't hurt. > Whenever I do a "df" on the system, the df process hangs, and can't > be killed. Has anyone seen this before? The system still does > everything else fine. I have seen the exact same thing using rumba/sharity-light (SMB/CIFS client), and get the same results. > So now I have: > > USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND > vshah 21694 0.0 0.2 636 272 p0 R+ 2:42PM 0:00.00 ps -gu > vshah 21201 0.0 0.0 188 52 p1- D 11:44AM 0:00.00 df > vshah 21228 0.0 0.0 188 52 p0- D 11:46AM 0:00.00 df . > vshah 21289 0.0 0.0 188 52 p0- D 11:51AM 0:00.00 df > vshah 21392 0.0 0.0 188 52 p3- D 1:13PM 0:00.00 df > vshah 21618 0.0 0.0 188 52 p0- D 2:11PM 0:00.00 df > vshah 21670 0.0 0.7 1112 956 p0 Ss 2:38PM 0:00.33 -tcsh (tcsh) > vshah 21191 0.0 0.0 188 52 p0- D 11:43AM 0:00.00 df Yes. no ``kill -9'' was good enough for my df / ls / anything NFS related zombies. > Any ideas? The box has been up for a while: > > [vshah@hal] ~> uptime > 2:43PM up 149 days, 3:55, 2 users, load averages: 0.20, 0.15, 0.12 I hate when people use uptime as a muscle flex or penis war. > And, unless it is absolutely necessary, we don't want to reboot it. People who do real work understand the validity of a reboot, uptime is nothing if the box doesn't work. Rebooting was the only thing I found to get rid of the processes (obviously, it would), though on shutdown, I got the "couldn't kill all processes, use ps -axl" message. - bill fumerola [root/billf]@chc-chimes.com - computer horizons corp - - ph:(800)252.2421 x128 / bfumerol@computerhorizons.com - BF1560 - "Logic, like whiskey, loses its beneficial effect when taken in too large quantities" -Lord Dunsany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 2 16:24:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA05486 for freebsd-stable-outgoing; Mon, 2 Nov 1998 16:24:18 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from freebie.dcfinc.com (freebie.dcfinc.com [138.113.5.128]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA05481 for ; Mon, 2 Nov 1998 16:24:16 -0800 (PST) (envelope-from chad@freebie.dcfinc.com) Received: (from chad@localhost) by freebie.dcfinc.com (8.8.7/8.8.3a) id RAA09520; Mon, 2 Nov 1998 17:23:56 -0700 (MST) From: "Chad R. Larson" Message-Id: <199811030023.RAA09520@freebie.dcfinc.com> Subject: Re: df hangs on 2.2.6-BETA To: billf@chc-chimes.com (Bill Fumerola) Date: Mon, 2 Nov 1998 17:23:55 -0700 (MST) Cc: viren@rstcorp.com, freebsd-stable@FreeBSD.ORG In-Reply-To: from Bill Fumerola at "Nov 2, 98 03:27:31 pm" Reply-to: chad@dcfinc.com X-unexpected: The Spanish Inquisition X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, 2 Nov 1998, Viren R. Shah wrote: > > Whenever I do a "df" on the system, the df process hangs, and can't > > be killed. Has anyone seen this before? The system still does > > everything else fine. > > I have seen the exact same thing using rumba/sharity-light (SMB/CIFS > client), and get the same results. This raises a missing feature I've long thought Unix needed. There should be a "kill with extreme prejudice". Something that will go through the kernel process tables and just remove all evidence the process ever existed. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org chad@anasazi.com larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 2 18:08:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19576 for freebsd-stable-outgoing; Mon, 2 Nov 1998 18:08:40 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ibm.net. (slip166-72-224-122.pa.us.ibm.net [166.72.224.122]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA19568 for ; Mon, 2 Nov 1998 18:08:37 -0800 (PST) (envelope-from placej@ibm.net) Received: (from placej@localhost) by ibm.net. (8.8.8/8.8.7) id VAA00232; Mon, 2 Nov 1998 21:08:18 -0500 (EST) (envelope-from placej) Message-ID: <19981102210818.01660@ka3tis.com> Date: Mon, 2 Nov 1998 21:08:18 -0500 From: "John C. Place" To: stable@FreeBSD.ORG Subject: Re: df hangs on 2.2.6-BETA Reply-To: "John C. Place" References: <199811030023.RAA09520@freebie.dcfinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199811030023.RAA09520@freebie.dcfinc.com>; from Chad R. Larson on Mon, Nov 02, 1998 at 05:23:55PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 02, 1998 at 05:23:55PM -0700, Chad R. Larson wrote: > This raises a missing feature I've long thought Unix needed. There > should be a "kill with extreme prejudice". Something that will go > through the kernel process tables and just remove all evidence the > process ever existed. > You mean kill -9 .... doesn't do the trick?? I always thought that was kill with extreme prejudice. Just my 2 cents John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 2 18:13:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20333 for freebsd-stable-outgoing; Mon, 2 Nov 1998 18:13:12 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA20311 for ; Mon, 2 Nov 1998 18:13:06 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0zaVxm-0002kI-00; Mon, 2 Nov 1998 18:12:54 -0800 Date: Mon, 2 Nov 1998 18:12:51 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: "John C. Place" cc: stable@FreeBSD.ORG Subject: Re: df hangs on 2.2.6-BETA In-Reply-To: <19981102210818.01660@ka3tis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 2 Nov 1998, John C. Place wrote: > On Mon, Nov 02, 1998 at 05:23:55PM -0700, Chad R. Larson wrote: > > This raises a missing feature I've long thought Unix needed. There > > should be a "kill with extreme prejudice". Something that will go > > through the kernel process tables and just remove all evidence the > > process ever existed. > > > You mean kill -9 .... doesn't do the trick?? I always thought that was kill > with extreme prejudice. That is what kill -9 does, except it doesn't work for processes stuck waiting for NFS. This is by design. See what the "intr" flag is for. > Just my 2 cents > > John Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 2 19:08:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA27207 for freebsd-stable-outgoing; Mon, 2 Nov 1998 19:08:14 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from parsons.rh.rit.edu (d111-l052.rh.rit.edu [129.21.111.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA27201 for ; Mon, 2 Nov 1998 19:08:11 -0800 (PST) (envelope-from mfisher@csh.rit.edu) Received: from mfisher (helo=localhost) by parsons.rh.rit.edu with local-esmtp (Exim 2.05 #1) id 0zaWos-0004li-00; Mon, 2 Nov 1998 22:07:46 -0500 Date: Mon, 2 Nov 1998 22:07:45 -0500 (EST) From: Mike Fisher X-Sender: mfisher@d111-l052.rh.rit.edu To: "John C. Place" cc: stable@FreeBSD.ORG Subject: Re: df hangs on 2.2.6-BETA In-Reply-To: <19981102210818.01660@ka3tis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 2 Nov 1998, John C. Place wrote: > On Mon, Nov 02, 1998 at 05:23:55PM -0700, Chad R. Larson wrote: > > This raises a missing feature I've long thought Unix needed. There > > should be a "kill with extreme prejudice". Something that will go > > through the kernel process tables and just remove all evidence the > > process ever existed. > > > You mean kill -9 .... doesn't do the trick?? I always thought that was kill > with extreme prejudice. I've seen df's or whatever hang when the NFS mount was down. In these cases, a ps listed that the state had the D flag... state The state is given by a sequence of letters, for example, ``RWNA''. The first letter indicates the run state of the pro- cess: D Marks a process in disk (or other short term, uninter- ruptible) wait. So, it couldn't be killed. -- Mike "...check your premises. You will find that one of them is wrong." --Ayn Rand, _Atlas Shrugged_ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 2 22:37:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA24341 for freebsd-stable-outgoing; Mon, 2 Nov 1998 22:37:01 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.double-barrel.be (mail.double-barrel.be [194.7.102.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA24318 for ; Mon, 2 Nov 1998 22:36:57 -0800 (PST) (envelope-from mvergall@mail.double-barrel.be) Received: (from uucp@localhost) by mail.double-barrel.be (8.9.1/8.8.8) id HAA02229; Tue, 3 Nov 1998 07:35:39 +0100 (CET) (envelope-from mvergall@mail.double-barrel.be) Received: from ns.double-barrel.be(194.7.102.18) via SMTP by mail.double-barrel.be, id smtpdxc2227; Tue Nov 3 07:35:39 1998 Date: Tue, 3 Nov 1998 07:35:31 +0100 (CET) From: "Michael C. Vergallen" X-Sender: mvergall@ns.double-barrel.be To: "Viren R. Shah" cc: freebsd-stable@FreeBSD.ORG Subject: Re: df hangs on 2.2.6-BETA In-Reply-To: <199811021945.OAA19170@jabberwock.rstcorp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Are you shure it can not be killed even by root usig kill -9 ? I've never seen any app who can not be killed by that process. Michael --- Michael C. Vergallen A.k.A. Mad Mike, Sportstraat 28 http://www.double-barrel.be/mvergall/ B 9000 Gent ftp://ftp.double-barrel.be/pub/linux/ Belgium tel : 32-9-2227764 Fax : 32-9-2224976 On Mon, 2 Nov 1998, Viren R. Shah wrote: > > This is on an NFS server: > > [vshah@hal] ~> uname -a > FreeBSD hal 2.2.6-BETA FreeBSD 2.2.6-BETA #0: Thu Mar 12 14:11:10 EST 1998 toor@hal:/var/src/sys/compile/HAL_TWO i386 > > Whenever I do a "df" on the system, the df process hangs, and can't > be killed. Has anyone seen this before? The system still does > everything else fine. > So now I have: > > USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND > vshah 21694 0.0 0.2 636 272 p0 R+ 2:42PM 0:00.00 ps -gu > vshah 21201 0.0 0.0 188 52 p1- D 11:44AM 0:00.00 df > vshah 21228 0.0 0.0 188 52 p0- D 11:46AM 0:00.00 df . > vshah 21289 0.0 0.0 188 52 p0- D 11:51AM 0:00.00 df > vshah 21392 0.0 0.0 188 52 p3- D 1:13PM 0:00.00 df > vshah 21618 0.0 0.0 188 52 p0- D 2:11PM 0:00.00 df > vshah 21670 0.0 0.7 1112 956 p0 Ss 2:38PM 0:00.33 -tcsh (tcsh) > vshah 21191 0.0 0.0 188 52 p0- D 11:43AM 0:00.00 df > > > Any ideas? The box has been up for a while: > > [vshah@hal] ~> uptime > 2:43PM up 149 days, 3:55, 2 users, load averages: 0.20, 0.15, 0.12 > > And, unless it is absolutely necessary, we don't want to reboot it. > > Thanks > Viren > -- > Viren R. Shah, viren @ rstcorp . com, http://www.rstcorp.com/~vshah/ > If you understand what you're doing, you are not learning anything > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 2 23:21:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA29417 for freebsd-stable-outgoing; Mon, 2 Nov 1998 23:21:51 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA29412 for ; Mon, 2 Nov 1998 23:21:50 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0zaamQ-00030Q-00; Mon, 2 Nov 1998 23:21:30 -0800 Date: Mon, 2 Nov 1998 23:21:25 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: "Michael C. Vergallen" cc: "Viren R. Shah" , freebsd-stable@FreeBSD.ORG Subject: Re: df hangs on 2.2.6-BETA In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 3 Nov 1998, Michael C. Vergallen wrote: > Are you shure it can not be killed even by root usig kill -9 ? > I've never seen any app who can not be killed by that process. Very. Processes waiting for disk (or nfs) io can't be killed. However, you can specify "-i" to mount_nfs to make processes waiting for NFS killable. > Michael > --- > Michael C. Vergallen A.k.A. Mad Mike, > Sportstraat 28 http://www.double-barrel.be/mvergall/ > B 9000 Gent ftp://ftp.double-barrel.be/pub/linux/ > Belgium tel : 32-9-2227764 Fax : 32-9-2224976 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 3 00:47:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA09083 for freebsd-stable-outgoing; Tue, 3 Nov 1998 00:47:23 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.double-barrel.be (mail.double-barrel.be [194.7.102.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA09076 for ; Tue, 3 Nov 1998 00:47:20 -0800 (PST) (envelope-from mvergall@mail.double-barrel.be) Received: (from uucp@localhost) by mail.double-barrel.be (8.9.1/8.8.8) id JAA02662; Tue, 3 Nov 1998 09:45:57 +0100 (CET) (envelope-from mvergall@mail.double-barrel.be) Received: from ns.double-barrel.be(194.7.102.18) via SMTP by mail.double-barrel.be, id smtpdeQ2660; Tue Nov 3 09:45:52 1998 Date: Tue, 3 Nov 1998 09:45:43 +0100 (CET) From: "Michael C. Vergallen" X-Sender: mvergall@ns.double-barrel.be To: Tom cc: "Viren R. Shah" , freebsd-stable@FreeBSD.ORG Subject: Re: df hangs on 2.2.6-BETA In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes I see, However isn't this due to the fact that one off the systems that had disc's mounted was reset improperly while the discs where mounted thus causing the nfs_mounted filesystems to cause zombie processes. Witch I don't see as an error but a logical result warning the other systems that the filesystem could be now located on a different physical disc. This can happen when using the raid adapter and a hot swap had to happen because of a physical disc defect. Michael --- Michael C. Vergallen A.k.A. Mad Mike, Sportstraat 28 http://www.double-barrel.be/mvergall/ B 9000 Gent ftp://ftp.double-barrel.be/pub/linux/ Belgium tel : 32-9-2227764 Fax : 32-9-2224976 On Mon, 2 Nov 1998, Tom wrote: > Very. Processes waiting for disk (or nfs) io can't be killed. > However, you can specify "-i" to mount_nfs to make processes waiting for > NFS killable. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 3 01:53:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA16990 for freebsd-stable-outgoing; Tue, 3 Nov 1998 01:53:57 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from internationalschool.co.uk (intschool.easynet.co.uk [194.72.37.214]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA16972 for ; Tue, 3 Nov 1998 01:53:52 -0800 (PST) (envelope-from stuart@internationalschool.co.uk) Received: from internationalschool.co.uk (bamboo [10.0.0.70]) by internationalschool.co.uk (8.8.8/8.8.8) with ESMTP id JAA19302; Tue, 3 Nov 1998 09:52:40 GMT Message-ID: <363ED28C.E9D2B101@internationalschool.co.uk> Date: Tue, 03 Nov 1998 09:53:17 +0000 From: Stuart Henderson Organization: http://ints.ml.org/ X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 2.2.7-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: "Viren R. Shah" CC: freebsd-stable@FreeBSD.ORG Subject: Re: df hangs on 2.2.6-BETA References: <199811021945.OAA19170@jabberwock.rstcorp.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Viren R. Shah" wrote: > > Whenever I do a "df" on the system, the df process hangs, and can't > be killed. Has anyone seen this before? The system still does > everything else fine. Sounds like it may be an NFS mount that isn't there any more. Any process trying to access it will block and can't be killed (I think you can set a mount option in /etc/fstab or the command line to make it so if things get in this state you can kill them - see manpages - I think it's the 'intr' flag)[1]. These can be rather tricky to get rid of without rebooting...(sometimes if you recreate the NFS mount on the machine it's mounted from you can get there). If you have been using rumba and didn't use the unrumba command to unmount, learn to do so. > Any ideas? The box has been up for a while: > And, unless it is absolutely necessary, we don't want to reboot it. As you are running a beta version anyway that's pretty good uptime as it stands. Go ahead, reboot it. At least you can *schedule* it :-) It's uncontrolled reboots that are the problem. Stuart [1] the way it works *is* good behaviour in the usual case where a NFS server is rebooted, because clients accessing it will just wait for it to come back online and continue where they left off. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 3 06:46:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA16695 for freebsd-stable-outgoing; Tue, 3 Nov 1998 06:46:18 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from destiny.erols.com (destiny.erols.com [207.96.73.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA16686 for ; Tue, 3 Nov 1998 06:46:15 -0800 (PST) (envelope-from jdowdal@destiny.erols.com) Received: from destiny.erols.com (someone@destiny.erols.com [207.96.73.65]) by destiny.erols.com (8.8.8/8.6.12) with SMTP id JAA17389; Tue, 3 Nov 1998 09:45:44 -0500 (EST) Date: Tue, 3 Nov 1998 09:45:44 -0500 (EST) From: John Dowdal To: "John C. Place" cc: stable@FreeBSD.ORG Subject: Re: df hangs on 2.2.6-BETA In-Reply-To: <19981102210818.01660@ka3tis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 2 Nov 1998, John C. Place wrote: > On Mon, Nov 02, 1998 at 05:23:55PM -0700, Chad R. Larson wrote: > > This raises a missing feature I've long thought Unix needed. There > > should be a "kill with extreme prejudice". Something that will go > > through the kernel process tables and just remove all evidence the > > process ever existed. > > > You mean kill -9 .... doesn't do the trick?? I always thought that was kill > with extreme prejudice. > I have noticed on several unixes (all based on BSD) such as SunOS 4, Ultrix, and Digital Unix, that processes in 'D' (disk wait) state in 'top' will not die with kill -9. This frequently occurs when a hard-mounted NFS filesystem goes down. The processes will remember that they were killed and die if the filesystem ever comes back up; otherwise they will waste resources (swap and process table but not CPU). Assuming the process cannot be unblocked, i have found the only way to get rid of them is to reboot. On SunOS, shutdown would frequently complain that there were processes which would not die. A few times it did NOT give me this message, which implies that they could be killed in these rare cases by shutting down to single-user then going back to multi-user. This will allow you to preserve your long uptime John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 3 06:49:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA17174 for freebsd-stable-outgoing; Tue, 3 Nov 1998 06:49:58 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA17169 for ; Tue, 3 Nov 1998 06:49:56 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA205754506; Tue, 3 Nov 1998 09:48:26 -0500 Date: Tue, 3 Nov 1998 09:48:26 -0500 (EST) From: Bill Fumerola To: chad@dcfinc.com Cc: freebsd-stable@FreeBSD.ORG Subject: Re: df hangs on 2.2.6-BETA In-Reply-To: <199811030023.RAA09520@freebie.dcfinc.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 2 Nov 1998, Chad R. Larson wrote: > This raises a missing feature I've long thought Unix needed. There > should be a "kill with extreme prejudice". Something that will go > through the kernel process tables and just remove all evidence the > process ever existed. ``killall -SIGANGRY sh-light'', huh? :> .. That would be funny. "kill with extreme prejudice".. heh. - bill fumerola [root/billf]@chc-chimes.com - computer horizons corp - - ph:(800)252.2421 x128 / bfumerol@computerhorizons.com - BF1560 - "Logic, like whiskey, loses its beneficial effect when taken in too large quantities" -Lord Dunsany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 3 06:52:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA17439 for freebsd-stable-outgoing; Tue, 3 Nov 1998 06:52:19 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA17434 for ; Tue, 3 Nov 1998 06:52:17 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA205854653; Tue, 3 Nov 1998 09:50:53 -0500 Date: Tue, 3 Nov 1998 09:50:53 -0500 (EST) From: Bill Fumerola To: "John C. Place" Cc: stable@FreeBSD.ORG Subject: Re: df hangs on 2.2.6-BETA In-Reply-To: <19981102210818.01660@ka3tis.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 2 Nov 1998, John C. Place wrote: > You mean kill -9 .... doesn't do the trick?? I always thought that was kill > with extreme prejudice. ``kill -9 PID'' will not take care of a zombied process. such as NFS/Sharity-Light server stuff, the discussion this thread was based on. - bill fumerola [root/billf]@chc-chimes.com - computer horizons corp - - ph:(800)252.2421 x128 / bfumerol@computerhorizons.com - BF1560 - "Logic, like whiskey, loses its beneficial effect when taken in too large quantities" -Lord Dunsany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 3 07:31:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA22268 for freebsd-stable-outgoing; Tue, 3 Nov 1998 07:31:54 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from www.scancall.no (www.scancall.no [195.139.183.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA22263 for ; Tue, 3 Nov 1998 07:31:50 -0800 (PST) (envelope-from Marius.Bendiksen@scancall.no) Received: from super2.langesund.scancall.no [195.139.183.29] by www with smtp id JRADCPLJ; Tue, 03 Nov 98 15:31:43 GMT (PowerWeb version 4.04r6) Message-Id: <3.0.5.32.19981103163141.009c1860@mail.scancall.no> X-Sender: Marius@mail.scancall.no X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Tue, 03 Nov 1998 16:31:41 +0100 To: Bill Fumerola , "John C. Place" From: Marius Bendiksen Subject: Re: df hangs on 2.2.6-BETA Cc: stable@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: References: <19981102210818.01660@ka3tis.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there any way of doing a true unconditional forcible kill? If not, what would be needed to implement it? (follow-ups to -hackers) --- Marius Bendiksen, IT-Trainee, ScanCall AS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 3 11:04:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA21974 for freebsd-stable-outgoing; Tue, 3 Nov 1998 11:04:40 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from megaweapon.zigg.com (megaweapon.zigg.com [206.114.60.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA21967 for ; Tue, 3 Nov 1998 11:04:35 -0800 (PST) (envelope-from matt@zigg.com) Received: from localhost (matt@localhost) by megaweapon.zigg.com (8.8.8/8.8.8) with SMTP id OAA05695 for ; Tue, 3 Nov 1998 14:04:38 -0500 (EST) (envelope-from matt@zigg.com) Date: Tue, 3 Nov 1998 14:04:38 -0500 (EST) From: Matt Behrens To: freebsd-stable@FreeBSD.ORG Subject: Re: df hangs on 2.2.6-BETA In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -SIGBEGONE ? :) On Tue, 3 Nov 1998, Bill Fumerola wrote: > On Mon, 2 Nov 1998, Chad R. Larson wrote: > > This raises a missing feature I've long thought Unix needed. There > > should be a "kill with extreme prejudice". Something that will go > > through the kernel process tables and just remove all evidence the > > process ever existed. > ``killall -SIGANGRY sh-light'', huh? :> .. That would be funny. "kill with > extreme prejudice".. heh. Matt Behrens | If only I could learn Japanese and get my Servant of Karen Behrens | hands on all 200 Sailor Moon episodes and Engineer, Nameless IRC Network | all the movies, I think my life would I eat Penguins for breakfast. | finally be complete. . . . . . . . . . . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 3 13:04:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09738 for freebsd-stable-outgoing; Tue, 3 Nov 1998 13:04:08 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ohio.river.org (river.org [209.24.233.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA09732 for ; Tue, 3 Nov 1998 13:04:07 -0800 (PST) (envelope-from dhawk@ohio.river.org) Received: (from dhawk@localhost) by ohio.river.org (8.8.8/8.7.3) id NAA08836 for freebsd-stable@FreeBSD.ORG; Tue, 3 Nov 1998 13:04:01 -0800 (PST) From: David Hawkins Message-Id: <199811032104.NAA08836@ohio.river.org> Subject: Re: df hangs on 2.2.6-BETA In-Reply-To: from Matt Behrens at "Nov 3, 1998 2: 4:38 pm" To: freebsd-stable@FreeBSD.ORG Date: Tue, 3 Nov 1998 13:04:01 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This raises a missing feature I've long thought Unix needed. There > should be a "kill with extreme prejudice". Something that will go > through the kernel process tables and just remove all evidence the > process ever existed. In SunOS 4.1.x I could use gcore PROCESS_ID and get that effect. Don't know if it was intended, but gcore would wipe out processes that kill couldn't touch. later, david -- David Hawkins -- dhawk@river.org http://www.river.org/~dhawk "Why.... that would be pretty cool, if they weren't trying to kill me." -- Calvin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 3 14:00:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA18625 for freebsd-stable-outgoing; Tue, 3 Nov 1998 14:00:22 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from freebie.dcfinc.com (freebie.dcfinc.com [138.113.5.128]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA18610 for ; Tue, 3 Nov 1998 14:00:15 -0800 (PST) (envelope-from chad@freebie.dcfinc.com) Received: (from chad@localhost) by freebie.dcfinc.com (8.8.7/8.8.3a) id PAA11029; Tue, 3 Nov 1998 15:00:07 -0700 (MST) From: "Chad R. Larson" Message-Id: <199811032200.PAA11029@freebie.dcfinc.com> Subject: Re: df hangs on 2.2.6-BETA To: jcplace@ibm.net Date: Tue, 3 Nov 1998 15:00:06 -0700 (MST) Cc: stable@FreeBSD.ORG In-Reply-To: <19981102210818.01660@ka3tis.com> from "John C. Place" at "Nov 2, 98 09:08:18 pm" Reply-to: chad@dcfinc.com X-unexpected: The Spanish Inquisition X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > This raises a missing feature I've long thought Unix needed. There > > should be a "kill with extreme prejudice". Something that will go > > through the kernel process tables and just remove all evidence the > > process ever existed. > > > You mean kill -9 .... doesn't do the trick?? I always thought that was kill > with extreme prejudice. Nope. It won't kill any process that is in kernel state (in a device driver) that has raised it's software interrupt processing level above that of signal processing. That is, processes sometimes call a driver to do device I/O, and the driver blocks waiting on some event that doesn't happen. And it blocks in a way that a signal doesn't cause it to awaken. The kill signal (-9) is happily queued, and the process will receive it as soon as it awakens (never). Basically bad form on the part of the driver writer, but not at all rare. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org chad@anasazi.com larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 3 17:09:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA19465 for freebsd-stable-outgoing; Tue, 3 Nov 1998 17:09:01 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from netmug.org (netmug.org [207.88.43.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA19457 for ; Tue, 3 Nov 1998 17:08:59 -0800 (PST) (envelope-from perl@netmug.org) Received: from localhost (perl@localhost) by netmug.org (8.8.8/NetMUG_1.0.0) with SMTP id RAA03502 for ; Tue, 3 Nov 1998 17:08:10 -0800 (PST) Date: Tue, 3 Nov 1998 17:08:10 -0800 (PST) From: perl To: stable@FreeBSD.ORG Subject: has this been fixed? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I was wondering if someone has changed the timeout in the wd driver so that Nov 3 17:06:17 netmug /kernel: wd2: interrupt timeout: Nov 3 17:06:17 netmug /kernel: wd2: status 50 error 1 is less common. Or is there a way to keep that from happening? What causes that error? An IDE timeout, right? Thanks, Michael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 3 17:24:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA21680 for freebsd-stable-outgoing; Tue, 3 Nov 1998 17:24:57 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA21675 for ; Tue, 3 Nov 1998 17:24:53 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0zargb-0000nf-00; Tue, 3 Nov 1998 17:24:37 -0800 Date: Tue, 3 Nov 1998 17:24:34 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: perl cc: stable@FreeBSD.ORG Subject: Re: has this been fixed? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 3 Nov 1998, perl wrote: > Hi, I was wondering if someone has changed the timeout in the wd driver so > that > Nov 3 17:06:17 netmug /kernel: wd2: interrupt timeout: > Nov 3 17:06:17 netmug /kernel: wd2: status 50 error 1 > is less common. It is hardware problem. Fix the hardware so it responds faster, and the warning message will disapear. > Or is there a way to keep that from happening? What causes that error? > An IDE timeout, right? You can lengthen the timeout, but this would just hide the problem. Your drive is taking a bit too long to respond. > Thanks, > > Michael Tom Systems Support Uniserve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 3 18:00:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA25773 for freebsd-stable-outgoing; Tue, 3 Nov 1998 18:00:19 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from netmug.org (netmug.org [207.88.43.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA25768 for ; Tue, 3 Nov 1998 18:00:18 -0800 (PST) (envelope-from perl@netmug.org) Received: from localhost (perl@localhost) by netmug.org (8.8.8/NetMUG_1.0.0) with SMTP id RAA05170; Tue, 3 Nov 1998 17:59:20 -0800 (PST) Date: Tue, 3 Nov 1998 17:59:20 -0800 (PST) From: perl To: Tom cc: stable@FreeBSD.ORG Subject: Re: has this been fixed? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG how would I go about fixing my hardware? is this caused by the drive spining down? (i'm not sure if it is or not) Thanks, Michael On Tue, 3 Nov 1998, Tom wrote: > > On Tue, 3 Nov 1998, perl wrote: > > > Hi, I was wondering if someone has changed the timeout in the wd driver so > > that > > Nov 3 17:06:17 netmug /kernel: wd2: interrupt timeout: > > Nov 3 17:06:17 netmug /kernel: wd2: status 50 error 1 > > is less common. > > It is hardware problem. Fix the hardware so it > responds faster, and the warning message will disapear. > > > Or is there a way to keep that from happening? What causes that error? > > An IDE timeout, right? > > You can lengthen the timeout, but this would just hide the problem. > Your drive is taking a bit too long to respond. > > > Thanks, > > > > Michael > > > > > Tom > Systems Support > Uniserve > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 3 18:11:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA26954 for freebsd-stable-outgoing; Tue, 3 Nov 1998 18:11:24 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA26948 for ; Tue, 3 Nov 1998 18:11:23 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA01400; Tue, 3 Nov 1998 18:10:19 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811040210.SAA01400@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: perl cc: Tom , stable@FreeBSD.ORG Subject: Re: has this been fixed? In-reply-to: Your message of "Tue, 03 Nov 1998 17:59:20 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 03 Nov 1998 18:10:19 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG See the archives for the last ten or so times this question has been answered. > how would I go about fixing my hardware? > is this caused by the drive spining down? (i'm not sure if it is or not) > > Thanks, > > Michael > > > On Tue, 3 Nov 1998, Tom wrote: > > > > > On Tue, 3 Nov 1998, perl wrote: > > > > > Hi, I was wondering if someone has changed the timeout in the wd driver so > > > that > > > Nov 3 17:06:17 netmug /kernel: wd2: interrupt timeout: > > > Nov 3 17:06:17 netmug /kernel: wd2: status 50 error 1 > > > is less common. > > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 3 18:35:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA00339 for freebsd-stable-outgoing; Tue, 3 Nov 1998 18:35:34 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from public.bta.net.cn (public.bta.net.cn [202.96.0.97]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA00334 for ; Tue, 3 Nov 1998 18:35:31 -0800 (PST) (envelope-from robinson@public.bta.net.cn) Received: (from robinson@localhost) by public.bta.net.cn (8.9.1/8.9.1) id KAA24822; Wed, 4 Nov 1998 10:34:52 +0800 (GMT) Date: Wed, 4 Nov 1998 10:34:52 +0800 (GMT) From: Michael Robinson Message-Id: <199811040234.KAA24822@public.bta.net.cn> To: perl@netmug.org, tom@uniserve.com Subject: Re: has this been fixed? Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tom writes: > It is hardware problem. Fix the hardware so it >responds faster, and the warning message will disapear. > >> Or is there a way to keep that from happening? What causes that error? >> An IDE timeout, right? > > You can lengthen the timeout, but this would just hide the problem. >Your drive is taking a bit too long to respond. Just out of curiousity, how did the threshold for "a bit too long" get determined? Is this defined in the IDE standard? Did someone conduct a comprehensive survey of popular drives under various error-recovery modes? Did the driver writer just pull a number out of the air? -Michael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 3 18:41:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA00715 for freebsd-stable-outgoing; Tue, 3 Nov 1998 18:41:04 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA00710 for ; Tue, 3 Nov 1998 18:41:03 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA01502; Tue, 3 Nov 1998 18:39:07 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811040239.SAA01502@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Michael Robinson cc: perl@netmug.org, tom@uniserve.com, stable@FreeBSD.ORG Subject: Re: has this been fixed? In-reply-to: Your message of "Wed, 04 Nov 1998 10:34:52 +0800." <199811040234.KAA24822@public.bta.net.cn> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 03 Nov 1998 18:39:07 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Tom writes: > > It is hardware problem. Fix the hardware so it > >responds faster, and the warning message will disapear. > > > >> Or is there a way to keep that from happening? What causes that error? > >> An IDE timeout, right? > > > > You can lengthen the timeout, but this would just hide the problem. > >Your drive is taking a bit too long to respond. > > Just out of curiousity, how did the threshold for "a bit too long" get > determined? Is this defined in the IDE standard? Did someone conduct > a comprehensive survey of popular drives under various error-recovery modes? > Did the driver writer just pull a number out of the air? It's just a random number that was hoped to be "long enough". Some drives seem to take weeks to decide that a block is bad, some are really quick about it. The current value is 10 seconds; there have been various discussions about raising it, and it'll probably get bumped, but increasing the timeout doesn't actually help the problem (which is almost always a read operation on a bad block that the drive is unable to recover). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Nov 3 19:30:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA05654 for freebsd-stable-outgoing; Tue, 3 Nov 1998 19:30:21 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gaylord.async.vt.edu (gaylord.async.vt.edu [128.173.18.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA05649 for ; Tue, 3 Nov 1998 19:30:19 -0800 (PST) (envelope-from gaylord@gaylord.async.vt.edu) Received: (from gaylord@localhost) by gaylord.async.vt.edu (8.8.8/8.8.5) id WAA02779; Tue, 3 Nov 1998 22:29:29 -0500 (EST) From: Clark Gaylord Message-Id: <199811040329.WAA02779@gaylord.async.vt.edu> Subject: Re: has this been fixed? In-Reply-To: <199811040234.KAA24822@public.bta.net.cn> from Michael Robinson at "Nov 4, 98 10:34:52 am" To: robinson@public.bta.net.cn (Michael Robinson) Date: Tue, 3 Nov 1998 22:29:28 -0500 (EST) Cc: perl@netmug.org, tom@uniserve.com, stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Tom writes: > > It is hardware problem. Fix the hardware so it > >responds faster, and the warning message will disapear. > > > >> Or is there a way to keep that from happening? What causes that error? > >> An IDE timeout, right? > > > > You can lengthen the timeout, but this would just hide the problem. > >Your drive is taking a bit too long to respond. > > Just out of curiousity, how did the threshold for "a bit too long" get > determined? Is this defined in the IDE standard? Did someone conduct IDE standard? You are funny. Let me guess, that's published on www.snakeoil.com, right? Clark -- Clark K. Gaylord Blacksburg, Virginia USA cgaylord@vt.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Nov 4 06:01:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA26643 for freebsd-stable-outgoing; Wed, 4 Nov 1998 06:01:55 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from Gambit.Msk.SU (gambit.msk.su [194.190.206.62]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA26619 for ; Wed, 4 Nov 1998 06:01:49 -0800 (PST) (envelope-from laskavy@Gambit.Msk.SU) Received: (from laskavy@localhost) by Gambit.Msk.SU (8.0/8.9.1) id RAA28737; Wed, 4 Nov 1998 17:01:23 +0300 (MSK) To: perl Cc: Tom , stable@FreeBSD.ORG Subject: Re: has this been fixed? References: From: Sergei Laskavy Date: 04 Nov 1998 17:01:22 +0300 In-Reply-To: perl's message of Tue, 3 Nov 1998 17:59:20 -0800 (PST) Message-ID: Lines: 10 X-Mailer: Gnus v5.5/Emacs 20.2 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG perl writes: > how would I go about fixing my hardware? is this caused by the > drive spining down? (i'm not sure if it is or not) Maybe, you use apm? -- FreeBSD Project: http://FreeBSD.org/docproj/ Vim: http://www.vim.org/ $_='$6C86:P$^P|2D<2GJPl=2D<2GJp82>3:E^>D<^DFn';tr#P-~\x20-O#\x20-~#;print To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Nov 4 10:01:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03310 for freebsd-stable-outgoing; Wed, 4 Nov 1998 10:01:12 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA03300 for ; Wed, 4 Nov 1998 10:01:07 -0800 (PST) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.8.8/8.8.7) id JAA18450; Wed, 4 Nov 1998 09:59:25 -0800 (PST) (envelope-from dhw) Date: Wed, 4 Nov 1998 09:59:25 -0800 (PST) From: David Wolfskill Message-Id: <199811041759.JAA18450@pau-amma.whistle.com> To: freebsd-stable@FreeBSD.ORG, gaylord@gaylord.async.vt.edu Subject: Re: has this been fixed? In-Reply-To: <199811040329.WAA02779@gaylord.async.vt.edu> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From: Clark Gaylord >Date: Tue, 3 Nov 1998 22:29:28 -0500 (EST) >> Just out of curiousity, how did the threshold for "a bit too long" get >> determined? Is this defined in the IDE standard? Did someone conduct >IDE standard? You are funny. Let me guess, that's published on >www.snakeoil.com, right? Ummm.... I didn't ask the original question, but it's not at all clear to me why it should be "funny." Given that someone evidently thinks it is, I gether from context that the phrase "IDE standard" is a reference to a nonentity? Is there an expectation that anyone who might ever want to use a FreeBSD system should know this? And what would the Chicago Tribune have to do with it? david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Nov 4 10:08:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA04224 for freebsd-stable-outgoing; Wed, 4 Nov 1998 10:08:06 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA04219 for ; Wed, 4 Nov 1998 10:08:05 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id KAA00878; Wed, 4 Nov 1998 10:07:31 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811041807.KAA00878@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: David Wolfskill cc: freebsd-stable@FreeBSD.ORG, gaylord@gaylord.async.vt.edu Subject: Re: has this been fixed? In-reply-to: Your message of "Wed, 04 Nov 1998 09:59:25 PST." <199811041759.JAA18450@pau-amma.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 04 Nov 1998 10:07:30 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >From: Clark Gaylord > >Date: Tue, 3 Nov 1998 22:29:28 -0500 (EST) > > >> Just out of curiousity, how did the threshold for "a bit too long" get > >> determined? Is this defined in the IDE standard? Did someone conduct > > >IDE standard? You are funny. Let me guess, that's published on > >www.snakeoil.com, right? > > Ummm.... I didn't ask the original question, but it's not at all clear > to me why it should be "funny." > > Given that someone evidently thinks it is, I gether from context that > the phrase "IDE standard" is a reference to a nonentity? Is there an > expectation that anyone who might ever want to use a FreeBSD system > should know this? There is, indeed, no "IDE standard". There are, instead, a set of ATA standards, (1 through 4) which attempt to define the ATA interface. Unfortunately, these aren't the best of standards, and it seems that vendors take perverse delight in ignoring parts of them that don't suit their agendas. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Nov 4 10:39:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA08293 for freebsd-stable-outgoing; Wed, 4 Nov 1998 10:39:33 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from laker.net (jet.laker.net [205.245.74.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA08285 for ; Wed, 4 Nov 1998 10:39:29 -0800 (PST) (envelope-from sfriedri@laker.net) Received: from nt (digital-pbi-141.laker.net [208.0.233.41]) by laker.net (8.9.0/8.9.LAKERNET.NO-SPAM.SPAMMERS.AND.RELAYS.WILL.BE.TRACKED.AND.PROSECUTED.) with SMTP id NAA20945; Wed, 4 Nov 1998 13:39:14 -0500 Message-Id: <199811041839.NAA20945@laker.net> From: "Steve Friedrich" To: "David Wolfskill" , "freebsd-stable@FreeBSD.ORG" , "gaylord@gaylord.async.vt.edu" Date: Wed, 04 Nov 1998 13:37:46 -0500 Reply-To: "Steve Friedrich" X-Mailer: PMMail 98 Professional (2.01.1600) For Windows NT (4.0.1381;3) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: has this been fixed? Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 4 Nov 1998 09:59:25 -0800 (PST), David Wolfskill wrote: >>From: Clark Gaylord >>Date: Tue, 3 Nov 1998 22:29:28 -0500 (EST) > >>> Just out of curiousity, how did the threshold for "a bit too long" get >>> determined? Is this defined in the IDE standard? Did someone conduct > >>IDE standard? You are funny. Let me guess, that's published on >>www.snakeoil.com, right? > >Ummm.... I didn't ask the original question, but it's not at all clear >to me why it should be "funny." > >Given that someone evidently thinks it is, I gether from context that >the phrase "IDE standard" is a reference to a nonentity? Is there an >expectation that anyone who might ever want to use a FreeBSD system >should know this? IMHO, anyone who uses PC hardware had better be aware that an IDE standard does not exist!! Manufacturers have been making it up as they go along. SCSI isn't really that much better. SCSI 1 devices from different manufacturers frequently couldn't *talk*, due to ambiguities in the spec. SCSI 2 is better, but many manufacturers were selling SCSI 2 devices before the spec was ratified (I think everyone stopped producing SCSI 1 devices just before SCSI 1 spec got ratified), and SCSI 3 (well, let's not go there). >And what would the Chicago Tribune have to do with it? Does the Tribune own the www.snakeoil.com domain?? Unix systems measure "uptime" in years, Winblows measures it in minutes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Nov 4 10:53:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA10645 for freebsd-stable-outgoing; Wed, 4 Nov 1998 10:53:03 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from junior.lgc.com (junior.lgc.com [134.132.72.99]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA10612 for ; Wed, 4 Nov 1998 10:52:58 -0800 (PST) (envelope-from jim.king@mail.sstar.com) Received: from oasis.zycor.lgc.com by junior.lgc.com (8.8.8/lgc.1.26) id MAA21551; Wed, 4 Nov 1998 12:52:16 -0600 (CST) Received: from maroon by oasis.zycor.lgc.com (8.8.8/lgc.1.20) id MAA04000; Wed, 4 Nov 1998 12:52:02 -0600 (CST) Message-Id: <199811041852.MAA04000@oasis.zycor.lgc.com> X-Sender: jim.king@mail.sstar.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Wed, 04 Nov 1998 12:52:02 -0600 To: David Wolfskill , freebsd-stable@FreeBSD.ORG, gaylord@gaylord.async.vt.edu From: Jim King Subject: Re: has this been fixed? In-Reply-To: <199811041759.JAA18450@pau-amma.whistle.com> References: <199811040329.WAA02779@gaylord.async.vt.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 09:59 AM 11/4/98 -0800, David Wolfskill wrote: >>From: Clark Gaylord >>Date: Tue, 3 Nov 1998 22:29:28 -0500 (EST) > >>> Just out of curiousity, how did the threshold for "a bit too long" get >>> determined? Is this defined in the IDE standard? Did someone conduct > >>IDE standard? You are funny. Let me guess, that's published on >>www.snakeoil.com, right? > >Ummm.... I didn't ask the original question, but it's not at all clear >to me why it should be "funny." > >Given that someone evidently thinks it is, I gether from context that >the phrase "IDE standard" is a reference to a nonentity? Is there an >expectation that anyone who might ever want to use a FreeBSD system >should know this? There are published documents that are referred to as IDE standards. My experience over the years has been that different drive manufacturers interpret them differently, and newer standards tend to skimp on backwards compatibility with older standards. I always cross my fingers when mixing drives from different manufacturers, or drives that were manufactured more than a year apart. Just last night, the simple act of tossing in a 2-year-old EIDE drive into a system with a 6-month-old UDMA drive resulted in a *completely* non-functional system, until I pulled out the EIDE drive AND reset the BIOS configuration. I absolutely *hate* IDE. Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Nov 4 11:24:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA16893 for freebsd-stable-outgoing; Wed, 4 Nov 1998 11:24:09 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from sabre.goldsword.com (sabre.goldsword.com [199.170.202.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA16819 for ; Wed, 4 Nov 1998 11:23:57 -0800 (PST) (envelope-from jfarmer@sabre.goldsword.com) Received: (from jfarmer@localhost) by sabre.goldsword.com (8.8.8/8.8.8) id OAA24048; Wed, 4 Nov 1998 14:28:10 -0500 (EST) Date: Wed, 4 Nov 1998 14:28:10 -0500 (EST) From: "John T. Farmer" Message-Id: <199811041928.OAA24048@sabre.goldsword.com> To: dhw@whistle.com, freebsd-stable@FreeBSD.ORG, gaylord@gaylord.async.vt.edu, jim.king@mail.sstar.com Subject: Re: has this been fixed? Cc: jfarmer@goldsword.com Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 04 Nov 1998 12:52:02 Jim King said: >There are published documents that are referred to as IDE standards. My >experience over the years has been that different drive manufacturers >interpret them differently, and newer standards tend to skimp on backwards >compatibility with older standards. I always cross my fingers when mixing >drives from different manufacturers, or drives that were manufactured more >than a year apart. > >Just last night, the simple act of tossing in a 2-year-old EIDE drive into >a system with a 6-month-old UDMA drive resulted in a *completely* >non-functional system, until I pulled out the EIDE drive AND reset the BIOS >configuration. I absolutely *hate* IDE. > Some days, SCSI is almost as bad what with the SCSI-2, ultra-SCSI, ultra2-SCSI, etc. I spent >5 hours Monday scratching my head (wasn't much hair left anyway...) after connecting a 5 year old Seagate 1.0GB drive to a new Adaptec 2940UW card. It would boot & run just fine, and a single user could access the drive, read, delete, and move files. If the user started a large database app on the server, then things "got interesting." Stray interrupts would be announced in the console log, the user would hang and soon the server would crash. Proved it wasn't the database by having other users try simple tasks. If 2 or more attempted access to the drive, it went down. Finally traced it to the fact that the Adaptec supplied drivers default the tag command queue size for every device to 16. Varying this number didn't change anything. Finally had to disable tag queueing entirely. (This was a Novell server but I have had similar things bite me under FBSD). Related to IDE, I had a client ask me why I placed the CD-ROM drive on the second IDE channel on the machines I built for him. Told him that it was for performance, both the machines and mine. Seperating the drives meant that I didn't spend time getting Brand X drive to work with Brand Y cd-rom drive... John ------------------------------------------------------------------------- John T. Farmer Proprietor, GoldSword Systems jfarmer@goldsword.com Public Internet Access in East Tennessee Office: (423)691-6498 for info, e-mail to info@goldsword.com Network Design, Internet Services & Servers, Consulting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Nov 4 17:00:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA16182 for freebsd-stable-outgoing; Wed, 4 Nov 1998 17:00:44 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ice.cold.org (cold.org [206.81.134.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA16175 for ; Wed, 4 Nov 1998 17:00:38 -0800 (PST) (envelope-from root@ice.cold.org) Received: (from root@localhost) by ice.cold.org (8.8.8/8.8.5) id SAA02196; Wed, 4 Nov 1998 18:00:27 -0700 (MST) Date: Wed, 4 Nov 1998 18:00:27 -0700 (MST) Message-Id: <199811050100.SAA02196@ice.cold.org> Subject: SECURITY NOTICE: FreeBSD 3.0-RELEASE From: freebsd-errata-update@roguetrader.com To: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ****************************************************************** ** THIS IS AN AUTOMATIC ERRATA UPDATE FOR FREEBSD 3.0-RELEASE ** ****************************************************************** You can retrieve the complete ERRATA from: ftp://ftp.freebsd.org/pub/FreeBSD/3.0-RELEASE/ERRATA.TXT The last update was sent: Sun Nov 1 10:28:37 1998 This update is sent: Wed Nov 4 18:00:26 1998 ------------------------------------------------------------------ ---- SECURITY ADVISORIES: o SA-98:08: IP fragmentation denial of service Fix: Update to 3.0-current or apply patch supplied with advisory 98:08 in: ftp://ftp.freebsd.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-98:08.fragment.asc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Nov 4 21:35:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA18190 for freebsd-stable-outgoing; Wed, 4 Nov 1998 21:35:45 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from amber.ghostwheel.com (www.ghostwheel.com [207.201.56.158] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA18184 for ; Wed, 4 Nov 1998 21:35:42 -0800 (PST) (envelope-from merlin@ghostwheel.com) Received: from avalon.ghostwheel.com (limbo-102.otherland.org [207.201.56.102]) by amber.ghostwheel.com (8.8.8/8.8.5) with SMTP id VAA18849 for ; Wed, 4 Nov 1998 21:33:23 -0800 (PST) Message-Id: <4.1.19981104212624.00b3c6e0@pop.ghostwheel.com> X-Sender: merlin@pop.ghostwheel.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Wed, 04 Nov 1998 21:32:42 -0800 To: freebsd-stable@FreeBSD.ORG From: Christopher Knight Subject: CVSUP for 3.0 stable? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just installed 3.0-release on a clean machine. Is there a 3.0-stable branch that I should be pulling updates from? What would the tag in my supfile be? And does anyone have an example? Thanks! -ck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Nov 5 00:37:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA05560 for freebsd-stable-outgoing; Thu, 5 Nov 1998 00:37:26 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from alcatel.fr (news2.alcatel.fr [194.133.58.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA05402 for ; Thu, 5 Nov 1998 00:37:23 -0800 (PST) (envelope-from Thierry.Herbelot@alcatel.fr) From: Thierry.Herbelot@alcatel.fr Received: from alcatel.fr (gatekeeper-ssn.alcatel.fr [155.132.180.244]) by mailgate.alcatel.fr (ALCANET/SMTP) with ESMTP id KAA15778; Thu, 5 Nov 1998 10:36:12 +0100 Received: from lune.telspace.alcatel.fr (lune.telspace.alcatel.fr [155.132.144.65]) by aifhs2.alcatel.fr (ALCANET/SMTP2) with ESMTP id JAA29945; Thu, 5 Nov 1998 09:35:42 +0100 (MET) Received: from telss1.telspace.alcatel.fr (telss1.telspace.alcatel.fr [155.132.51.4]) by lune.telspace.alcatel.fr (8.9.1a/8.9.1) with SMTP id JAA27922; Thu, 5 Nov 1998 09:16:02 +0100 (MET) Received: from telspace.alcatel.fr by telss1.telspace.alcatel.fr (4.1/SMI-4.1) id AA20294; Thu, 5 Nov 98 09:18:36 +0100 Received: from localhost by telspace.alcatel.fr with SMTP (1.40.112.12/16.2) id AA243663496; Thu, 5 Nov 1998 09:11:36 +0100 X-Openmail-Hops: 1 Date: Thu, 5 Nov 98 09:11:27 +0100 Message-Id: In-Reply-To: <4.1.19981104212624.00b3c6e0@pop.ghostwheel.com> Subject: CVSUP for 3.0 stable? Mime-Version: 1.0 To: merlin@ghostwheel.com Cc: freebsd-stable@FreeBSD.ORG Content-Type: text/plain; charset=US-ASCII; name="CVSUP" Content-Disposition: inline; filename="CVSUP" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, -Stable is for the moment based on the 2.2.x branch. It is the most stable FreeBSD there is. 3.0 is the first release of the other branch (the -Current branch). It's only a snapshot of the -Current branch at a certain date (wel, it's a bit more ... but let's keep things simple) 3.0 has been released because it's almost -Stable quality, but there are always cases which have not tested by the release team. So after a shake-up period (up to January ?), 3.0 will be named -Stable. For the moment, if you want to follow the development of 3.0, you can follow -Current (I've found a "-Standard" Supfile in /usr/share/cvsup). The tag is '.' Hope this helps TfH > I just installed 3.0-release on a clean machine. > > Is there a 3.0-stable branch that I should be pulling updates from? What > would the tag in my supfile be? And does anyone have an example? > > Thanks! > > -ck > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Nov 5 06:46:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA20033 for freebsd-stable-outgoing; Thu, 5 Nov 1998 06:46:22 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA20020 for ; Thu, 5 Nov 1998 06:46:19 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA005577089; Thu, 5 Nov 1998 09:44:49 -0500 Date: Thu, 5 Nov 1998 09:44:49 -0500 (EST) From: Bill Fumerola To: Christopher Knight Cc: freebsd-stable@FreeBSD.ORG Subject: Re: CVSUP for 3.0 stable? In-Reply-To: <4.1.19981104212624.00b3c6e0@pop.ghostwheel.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 4 Nov 1998, Christopher Knight wrote: > Is there a 3.0-stable branch that I should be pulling updates from? What > would the tag in my supfile be? And does anyone have an example? 3.0 is still in the -CURRENT branch, and will be for a few more months. - bill fumerola [root/billf]@chc-chimes.com - computer horizons corp - - ph:(800)252.2421 x128 / bfumerol@computerhorizons.com - BF1560 - "Logic, like whiskey, loses its beneficial effect when taken in too large quantities" -Lord Dunsany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Nov 5 08:27:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA29832 for freebsd-stable-outgoing; Thu, 5 Nov 1998 08:27:25 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from macon.informatik.uni-tuebingen.de (macon2.Informatik.Uni-Tuebingen.De [134.2.13.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA29803 for ; Thu, 5 Nov 1998 08:27:05 -0800 (PST) (envelope-from sperber@brabantio.informatik.uni-tuebingen.de) Received: from brabantio.informatik.uni-tuebingen.de (brabantio.Informatik.Uni-Tuebingen.De [134.2.12.25]) by macon.informatik.uni-tuebingen.de (8.9.1/8.9.1) with ESMTP id RAA31262 for ; Thu, 5 Nov 1998 17:26:49 +0100 Received: (from sperber@localhost) by brabantio.informatik.uni-tuebingen.de (AIX4.2/UCB 8.7/8.7) id RAA19114; Thu, 5 Nov 1998 17:26:48 +0100 (MET) To: freebsd-stable@FreeBSD.ORG Subject: Re: CPU halts using mpg123 and OSS References: <199810142222.PAA00592@B1FF.nas.nasa.gov> Mime-Version: 1.0 (generated by tm-edit 1.4) Content-Type: text/plain; charset=ISO-8859-1 From: sperber@Informatik.Uni-Tuebingen.De (Michael Sperber [Mr. Preprocessor]) Date: 05 Nov 1998 17:26:48 +0100 Message-ID: Lines: 21 X-Mailer: Gnus v5.6.33/XEmacs 21.0 - "Irish Goat" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id IAA29812 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here's what the OSS people have to say on problems with OSS on FreeBSD. Can anyone in the know clarify what the status is? I couldn't find anything in the freebsd-bugs archive, but maybe I don't know where to look. 4Front> This is a known problem.....we have found a major bug with 4Front> FreeBSD 3.0 and 2.2.7 for that matter and have notified the 4Front> kernel group....thus far we haven't heard anything. 4Front> 4Front> THe problem seems to be in a kernel function call 4Front> vm_page_alloc_contig() which allocates kernel memory and for 4Front> some reason it's not doing the right thing. OSS requires this 4Front> and every now and then we are given some bogus memory address 4Front> by the kernel and that's where it crashes. -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Nov 5 18:22:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA04522 for freebsd-stable-outgoing; Thu, 5 Nov 1998 18:22:29 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from marathon.simons-rock.edu (marathon.simons-rock.edu [208.144.215.19]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA04510 for ; Thu, 5 Nov 1998 18:22:12 -0800 (PST) (envelope-from psion@geekspace.com) Received: (qmail 9088 invoked from network); 6 Nov 1998 03:38:17 -0000 Received: from cwilliams.student.simons-rock.edu (HELO geekspace.com) (207.51.114.13) by marathon.simons-rock.edu with SMTP; 6 Nov 1998 03:38:17 -0000 Message-ID: <36425DBF.AD32A510@geekspace.com> Date: Thu, 05 Nov 1998 21:23:59 -0500 From: Chris Williams X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: Problems with Ports Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recently installed 2.2.7 on a new i386 machine, and everything was working great, until I cvsuped myself to -stable two nights ago. I didn't have any problems making the world or a new kernel, but when I got the new sources I also got the new ports tree, and none of the ports I install seem to work now, they all fail with the message: ELF interpreter /usr/libexec/ld-elf.so.1 not found Abort trap Also, sometime when I try to install packages from sysinstall, I get an error message that it can't find XFree86 (which is required for such-and-such package), yet I have X installed, and it could find it fine before I upgraded. What did I do wrong?? Oh, also I'm having a weird problem (this didn't change between .7 and -stable) with a MOO I'm running. When I try to load a large MOO db, it starts to load, and then panics that malloc() failed, always at about the same point. I figured out, however, that if I run it as root, it works fine. If there some limit on how much memory a normal-user's process can use? The really weird thing about it, is that I have it set to setuid to a relatively non-priveledged user, yet it still only works when run from root. -- -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GCS/IT/M/P/S d?- s+:- a17>? C++++$ UBLS++$>++++ P--- L++>+++ E---- W+++$ N- !o K? w@$ !O M-- V-- PS+++ PE Y+ PGP- t+ 5-(++) X+ R+ tv>! b+++ DI+++ D+ G++ e* h!*>++ r%>++ !y->$ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Nov 5 19:38:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA10568 for freebsd-stable-outgoing; Thu, 5 Nov 1998 19:38:21 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from earth.anet-stl.com (earth.anet-stl.com [209.83.128.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA10563 for ; Thu, 5 Nov 1998 19:38:19 -0800 (PST) (envelope-from doogie@earth.anet-stl.com) Received: from localhost (localhost.anet-stl.com [127.0.0.1]) by earth.anet-stl.com (VMailer) with SMTP id 22A987826; Thu, 5 Nov 1998 21:38:05 -0600 (CST) Date: Thu, 5 Nov 1998 21:38:00 -0600 (CST) From: Jason Young Reply-To: Jason Young To: Chris Williams Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Problems with Ports In-Reply-To: <36425DBF.AD32A510@geekspace.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 5 Nov 1998, Chris Williams wrote: > I recently installed 2.2.7 on a new i386 machine, and everything was > working great, until I cvsuped myself to -stable two nights ago. I > didn't have any problems making the world or a new kernel, but when I > got the new sources I also got the new ports tree, and none of the ports > I install seem to work now, they all fail with the message: > > ELF interpreter /usr/libexec/ld-elf.so.1 not found > Abort trap You installed a 3.0 binary package on a 2.2.7 box (I did the same thing myself a couple times, I have mixed server versions around the office and forgot). > Also, sometime when I try to install packages from sysinstall, I get an > error message that it can't find XFree86 (which is required for > such-and-such package), yet I have X installed, and it could find it > fine before I upgraded. > What did I do wrong?? > > Oh, also I'm having a weird problem (this didn't change between .7 and > -stable) with a MOO I'm running. When I try to load a large MOO db, it > starts to load, and then panics that malloc() failed, always at about > the same point. I figured out, however, that if I run it as root, it > works fine. If there some limit on how much memory a normal-user's > process can use? > The really weird thing about it, is that I have it set to setuid to a > relatively non-priveledged user, yet it still only works when run from > root. Your login.conf limits are kicking in. In csh or tcsh use 'limit' to see what they're currently set to. Edit /etc/login.conf to give the default class (or a new class if you so choose) a higher limit. Be sure to do a cap_mkdb /etc/login.conf after that. Jason Young ANET Chief Network Engineer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Nov 5 20:05:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA13316 for freebsd-stable-outgoing; Thu, 5 Nov 1998 20:05:18 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from marathon.simons-rock.edu (marathon.simons-rock.edu [208.144.215.19]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA13310 for ; Thu, 5 Nov 1998 20:05:16 -0800 (PST) (envelope-from da5id@simons-rock.edu) From: da5id@simons-rock.edu Received: (qmail 12757 invoked from network); 6 Nov 1998 05:21:11 -0000 Received: from blacksun.student.simons-rock.edu (HELO simons-rock.edu) (207.51.114.72) by marathon.simons-rock.edu with SMTP; 6 Nov 1998 05:21:11 -0000 Message-ID: <36427565.AEDA329E@simons-rock.edu> Date: Thu, 05 Nov 1998 23:04:53 -0500 X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 2.2.7-STABLE i386) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: Re: Problems with Ports References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jason Young wrote: > You installed a 3.0 binary package on a 2.2.7 box (I did the same thing > myself a couple times, I have mixed server versions around the office > and forgot). How does one prevent this? - d. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Nov 5 20:18:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA14610 for freebsd-stable-outgoing; Thu, 5 Nov 1998 20:18:02 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from earth.anet-stl.com (earth.anet-stl.com [209.83.128.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA14545 for ; Thu, 5 Nov 1998 20:18:00 -0800 (PST) (envelope-from doogie@earth.anet-stl.com) Received: from localhost (localhost.anet-stl.com [127.0.0.1]) by earth.anet-stl.com (VMailer) with SMTP id 756C07826; Thu, 5 Nov 1998 22:17:50 -0600 (CST) Date: Thu, 5 Nov 1998 22:17:50 -0600 (CST) From: Jason Young To: da5id@simons-rock.edu Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Problems with Ports In-Reply-To: <36427565.AEDA329E@simons-rock.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 5 Nov 1998 da5id@simons-rock.edu wrote: > Jason Young wrote: > > You installed a 3.0 binary package on a 2.2.7 box (I did the same thing > > myself a couple times, I have mixed server versions around the office > > and forgot). > > How does one prevent this? Uh, don't install 3.0 packages on a 2.2 box? Don't get packages from ftp.freebsd.org/pub/FreeBSD/3.0-release/packages, instead get them from 2.2.7-release/packages. Sysinstall defaults to doing this correctly unless you deliberately change it. Alternately, build them yourself from /usr/ports. Jason Young ANET Chief Network Engineer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Nov 6 05:18:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA28578 for freebsd-stable-outgoing; Fri, 6 Nov 1998 05:18:38 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.double-barrel.be (mail.double-barrel.be [194.7.102.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA28573 for ; Fri, 6 Nov 1998 05:18:34 -0800 (PST) (envelope-from mvergall@mail.double-barrel.be) Received: (from uucp@localhost) by mail.double-barrel.be (8.8.8/8.8.8) id OAA03728; Fri, 6 Nov 1998 14:18:06 +0100 (CET) (envelope-from mvergall@mail.double-barrel.be) Received: from ns.double-barrel.be(194.7.102.18) via SMTP by mail.double-barrel.be, id smtpdsU3726; Fri Nov 6 14:18:00 1998 Date: Fri, 6 Nov 1998 14:17:58 +0100 (CET) From: "Michael C. Vergallen" X-Sender: mvergall@ns.double-barrel.be To: da5id@simons-rock.edu cc: freebsd-stable@FreeBSD.ORG Subject: Re: Problems with Ports In-Reply-To: <36427565.AEDA329E@simons-rock.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 5 Nov 1998 da5id@simons-rock.edu wrote: > Jason Young wrote: > > You installed a 3.0 binary package on a 2.2.7 box (I did the same thing > > myself a couple times, I have mixed server versions around the office > > and forgot). > > How does one prevent this? This is a retorical question you know the answer to ... namely upgrade the older ones to 3.0 .. I know it's a lot off work to do them all ... I'm just starting the upgrade process now and they all have to be done by monday. Michael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Nov 6 14:30:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13352 for freebsd-stable-outgoing; Fri, 6 Nov 1998 14:30:56 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.double-barrel.be (mail.double-barrel.be [194.7.102.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA13343 for ; Fri, 6 Nov 1998 14:30:53 -0800 (PST) (envelope-from mvergall@mail.double-barrel.be) Received: (from uucp@localhost) by mail.double-barrel.be (8.8.8/8.8.8) id XAA00531 for ; Fri, 6 Nov 1998 23:30:38 +0100 (CET) (envelope-from mvergall@mail.double-barrel.be) Received: from ns.double-barrel.be(194.7.102.18) via SMTP by mail.double-barrel.be, id smtpdUhs529; Fri Nov 6 23:30:34 1998 Date: Fri, 6 Nov 1998 23:30:34 +0100 (CET) From: "Michael C. Vergallen" X-Sender: mvergall@ns.double-barrel.be To: freebsd-stable@FreeBSD.ORG Subject: error compiling sane Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, The sane package in the /usr/ports/graphics/sane had a problem when running it under 2.2.7 stable. namely patch-04 has to be deleted from the patch directory. Michael --- Michael C. Vergallen A.k.A. Mad Mike, Sportstraat 28 http://www.double-barrel.be/mvergall/ B 9000 Gent ftp://ftp.double-barrel.be/pub/linux/ Belgium tel : 32-9-2227764 Fax : 32-9-2224976 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Nov 6 14:59:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16760 for freebsd-stable-outgoing; Fri, 6 Nov 1998 14:59:30 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA16750 for ; Fri, 6 Nov 1998 14:59:27 -0800 (PST) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id XAA23299; Fri, 6 Nov 1998 23:59:02 +0100 (MET) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Fri, 6 Nov 1998 23:59:02 +0100 (MET) Mime-Version: 1.0 To: sperber@Informatik.Uni-Tuebingen.De (Michael Sperber [Mr. Preprocessor]) Cc: freebsd-stable@FreeBSD.ORG Subject: Re: CPU halts using mpg123 and OSS References: <199810142222.PAA00592@B1FF.nas.nasa.gov> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which I am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 06 Nov 1998 23:59:01 +0100 In-Reply-To: sperber@Informatik.Uni-Tuebingen.De's message of "05 Nov 1998 17:26:48 +0100" Message-ID: Lines: 12 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id OAA16756 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sperber@Informatik.Uni-Tuebingen.De (Michael Sperber [Mr. Preprocessor]) writes: > Here's what the OSS people have to say on problems with OSS on > FreeBSD. Can anyone in the know clarify what the status is? I > couldn't find anything in the freebsd-bugs archive, but maybe I don't > know where to look. Ask them what they mean by "notifying the kernel group", and whether they have submitted a PR. My guess is they haven't. DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Nov 6 15:30:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA21122 for freebsd-stable-outgoing; Fri, 6 Nov 1998 15:30:22 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA21114 for ; Fri, 6 Nov 1998 15:30:19 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca6-19.ix.netcom.com [205.186.213.19]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id PAA16022; Fri, 6 Nov 1998 15:30:04 -0800 (PST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.8.8/8.6.9) id PAA10143; Fri, 6 Nov 1998 15:30:01 -0800 (PST) Date: Fri, 6 Nov 1998 15:30:01 -0800 (PST) Message-Id: <199811062330.PAA10143@silvia.hip.berkeley.edu> To: mvergall@mail.double-barrel.be CC: freebsd-stable@FreeBSD.ORG In-reply-to: (mvergall@mail.double-barrel.be) Subject: Re: error compiling sane From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * The sane package in the /usr/ports/graphics/sane had a problem when * running it under 2.2.7 stable. namely patch-04 has to be deleted from the * patch directory. Please send such reports to the maintainer. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Nov 7 01:10:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA11651 for freebsd-stable-outgoing; Sat, 7 Nov 1998 01:10:58 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from vega.pfts.com (vega.pfts.com [193.193.196.239]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA11646 for ; Sat, 7 Nov 1998 01:10:51 -0800 (PST) (envelope-from max@vega.pfts.com) Received: from vega.pfts.com (big_brother [192.168.1.1]) by vega.pfts.com (8.9.1/8.9.1) with ESMTP id LAA28351 for ; Sat, 7 Nov 1998 11:15:31 +0200 (EET) (envelope-from max@vega.pfts.com) Message-ID: <36440E77.3758284D@vega.pfts.com> Date: Sat, 07 Nov 1998 11:10:15 +0200 From: Maxim Sobolev X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: calcru: negative time of -71345076 usec for pid 23891 (make) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All, Does anybody know what does this mysterious message means? calcru: negative time of -71345076 usec for pid 23891 (make) Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Nov 7 05:45:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA04313 for freebsd-stable-outgoing; Sat, 7 Nov 1998 05:45:15 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from tasam.com (tasam.com [198.232.144.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA04308 for ; Sat, 7 Nov 1998 05:45:13 -0800 (PST) (envelope-from clash@tasam.com) Received: from bug (bug.tasam.com [198.232.144.254]) by tasam.com (8.9.1/8.9.1) with SMTP id IAA22422; Sat, 7 Nov 1998 08:43:16 -0500 (EST) Message-ID: <000e01be0a54$9196eab0$fe90e8c6@bug.tasam.com> From: "Joe Gleason" To: "Maxim Sobolev" , Subject: Re: calcru: negative time of -71345076 usec for pid 23891 (make) Date: Sat, 7 Nov 1998 08:43:07 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2110.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I got one of those also on my FreeBSD 3.0-current system. I have no idea what it is, I'm jsut letting you know that it happens to others also. Joe Gleason Tasam >Hi All, > >Does anybody know what does this mysterious message means? > >calcru: negative time of -71345076 usec for pid 23891 (make) > >Maxim > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message