From owner-freebsd-current Sun Apr 14 0:39:52 2002 Delivered-To: freebsd-current@freebsd.org Received: from rwcrmhc54.attbi.com (rwcrmhc54.attbi.com [216.148.227.87]) by hub.freebsd.org (Postfix) with ESMTP id 1225F37B400 for ; Sun, 14 Apr 2002 00:39:51 -0700 (PDT) Received: from blossom.cjclark.org ([12.234.91.48]) by rwcrmhc54.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020414073950.PVCL15826.rwcrmhc54.attbi.com@blossom.cjclark.org>; Sun, 14 Apr 2002 07:39:50 +0000 Received: (from cjc@localhost) by blossom.cjclark.org (8.11.6/8.11.6) id g3E7dnI51888; Sun, 14 Apr 2002 00:39:49 -0700 (PDT) (envelope-from cjc) Date: Sun, 14 Apr 2002 00:39:49 -0700 From: "Crist J. Clark" To: Jason Cc: Freebsd Current Subject: Re: Couple of weird messages in logs, and crashing to debuggier. Message-ID: <20020414003949.G43915@blossom.cjclark.org> References: <001501c1e2c8$4da39fb0$0300000a@desktop> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <001501c1e2c8$4da39fb0$0300000a@desktop>; from freebsd-current@tcpipbitch.net on Sat, Apr 13, 2002 at 04:50:44AM -0400 X-URL: http://people.freebsd.org/~cjc/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Apr 13, 2002 at 04:50:44AM -0400, Jason wrote: > After finally getting machine to stop crashing, I noticed these, no clue > what they mean.... Any ideas > > link_elf: symbol pfil_add_hook undefined This is the ipl.ko (IPFilter) kernel module failing to load. It is currently broken. -- Crist J. Clark | cjclark@alum.mit.edu | cjclark@jhu.edu http://people.freebsd.org/~cjc/ | cjc@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 14 1:34:20 2002 Delivered-To: freebsd-current@freebsd.org Received: from mailout04.sul.t-online.com (mailout04.sul.t-online.com [194.25.134.18]) by hub.freebsd.org (Postfix) with ESMTP id 63A9837B404; Sun, 14 Apr 2002 01:34:17 -0700 (PDT) Received: from fwd05.sul.t-online.de by mailout04.sul.t-online.com with smtp id 16wfSe-0005Ln-06; Sun, 14 Apr 2002 10:34:12 +0200 Received: from Magelan.Leidinger.net (520065502893-0001@[217.229.218.100]) by fmrl05.sul.t-online.com with esmtp id 16wfSb-1VUcy0C; Sun, 14 Apr 2002 10:34:09 +0200 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.12.2/8.12.2) with ESMTP id g3E8YIJx000632; Sun, 14 Apr 2002 10:34:22 +0200 (CEST) (envelope-from netchild@Leidinger.net) Message-Id: <200204140834.g3E8YIJx000632@Magelan.Leidinger.net> Date: Sun, 14 Apr 2002 10:34:18 +0200 (CEST) From: Alexander Leidinger Subject: Re: ATA errors on recent -current To: dwcjr@inethouston.net Cc: current@FreeBSD.ORG, sos@FreeBSD.ORG In-Reply-To: <20020414050301.GA34066@leviathan.inethouston.net> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT X-Sender: 520065502893-0001@t-dialin.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 14 Apr, David W. Chapman Jr. wrote: > I updated to -current today and am now getting these errors > > ad0: READ command timeout tag=1 serv=1 - resetting > ata0: resetting devices .. ad0: invalidating queued requests > done Turn off tagged queing. Søren knows about this error and tries to reproduce it (but fails as far as I know). Bye, Alexander. -- "One world, one web, one program" -- Microsoft promotional ad "Ein Volk, ein Reich, ein Fuehrer" -- Adolf Hitler http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 14 2:56:34 2002 Delivered-To: freebsd-current@freebsd.org Received: from skaarup.org (skaarup.org [130.228.230.140]) by hub.freebsd.org (Postfix) with SMTP id E966F37B41B for ; Sun, 14 Apr 2002 02:56:31 -0700 (PDT) Received: (qmail 27459 invoked by uid 0); 14 Apr 2002 09:56:30 -0000 Received: from localhost (HELO skaarup.org) (127.0.0.1) by localhost with SMTP; 14 Apr 2002 09:56:27 -0000 Received: (qmail 27441 invoked by uid 1039); 14 Apr 2002 09:56:27 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 14 Apr 2002 09:56:27 -0000 Date: Sun, 14 Apr 2002 11:56:27 +0200 (CEST) From: Rasmus Skaarup To: Terry Lambert Cc: freebsd-current@freebsd.org Subject: Re: pam_unix.so error and lock order reversal In-Reply-To: <3CB80C4F.B37B1C37@mindspring.com> Message-ID: <20020414115442.X27398-100000@skaarup.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS perl-11 @skaarup.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 13 Apr 2002, Terry Lambert wrote: > Rasmus Skaarup wrote: > > 2) When logged in as root, and su'd to a non-root user, I cannot ssh to a > > 4.5-STABLE machine.. It just hangs. But when logged in as non-root, it > > works fine. Is this somekind of security feature? :-) > > Pretty much. The user it attempts to log you in as is still > "root", because that's still your identity, even if it's not > your current credential. [...] > You might want to try using "su -" instead of "su", in > order to actually *become* the other person. I am. Best regards, Rasmus Skaarup To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 14 2:57:44 2002 Delivered-To: freebsd-current@freebsd.org Received: from skaarup.org (skaarup.org [130.228.230.140]) by hub.freebsd.org (Postfix) with SMTP id 4FC3437B405 for ; Sun, 14 Apr 2002 02:57:39 -0700 (PDT) Received: (qmail 27491 invoked by uid 0); 14 Apr 2002 09:57:38 -0000 Received: from localhost (HELO skaarup.org) (127.0.0.1) by localhost with SMTP; 14 Apr 2002 09:57:35 -0000 Received: (qmail 27476 invoked by uid 1039); 14 Apr 2002 09:57:34 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 14 Apr 2002 09:57:34 -0000 Date: Sun, 14 Apr 2002 11:57:34 +0200 (CEST) From: Rasmus Skaarup To: Steve Kargl Cc: freebsd-current@freebsd.org Subject: Re: swi_net: unregistered isr number: 18 In-Reply-To: <20020413110740.A56925@troutmask.apl.washington.edu> Message-ID: <20020414115650.J27398-100000@skaarup.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS perl-11 @skaarup.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm getting the same message a lot when using 'dhclient'. Best regards, Rasmus Skaarup On Sat, 13 Apr 2002, Steve Kargl wrote: > cvsup and make world sequence from this morning > (0841 PDT) yields the following warning at boot > > swi_net: unregistered isr number: 18. > > System appears to be running fine. > > -- > Steve > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 14 5: 3:43 2002 Delivered-To: freebsd-current@freebsd.org Received: from mclean.mail.mindspring.net (mclean.mail.mindspring.net [207.69.200.57]) by hub.freebsd.org (Postfix) with ESMTP id D117837B41A for ; Sun, 14 Apr 2002 05:03:27 -0700 (PDT) Received: from user-2injgvk.dialup.mindspring.com ([165.121.195.244] helo=europa2) by mclean.mail.mindspring.net with smtp (Exim 3.33 #1) id 16wiis-0001cO-00; Sun, 14 Apr 2002 08:03:10 -0400 Message-Id: <3.0.6.32.20020414080107.00da8a48@imatowns.com> X-Sender: ggombert@imatowns.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Sun, 14 Apr 2002 08:01:07 -0400 To: Rasmus Skaarup , Steve Kargl From: Glenn Gombert Subject: Re: swi_net: unregistered isr number: 18 Cc: freebsd-current@freebsd.org In-Reply-To: <20020414115650.J27398-100000@skaarup.org> References: <20020413110740.A56925@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have seen the same message on a couple FreeBSD systems that I run over the last several months, but they both seem to be running fine. I was wondering if it was a 'hack attempt' of somekind over my DSL line.... Glenn Gombert ggombert@imatowns.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 14 6: 1:25 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.speakeasy.net (mail15.speakeasy.net [216.254.0.215]) by hub.freebsd.org (Postfix) with ESMTP id 0A89737B400 for ; Sun, 14 Apr 2002 06:01:24 -0700 (PDT) Received: (qmail 4406 invoked from network); 14 Apr 2002 13:01:22 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail15.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 14 Apr 2002 13:01:22 -0000 Received: from laptop.baldwin.cx (john@laptop.baldwin.cx [192.168.0.4]) by server.baldwin.cx (8.11.6/8.11.6) with ESMTP id g3ED2Nv69558; Sun, 14 Apr 2002 09:02:23 -0400 (EDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3.0.6.32.20020414080107.00da8a48@imatowns.com> Date: Sun, 14 Apr 2002 09:00:40 -0400 (EDT) From: John Baldwin To: Glenn Gombert Subject: Re: swi_net: unregistered isr number: 18 Cc: freebsd-current@freebsd.org, Steve Kargl , Rasmus Skaarup Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 14-Apr-2002 Glenn Gombert wrote: > I have seen the same message on a couple FreeBSD systems that I run over > the last several months, but they both seem to be running fine. I was > wondering if it was a 'hack attempt' of somekind over my DSL line.... No it's a kernel bug of some sort. I've only seen it on some test kernels (not CVS kernels) during dhclient on my laptop. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 14 6:57: 8 2002 Delivered-To: freebsd-current@freebsd.org Received: from mao.stokely.org (mao.stokely.org [65.84.64.228]) by hub.freebsd.org (Postfix) with ESMTP id C93A437B404 for ; Sun, 14 Apr 2002 06:56:51 -0700 (PDT) Received: by mao.stokely.org (Postfix, from userid 2074) id 91EB74B66A; Sun, 14 Apr 2002 06:56:46 -0700 (PDT) Date: Sun, 14 Apr 2002 06:56:46 -0700 From: Murray Stokely To: John Angelmo Cc: Elric of Melnibone , freebsd-current Subject: Re: Problem with rl Message-ID: <20020414135646.GM1341@freebsdmall.com> References: <3CB7F184.3090108@veidit.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="1LKvkjL3sHcu1TtY" Content-Disposition: inline In-Reply-To: <3CB7F184.3090108@veidit.net> User-Agent: Mutt/1.3.25i X-GPG-Key-ID: 1024D/0E451F7D X-GPG-Key-Fingerprint: E2CA 411D DD44 53FD BB4B 3CB5 B4D7 10A2 0E45 1F7D Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --1LKvkjL3sHcu1TtY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Apr 13, 2002 at 10:51:16AM +0200, John Angelmo wrote: > The errormessage I get is: >=20 > rl0: Irq 5 at device 2.0 pci 1 > Couldn't map ports/memory > device_probe_and_attatch( rl0 attatch retuned 6) Is "PNP OS installed" selected in your BIOS? If so, try without this option set. - Murray --1LKvkjL3sHcu1TtY Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Comment: For info see http://www.gnupg.org iD8DBQE8uYqdtNcQog5FH30RAhtsAJ9k+/USMDLoiPTc1xhyWplbIII/AACgkZ1R kDLGnaKyexfe9gv/YILYATM= =EtOI -----END PGP SIGNATURE----- --1LKvkjL3sHcu1TtY-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Apr 14 7:55:19 2002 Delivered-To: freebsd-current@freebsd.org Received: from mailout08.sul.t-online.com (mailout08.sul.t-online.com [194.25.134.20]) by hub.freebsd.org (Postfix) with ESMTP id 06E4D37B400; Sun, 14 Apr 2002 07:55:11 -0700 (PDT) Received: from fwd06.sul.t-online.de by mailout08.sul.t-online.com with smtp id 16wlM6-0003ND-06; Sun, 14 Apr 2002 16:51:50 +0200 Received: from pc-micha.mc.hp.com (320021761316-0001@[217.230.23.164]) by fmrl06.sul.t-online.com with esmtp id 16wlLx-1Q1IcCC; Sun, 14 Apr 2002 16:51:41 +0200 Received: from pc-micha.mc.hp.com (michaelc@localhost [127.0.0.1]) by pc-micha.mc.hp.com (8.12.3/8.12.3) with ESMTP id g3E9luoB000771; Sun, 14 Apr 2002 11:47:56 +0200 (MEST) (envelope-from michaelc@space.ebiz-hp.com) Received: from localhost (michaelc@localhost) by pc-micha.mc.hp.com (8.12.3/8.12.3/Submit) with ESMTP id g3E9lpdc000768; Sun, 14 Apr 2002 11:47:55 +0200 (MEST) X-Authentication-Warning: pc-micha.mc.hp.com: michaelc owned process doing -bs Date: Sun, 14 Apr 2002 11:47:51 +0200 (MEST) From: Michael Class X-X-Sender: michaelc@pc-micha.mc.hp.com Reply-To: Michael Class To: Alexander Leidinger Cc: dwcjr@inethouston.net, , Subject: Re: ATA errors on recent -current In-Reply-To: <200204140834.g3E8YIJx000632@Magelan.Leidinger.net> Message-ID: <20020414113822.S740-100000@pc-micha.mc.hp.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT X-Sender: 320021761316-0001@t-dialin.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, just as an additional datapoint. My 5.0-current system panics during boot when I enable tagged queing. This did not happen with a system built on March 16th, but there have been numerous changes on the ata-subsystem inbetween and I was not able to trace this down to a specific change. The trace looks like this (this is just handwritten) ad_service (e5217c00,1,12788100,0,0) +0x36 ad_transfer (e51fcdc0) ata_start adstrategy ar_rw ar_promise_read_conf ata_raiddisk_attach ad_attach The panic appears right when the disks should be attached. This happens with a GENERIC kernel too! This is a dmesg output without tagging: Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Sun Apr 14 09:29:41 MEST 2002 michaelc@pc-micha.mc.hp.com:/usr/src/sys/i386/compile/MCSMP2 Preloaded elf kernel "/boot/kernel/kernel" at 0xc0523000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc05230a8. Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (996.55-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x68a Stepping = 10 Features=0x383fbff real memory = 1073676288 (1048512K bytes) avail memory = 1038569472 (1014228K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00178011, at 0xfec00000 Pentium Pro MTRR support enabled Using $PIR table, 8 entries at 0xc00f7570 npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 acpi_cpu0: on acpi0 acpi_cpu1: on acpi0 acpi_tz0: on acpi0 acpi_button0: on acpi0 acpi_pcib0: port 0xcf8-0xcff on acpi0 pci0: on acpi_pcib0 agp0: mem 0xe0000000-0xe3ffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xcc00-0xcc1f irq 10 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ums0: KYE Genius USB Wheel Mouse, rev 1.00/0.00, addr 2, iclass 3/1 ums0: 3 buttons and Z dir. ulpt0: Hewlett-Packard DeskJet 990C, rev 1.10/1.00, addr 3, iclass 7/1 ulpt0: using bi-directional mode uhci1: port 0xd800-0xd81f irq 10 at device 7.3 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pci0: at device 7.4 (no driver attached) xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xc800-0xc87f mem 0xdffffe80-0xdffffeff irq 12 at device 9.0 on pci0 xl0: Ethernet address: 00:10:5a:d7:dd:9c miibus0: on xl0 xlphy0: <3Com internal media interface> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pcm0: port 0xc400-0xc41f irq 9 at device 10.0 on pci0 bktr0: mem 0xdedfe000-0xdedfefff irq 10 at device 11.0 on pci0 bktr0: Hauppauge Model 61344 D121 bktr0: Detected a MSP3410D-B4 at 0x80 bktr0: Hauppauge WinCast/TV, Philips FR1216 PAL FM tuner, msp3400c stereo, remote control. pci0: at device 11.1 (no driver attached) sym0: <875> port 0xd000-0xd0ff mem 0xdfffe000-0xdfffefff,0xdfffff00-0xdfffffff irq 11 at device 12.0 on pci0 sym0: Symbios NVRAM, ID 7, Fast-20, SE, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: using LOAD/STORE-based firmware. sym0: SCAN FOR LUNS disabled for targets 0 1 2 3 4 5 6 8 9 10 11 12 13 14 15. acpi_button1: on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 fdc0: port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0 port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold lpt0: on ppbus0 lpt0: Interrupt-driven port orm0:
Hi everyone,
  I has seen the manual and /sys/ufs/ufs/README.* . I add = the following to the kernel conf:
 options  &nb= sp;      UFS_EXTATTR    &nbs= p;            = ;            =             &= nbsp;          
&nb= sp;options         UFS_EXTATTR_AU= TOSTART           =             &= nbsp;           &n= bsp;      
 options  &nb= sp;      UFS_ACL  
 T= hen, I saw extattrctl and setextattr's manual. But I do not know what's m= eaning.
 For example, I has a user name Jack, who is a wh= eel member.
 I want to deny him to access /boot/, how ca= n I do?
 Thanks!
Best Regards
&nbs= p; Ouyang kai


=B4=D3=CD=F8= =D5=BE=B5=C3=B5=BD=B8=FC=B6=E0=D0=C5=CF=A2=A1=A3MSN Explorer =C3=E2=B7=D1= =CF=C2=D4=D8=A3=BAhttp://explore= r.msn.com/lccn

------=_NextPart_001_0001_01C1E79D.70AC8240-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 18 23:14:35 2002 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id F278937B419 for ; Thu, 18 Apr 2002 23:14:30 -0700 (PDT) Received: from localhost (ilmar@localhost) by fledge.watson.org (8.11.6/8.11.6) with ESMTP id g3J6EJt42410; Fri, 19 Apr 2002 02:14:19 -0400 (EDT) (envelope-from ilmar@watson.org) Date: Fri, 19 Apr 2002 02:14:19 -0400 (EDT) From: "Ilmar S. Habibulin" To: kai ouyang Cc: current@FreeBSD.org Subject: Re: How use UFS_ACL function? In-Reply-To: Message-ID: <20020419020817.X41830-100000@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 19 Apr 2002, kai ouyang wrote: > options UFS_EXTATTR > options UFS_EXTATTR_AUTOSTART > options UFS_ACL Now you have to create backing storage for extended attributes, ALC in your case. This can be achieved by the following commands: # cd / # mkdir .attribute .attribute/system # cd .attribute/system # extattrctl initattr -p / 388 posix1e.acl_access # extattrctl initattr -p / 388 posix1e.acl_default > For example, I has a user name Jack, who is a wheel member. > I want to deny him to access /boot/, how can I do? After reboot you will have the ability to set acls on your root filesystem. So issue the command: # setfacl -m u:Jack: /boot and check it with getfacl /boot. The output should be like: ... user:Jack:--- ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 18 23:32: 1 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.acns.ab.ca (mail.acns.ab.ca [142.179.151.95]) by hub.freebsd.org (Postfix) with ESMTP id E450537B419 for ; Thu, 18 Apr 2002 23:31:39 -0700 (PDT) Received: from colnta.acns.ab.ca (colnta.acns.ab.ca [192.168.1.2]) by mail.acns.ab.ca (8.12.2/8.12.2) with ESMTP id g3J6VY3S006277 for ; Fri, 19 Apr 2002 00:31:34 -0600 (MDT) (envelope-from davidc@colnta.acns.ab.ca) Received: from colnta.acns.ab.ca (localhost [127.0.0.1]) by colnta.acns.ab.ca (8.12.2/8.11.3) with ESMTP id g3J6VYsn054104 for ; Fri, 19 Apr 2002 00:31:34 -0600 (MDT) (envelope-from davidc@colnta.acns.ab.ca) Received: (from davidc@localhost) by colnta.acns.ab.ca (8.12.2/8.12.2/Submit) id g3J6VYT1054103 for current@freebsd.org; Fri, 19 Apr 2002 00:31:34 -0600 (MDT) Date: Fri, 19 Apr 2002 00:31:34 -0600 From: Chad David To: current@freebsd.org Subject: savecore Message-ID: <20020419003134.A54078@colnta.acns.ab.ca> Mail-Followup-To: current@freebsd.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="OXfL5xGRrasGEqWY" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --OXfL5xGRrasGEqWY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Any comments / objections to these patches to savecore and friends? After I get more than two or three md5 named files in var/crash I start to go cross eyed. -- Chad David davidc@acns.ab.ca www.FreeBSD.org davidc@freebsd.org ACNS Inc. Calgary, Alberta Canada Fourthly, The constant breeders, beside the gain of eight shillings sterling per annum by the sale of their children, will be rid of the charge of maintaining them after the first year. - Johnathan Swift --OXfL5xGRrasGEqWY Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="savecore.c.diff" Index: Makefile =================================================================== RCS file: /mnt1/ncvs/src/sbin/savecore/Makefile,v retrieving revision 1.9 diff -u -d -r1.9 Makefile --- Makefile 1 Apr 2002 08:27:19 -0000 1.9 +++ Makefile 19 Apr 2002 06:21:17 -0000 @@ -1,7 +1,5 @@ # $FreeBSD: src/sbin/savecore/Makefile,v 1.9 2002/04/01 08:27:19 phk Exp $ PROG= savecore WARNS= 4 -NOMAN= sorry, not yet. -LDADD= -lmd .include Index: savecore.8 =================================================================== RCS file: /mnt1/ncvs/src/sbin/savecore/savecore.8,v retrieving revision 1.15 diff -u -d -r1.15 savecore.8 --- savecore.8 28 Oct 2001 16:41:56 -0000 1.15 +++ savecore.8 19 Apr 2002 06:20:04 -0000 @@ -42,81 +42,70 @@ .Nm .Fl c .Nm -.Op Fl fkvz -.Op Fl N Ar system -.Ar directory +.Op Fl kvf +.Op directory Op device ... .Sh DESCRIPTION -.Nm Savecore -copies the currently running kernel and its associated core dump into -.Fa directory , -and enters a reboot message and information about the core dump into -the system log. +The +.Nm savecore +command saves system dumps from any and all filesystems that are of type +swap and of type dump to the directory specified on the command line. +If any optional devices are specified +.Nm savecore +will attempt to read dumps from them instead. .Pp -The options are as follows: +The +.Nm savecore +command accepts the following options: .Bl -tag -width indent .It Fl c -Clear the dump, so that future invocations of -.Nm +Clear the dump's header so that future invocations of +.Nm savecore will ignore it. +When this option is specified +.Nm savecore +does not attempt to save the dump, and all other options are ignored. .It Fl f -Force a dump to be taken even if the dump doesn't appear correct or there -is insufficient disk space. +Force a dump to be taken even if it has already been taken. .It Fl k -Do not clear the dump after saving it. -.It Fl N -Use -.Ar system -as the kernel instead of the running kernel (as determined from -.Xr getbootfile 3 ) . +Do not clear the dump header after saving it. .It Fl v -Print out some additional debugging information. -.It Fl z -Compress the core dump and kernel (see -.Xr gzip 1 ) . +Print additional debugging information, including the details of the dump +header to stdout. .El .Pp -.Nm Savecore -checks the core dump in various ways to make sure that it is current and -that it corresponds to the currently running system. -If it passes these checks, it saves the core image in +The +.Nm savecore +command attempts to verify that a core image is valid by verifying it's +header (magic number and version etc.). +If the header passes these checks +.Nm savecore +saves the core image in .Ar directory Ns Pa /vmcore.# -and the system in -.Ar directory Ns Pa /kernel.# +and the header information in +.Ar directory Ns Pa /info.# . The ``#'' is the number from the first line of the file .Ar directory Ns Pa /bounds , -and it is incremented and stored back into the file each time -.Nm +and is incremented and stored back into the file each time +.Nm savecore successfully runs. .Pp -.Nm Savecore -also checks the available disk space before attempting to make the copies. -If there is insufficient disk space in the filesystem containing -.Ar directory , -or if the file -.Ar directory Ns Pa /minfree -exists and the number of free kilobytes (for non-superusers) in the -filesystem after the copies were made would be less than the number -in the first line of this file, the copies are not attempted. -.Pp If -.Nm -successfully copies the kernel and the core dump, the core dump is cleared -so that future invocations of -.Nm +.Nm savecore +successfully saves the core dump, and the +.Fl k +option is not specific, the dump's header is cleared so that future +invocations of +.Nm savecore will ignore it. .Pp -.Nm Savecore -is meant to be called near the end of the initialization file +The +.Nm savecore +command is meant to be called from the initialization file .Pa /etc/rc (see .Xr rc 8 ) . -.Sh BUGS -The minfree code does not consider the effect of compression. .Sh SEE ALSO -.Xr gzip 1 , -.Xr getbootfile 3 , .Xr dumpon 8 , -.Xr syslogd 8 .Sh HISTORY The .Nm Index: savecore.c =================================================================== RCS file: /mnt1/ncvs/src/sbin/savecore/savecore.c,v retrieving revision 1.55 diff -u -d -r1.55 savecore.c --- savecore.c 13 Apr 2002 08:20:15 -0000 1.55 +++ savecore.c 19 Apr 2002 06:14:01 -0000 @@ -43,7 +43,6 @@ #include #include #include -#include #include #include #include @@ -55,7 +54,7 @@ static void printheader(FILE *f, const struct kerneldumpheader *h, const char *device, - const char *md5) + int bounds) { uint64_t dumplen; time_t t; @@ -73,25 +72,68 @@ fprintf(f, " Hostname: %s\n", h->hostname); fprintf(f, " Versionstring: %s", h->versionstring); fprintf(f, " Panicstring: %s\n", h->panicstring); - fprintf(f, " MD5: %s\n", md5); + fprintf(f, " Bounds: %d\n", bounds); } +static int +getbounds(void) { + FILE *fp; + char buf[6]; + int ret; + + ret = 0; + + if ((fp = fopen("bounds", "r")) == NULL) { + warnx("unable to open bounds file, using 0"); + goto new; + } + + if (fgets(buf, sizeof buf, fp) == NULL) { + warnx("unable to read from bounds, using 0"); + goto new; + } + + errno = 0; + ret = (int)strtol(buf, NULL, 10); + if (ret == 0) + if (errno == EINVAL || errno == ERANGE) + warnx("invalid value found in bounds, using 0"); + +new: + if (fp) + fclose(fp); + + if ((fp = fopen("bounds", "w")) == NULL) { + warnx("unable to write to bounds file"); + goto done; + } + + if (verbose) + printf("bounds number: %d\n", ret); + + fprintf(fp, "%d\n", (ret + 1)); + fclose(fp); + +done: + return (ret); +} static void DoFile(const char *device) { struct kerneldumpheader kdhf, kdhl; - char buf[BUFSIZ]; + char buf[BUFSIZ * 64]; struct stat sb; - off_t mediasize, dumpsize, firsthd, lasthd; - char *md5; + off_t mediasize, dumpsize, firsthd, lasthd, dmpcnt; FILE *info; int fd, fdcore, fdinfo, error, wl; + int bounds; u_int sectorsize; if (verbose) printf("Checking for kernel dump on device %s\n", device); + dmpcnt = 0; mediasize = 0; fd = open(device, O_RDWR); if (fd < 0) { @@ -123,7 +165,20 @@ if (verbose) warnx("Magic mismatch on last dump header on %s", device); - goto closefd; + if (force) { + if (memcmp(kdhl.magic, KERNELDUMPMAGIC_CLEARED, + sizeof kdhl.magic) == 0) { + if (verbose) + warnx("Forcing magic on %s", device); + memcpy(kdhl.magic, KERNELDUMPMAGIC, + sizeof kdhl.magic); + } else { + warnx("Unable to force dump"); + goto closefd; + } + } else { + goto closefd; + } } if (dtoh32(kdhl.version) != KERNELDUMPVERSION) { warnx("Unknown version (%d) in last dump header on %s", @@ -152,8 +207,10 @@ warn("First and last dump headers disagree on %s", device); goto closefd; } - md5 = MD5Data((unsigned char *)&kdhl, sizeof kdhl, NULL); - sprintf(buf, "%s.info", md5); + + bounds = getbounds(); + + sprintf(buf, "info.%d", bounds); /* * See if the dump has been saved already. Don't save the dump @@ -162,8 +219,8 @@ if (stat(buf, &sb) == 0) { if (!force) { if (verbose) - printf("Dump on device %s already saved\n", - device); + printf("Dump %d on device %s already saved\n", + bounds, device); goto closefd; } } else if (errno != ENOENT) { @@ -179,7 +236,7 @@ warn("%s", buf); goto closefd; } - sprintf(buf, "%s.core", md5); + sprintf(buf, "vmcore.%d", bounds); fdcore = open(buf, O_WRONLY | O_CREAT | O_TRUNC, 0600); if (fdcore < 0) { warn("%s", buf); @@ -189,12 +246,13 @@ info = fdopen(fdinfo, "w"); if (verbose) - printheader(stdout, &kdhl, device, md5); + printheader(stdout, &kdhl, device, bounds); printf("Saving dump to file %s\n", buf); nsaved++; - printheader(info, &kdhl, device, md5); + printheader(info, &kdhl, device, bounds); + fclose(info); while (dumpsize > 0) { wl = sizeof(buf); @@ -207,12 +265,16 @@ } error = write(fdcore, buf, wl); if (error != wl) { - warn("Write error on %s.core file", md5); + warn("Write error on vmcore.%d file", bounds); goto closeall; } + if (verbose) { + dmpcnt += wl; + printf("%llu\r", dmpcnt); + fflush(stdout); + } dumpsize -= wl; } - close(fdinfo); close(fdcore); if (verbose) @@ -222,7 +284,7 @@ if (clear || !keep) { if (verbose) printf("Clearing dump header\n"); - memset(&kdhl, 0, sizeof kdhl); + memcpy(kdhl.magic, KERNELDUMPMAGIC_CLEARED, sizeof kdhl.magic); lseek(fd, lasthd, SEEK_SET); error = write(fd, &kdhl, sizeof kdhl); if (error != sizeof kdhl) --OXfL5xGRrasGEqWY Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="kerneldump.h.diff" Index: kerneldump.h =================================================================== RCS file: /mnt1/ncvs/src/sys/sys/kerneldump.h,v retrieving revision 1.3 diff -u -d -r1.3 kerneldump.h --- kerneldump.h 3 Apr 2002 07:24:10 -0000 1.3 +++ kerneldump.h 17 Apr 2002 22:05:48 -0000 @@ -60,6 +60,7 @@ struct kerneldumpheader { char magic[20]; #define KERNELDUMPMAGIC "FreeBSD Kernel Dump" +#define KERNELDUMPMAGIC_CLEARED "FreeBSD Cleard Dump" char architecture[12]; uint32_t version; #define KERNELDUMPVERSION 1 --OXfL5xGRrasGEqWY-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Apr 18 23:35:39 2002 Delivered-To: freebsd-current@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id 89A9137B400 for ; Thu, 18 Apr 2002 23:35:37 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1192) id 5FF6CAE1C1; Thu, 18 Apr 2002 23:35:37 -0700 (PDT) Date: Thu, 18 Apr 2002 23:35:37 -0700 From: Alfred Perlstein To: Chad David Cc: current@freebsd.org Subject: Re: savecore Message-ID: <20020419063537.GA38320@elvis.mu.org> References: <20020419003134.A54078@colnta.acns.ab.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020419003134.A54078@colnta.acns.ab.ca> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Chad David [020418 23:32] wrote: > Any comments / objections to these patches to savecore and friends? > > After I get more than two or three md5 named files in var/crash I > start to go cross eyed. I found the md5 names to be particularly disgusting as well. If this reverts the naming of cores to the previous scheme it's seems like a good idea. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 19 0:47:59 2002 Delivered-To: freebsd-current@freebsd.org Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by hub.freebsd.org (Postfix) with ESMTP id 8E9CC37B416 for ; Fri, 19 Apr 2002 00:47:56 -0700 (PDT) Received: from laptop.6bone.nl (penguin.ripe.net [193.0.1.232]) by birch.ripe.net (8.11.6/8.11.6) with SMTP id g3J7lsu31688; Fri, 19 Apr 2002 09:47:54 +0200 Received: (nullmailer pid 23341 invoked by uid 1000); Fri, 19 Apr 2002 07:47:53 -0000 Date: Fri, 19 Apr 2002 09:47:53 +0200 From: Mark Santcroos To: Hiten Pandya Cc: current@FreeBSD.ORG Subject: Re: [REVIEW] - Kernel path changes in -current man pages Message-ID: <20020419074753.GA1811@laptop.6bone.nl> References: <20020419001347.A33940@hpdi.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020419001347.A33940@hpdi.ath.cx> User-Agent: Mutt/1.3.28i X-Handles: MS6-6BONE, MS18417-RIPE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Apr 19, 2002 at 12:13:47AM +0100, Hiten Pandya wrote: > If anyone recalls, I sent a post before which was about changing the > kernel path changes in the (only) -current man pages. As these are > related to -current, I am sending them to this list for a complete > review. Why are you replacing /dev/kmem with the kernel path??? -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 19 1: 1:26 2002 Delivered-To: freebsd-current@freebsd.org Received: from web21102.mail.yahoo.com (web21102.mail.yahoo.com [216.136.227.104]) by hub.freebsd.org (Postfix) with SMTP id D8A6737B41A for ; Fri, 19 Apr 2002 01:01:21 -0700 (PDT) Message-ID: <20020419080121.13800.qmail@web21102.mail.yahoo.com> Received: from [62.254.0.5] by web21102.mail.yahoo.com via HTTP; Fri, 19 Apr 2002 01:01:21 PDT Date: Fri, 19 Apr 2002 01:01:21 -0700 (PDT) From: Hiten Pandya Reply-To: hiten@uk.FreeBSD.org Subject: Re: [REVIEW] - Kernel path changes in -current man pages To: Mark Santcroos Cc: current@FreeBSD.ORG In-Reply-To: <20020419074753.GA1811@laptop.6bone.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --- Mark Santcroos wrote: > On Fri, Apr 19, 2002 at 12:13:47AM +0100, Hiten Pandya wrote: > > If anyone recalls, I sent a post before which was about changing the > > kernel path changes in the (only) -current man pages. As these are > > related to -current, I am sending them to this list for a complete > > review. > > Why are you replacing /dev/kmem with the kernel path??? I knew that question was coming. Anyway, I did that because that /dev/kmem string is longer than /kernel and shorter the /boot/kernel/kernel which Is the main reason as far as my mdoc knowledge goes and the layout on screen generated by: nroff -man dev_kmem_path_change.9 (example) Regards. -- Hiten __________________________________________________ Do You Yahoo!? Yahoo! Tax Center - online filing with TurboTax http://taxes.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 19 1:43:12 2002 Delivered-To: freebsd-current@freebsd.org Received: from uucp.nl.uu.net (uucp.nl.uu.net [193.79.237.146]) by hub.freebsd.org (Postfix) with ESMTP id BDD7037B41C for ; Fri, 19 Apr 2002 01:43:08 -0700 (PDT) Received: from stuyts by uucp.nl.uu.net with UUCP id ; Fri, 19 Apr 2002 08:42:55 +0000 Received: from lodovik.stuyts-spamtrap.nl (lodovik.stuyts.nl [193.78.231.31]) by terminus.stuyts.nl (8.12.3/8.12.3) with ESMTP id g3J8fdZX008728 for ; Fri, 19 Apr 2002 10:41:39 +0200 (CEST) (envelope-from ben@stuyts-spamtrap.nl) Message-Id: <4.3.2.7.2.20020419103428.00bbb070@terminus> X-Sender: benst@terminus X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 19 Apr 2002 10:38:32 +0200 To: current@freebsd.org From: "Ben Stuyts (remove -spamtrap)" Subject: A few lock order reversals Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I updated my -current system yesterday, and I see a few lock order reversals. This one happens during booting: Apr 18 16:35:40 <0.2> terminus kernel: lock order reversal Apr 18 16:35:40 <0.2> terminus kernel: 1st 0xc5ecbbb8 xl0 (network driver) @ /var/src/sys/pci/if_xl.c:1260 Apr 18 16:35:40 <0.2> terminus kernel: 2nd 0xc03590e0 allproc (allproc) @ /var/src/sys/kern/kern_fork.c:352 And these ones during normal use: Apr 18 18:45:09 <0.2> terminus kernel: lock order reversal Apr 18 18:45:09 <0.2> terminus kernel: 1st 0xc64332a4 KNOTE (UMA zone) @ /var/src/sys/vm/uma_core.c:527 Apr 18 18:45:09 <0.2> terminus kernel: 2nd 0xc082a724 PCPU KMAP ENTRY (UMA cpu) @ /var/src/sys/vm/uma_core.c:1301 Apr 19 03:01:12 <0.2> terminus kernel: lock order reversal Apr 19 03:01:12 <0.2> terminus kernel: 1st 0xc64333e4 DIRHASH (UMA zone) @ /var/src/sys/vm/uma_core.c:527 Apr 19 03:01:12 <0.2> terminus kernel: 2nd 0xc082a724 PCPU KMAP ENTRY (UMA cpu) @ /var/src/sys/vm/uma_core.c:1301 If you need more information, kernel config, dmesg, etc, please let me know. Kind regards, Ben To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 19 1:48:57 2002 Delivered-To: freebsd-current@freebsd.org Received: from mailout05.sul.t-online.com (mailout05.sul.t-online.com [194.25.134.82]) by hub.freebsd.org (Postfix) with ESMTP id 9C36937B433 for ; Fri, 19 Apr 2002 01:48:24 -0700 (PDT) Received: from fwd09.sul.t-online.de by mailout05.sul.t-online.com with smtp id 16yS7E-0001HG-02; Fri, 19 Apr 2002 08:43:28 +0200 Received: from twoflower (320072111332-0001@[217.80.121.164]) by fmrl09.sul.t-online.com with smtp id 16yS72-1pfnUmC; Fri, 19 Apr 2002 08:43:16 +0200 Reply-To: From: "Jan Stocker" To: "Long, Scott" , Subject: RE: pcm / mic Date: Thu, 18 Apr 2002 08:42:28 +0200 Message-ID: <000001c1e6a4$350f3a60$fe02010a@twoflower.liebende.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal In-Reply-To: <7CFBF2F0C679B84CAF3B80D39D4B80D60A9BE9@btcexc01.btc.adaptec.com> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 X-Sender: 320072111332-0001@t-dialin.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG A Creative Soundblaster PCI64 (Ensoniq Audio PCI)... $cat at io 0xd000 irq 10 (1p/1r/0v channels duplex default) > -----Original Message----- > From: owner-freebsd-current@FreeBSD.ORG > [mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of Long, Scott > Sent: Thursday, April 18, 2002 10:23 PM > To: 'jstocker@tzi.de'; current@FreeBSD.ORG > Subject: RE: pcm / mic > > > > Hi, > > > > i cant record from /dev/dsp with the record device 'mic'. Is > > there support > > for the microphone input? > > > > What sound card are you using? > > Scott > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 19 2:51:54 2002 Delivered-To: freebsd-current@freebsd.org Received: from 12-234-22-238.client.attbi.com (12-234-90-219.client.attbi.com [12.234.90.219]) by hub.freebsd.org (Postfix) with ESMTP id 2C07B37B41F for ; Fri, 19 Apr 2002 02:51:43 -0700 (PDT) Received: from Master.gorean.org (master.gorean.org [10.0.0.2]) by 12-234-22-238.client.attbi.com (8.12.2/8.12.2) with ESMTP id g3J9phHt042361 for ; Fri, 19 Apr 2002 02:51:43 -0700 (PDT) (envelope-from DougB@FreeBSD.org) Received: from Master.gorean.org (zoot [127.0.0.1]) by Master.gorean.org (8.12.2/8.12.2) with ESMTP id g3J9piLr010545 for ; Fri, 19 Apr 2002 02:51:44 -0700 (PDT) (envelope-from DougB@FreeBSD.org) Received: from localhost (doug@localhost) by Master.gorean.org (8.12.2/8.12.2/Submit) with ESMTP id g3J9piE3010542 for ; Fri, 19 Apr 2002 02:51:44 -0700 (PDT) X-Authentication-Warning: Master.gorean.org: doug owned process doing -bs Date: Fri, 19 Apr 2002 02:51:44 -0700 (PDT) From: Doug Barton X-X-Sender: doug@master.gorean.org To: freebsd-current@FreeBSD.org Subject: Proposal for dealing with sendmail [ug]id bootstrapping Message-ID: <20020419021942.A10172-100000@master.gorean.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG While I do not object to the addition of the new users for sendmail, and I understand the theory of having them own directories for its operation, I think that the current bootstrapping problems are creating too greate a barrier for users who upgrade from source. There are (at least) two groups of users who are distinctly affected: 1. Those who don't use sendmail. Several users have commented, "I have 'NO_SENDMAIL= true' in my /etc/make.conf, so I didn't think this would affect me." I realize that it's not possible at this time to conditionalize mtree stuff... the problem has been discussed before. 2. Users who don't read (or don't understand) UPDATING. This is basically, everybody. My proposal is simple. Change from using names to numeric [ug]id's in mtree, and elsewhere if needed. The plus is that it solves the bootstrapping problem. The negatives involve problems with systems that don't merge the password and group files, and therefore will have directories owned by "weird" users. Another possible difficulty involves systems where there are already users with the numeric values currently used by sendmail. Another, although more complex option would be to add code such as the following (in pseudocode) to /usr/src/etc/Makefile: if ((not grep ^smmsp: /etc/master.passwd) and (not grep ':25:25:' /etc/master.passwd)) then pw useradd -n smmsp -u 25 -c 'Sendmail Submission User' \ -g 25 -s /sbin/nologin -d /var/spool/clientmqueue And repeat for the other two entries. This is more prone to failure, since there are more variables. However, at this point I think it would be better than nothing. -- "We have known freedom's price. We have shown freedom's power. And in this great conflict, ... we will see freedom's victory." - George W. Bush, President of the United States State of the Union, January 28, 2002 Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 19 3:48:52 2002 Delivered-To: freebsd-current@freebsd.org Received: from alternator.sgh.waw.pl (alternator.sgh.waw.pl [194.145.96.100]) by hub.freebsd.org (Postfix) with ESMTP id 8641837B419 for ; Fri, 19 Apr 2002 03:48:44 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by alternator.sgh.waw.pl (Postfix) with SMTP id 9A5372AA31E for ; Fri, 19 Apr 2002 12:48:21 +0200 (CEST) Received: from akson.sgh.waw.pl (akson.sgh.waw.pl [194.145.96.12]) by alternator.sgh.waw.pl (Postfix) with ESMTP id 77E572AA2AB for ; Fri, 19 Apr 2002 12:48:21 +0200 (CEST) Received: (from saper@localhost) by akson.sgh.waw.pl (8.8.8+Sun/8.8.8) id MAA07301 for current@freebsd.org; Fri, 19 Apr 2002 12:48:22 +0200 (MET DST) Date: Fri, 19 Apr 2002 12:48:22 +0200 From: Marcin =?iso-8859-2?Q?CIE=A6LAK?= To: current@freebsd.org Subject: Re: A few lock order reversals + HANG on vnodes? Message-ID: <20020419104822.GA2432@sgh.waw.pl> References: <4.3.2.7.2.20020419103428.00bbb070@terminus> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <4.3.2.7.2.20020419103428.00bbb070@terminus> User-Agent: Mutt/1.3.25i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Even worse, I've had the same messages _and_ all commands accessing one particular file (/sys/i386/conf/THINKPAD if anyone's interested) hanged completely. -- << Marcin Cie¶lak // saper@sgh.waw.pl >> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 19 4: 4:48 2002 Delivered-To: freebsd-current@freebsd.org Received: from clever.eusc.inter.net (clever.eusc.inter.net [213.73.101.4]) by hub.freebsd.org (Postfix) with ESMTP id B9E0037B404 for ; Fri, 19 Apr 2002 04:04:42 -0700 (PDT) Received: from mail.snafu.de ([10.11.0.4] helo=service.snafu.de) by clever.eusc.inter.net with smtp (Exim 3.22 #3) id 16yWC1-0005bg-00; Fri, 19 Apr 2002 13:04:41 +0200 To: Terry Lambert , msch@snafu.de, sos@freebsd.dk, freebsd-current@FreeBSD.ORG From: msch@snafu.de X-Sender: msch@snafu.de Subject: Re: ATA errors on recent -current Date: Fri, 19 Apr 2002 11:04:41 GMT X-Mailer: Endymion MailMan Standard Edition v3.0.35 Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > So: I changed line 186 in sys/dev/ata/ata-disk.c from > > > > adp->num_tags = atadev->param->queuelen; > > > > to > > > > adp->num_tags = 0x10; > > > > which is roughly the half of the reported queuelenght (which is 0x1F). > > > > And, Terry, I can't avoid to disappoint you... there's absolutely *no* > > change in the behaviour of the new kernel :-( > > Uh... the "16" you changed to "10" was decimal, so changining it > to 0x10 changes it to ... 16. > > Rather than point out the hex/decimal confusion earlier, that's > why I said "/2". Ahm, Terry, perhaps I misunderstand you, but: The reported queue-length is 31(dec), which is 0x1F(hex), as stated above. The half of it would be 15.5(dec) what I rounded up to 16(dec), which is approx. 0x10(hex). Where's your point? > Soren's commit is for a -current specific merge. The problems > you are seeing supposedly are in RELENG_4, and will probably not > be effected... though the commit will provide much better > diagnostics than I've suggested. 8-). All I posted here is done, even if my signature states something different, under -current. This last test was done under a -current of Apr 18,2002, 18:00 UTC. I run my allday system, from which I'm posting and writing my e-mail, under -STABLE... I hope that clears things a bit. Ciao/BSD - Matthias To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 19 7:25:58 2002 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id D6F2337B404 for ; Fri, 19 Apr 2002 07:25:54 -0700 (PDT) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 285B05309; Fri, 19 Apr 2002 16:25:53 +0200 (CEST) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Mark Santcroos Cc: Hiten Pandya , current@FreeBSD.ORG Subject: Re: [REVIEW] - Kernel path changes in -current man pages References: <20020419001347.A33940@hpdi.ath.cx> <20020419074753.GA1811@laptop.6bone.nl> From: Dag-Erling Smorgrav Date: 19 Apr 2002 16:25:52 +0200 In-Reply-To: <20020419074753.GA1811@laptop.6bone.nl> Message-ID: Lines: 17 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mark Santcroos writes: > Why are you replacing /dev/kmem with the kernel path??? If you are referring to -.Bl -tag -width /dev/kmem -compact -.It Pa /kernel +.Bl -tag -width /boot/kernel/kernel -compact +.It Pa /boot/kernel/kernel then he's doing it because "/boot/kernel/kernel" is now the widest tag in the list, and the -width argument to .Bl basically means "make the left-hand column at least as wide as this". DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 19 9:29:19 2002 Delivered-To: freebsd-current@freebsd.org Received: from horsey.gshapiro.net (horsey.gshapiro.net [209.220.147.178]) by hub.freebsd.org (Postfix) with ESMTP id 24D8D37B405; Fri, 19 Apr 2002 09:29:08 -0700 (PDT) Received: from horsey.gshapiro.net (gshapiro@localhost [127.0.0.1]) by horsey.gshapiro.net (8.12.3/8.12.3) with ESMTP id g3JGT7mk093497 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 19 Apr 2002 09:29:07 -0700 (PDT) Received: (from gshapiro@localhost) by horsey.gshapiro.net (8.12.3/8.12.3/Submit) id g3JGT7wb093494; Fri, 19 Apr 2002 09:29:07 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15552.17875.373230.467284@horsey.gshapiro.net> Date: Fri, 19 Apr 2002 09:29:07 -0700 From: Gregory Neil Shapiro To: Doug Barton Cc: freebsd-current@FreeBSD.ORG Subject: Re: Proposal for dealing with sendmail [ug]id bootstrapping In-Reply-To: <20020419021942.A10172-100000@master.gorean.org> References: <20020419021942.A10172-100000@master.gorean.org> X-Mailer: VM 7.00 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG DougB> My proposal is simple. Change from using names to numeric [ug]id's DougB> in mtree, and elsewhere if needed. The plus is that it solves the DougB> bootstrapping problem. The negatives involve problems with systems DougB> that don't merge the password and group files, and therefore will DougB> have directories owned by "weird" users. Another possible difficulty DougB> involves systems where there are already users with the numeric DougB> values currently used by sendmail. This could lead to security problems. If the UID is already in use by another user on the system, that user will be able to attack the submission mail queue causing denial of service and an invasion of privacy. Furthermore, it won't fix the problem if NO_SENDMAIL=no as it will only delay the installworld failure until later in the installation process when the sendmail binary is installed. Finally, it would leave behind a broken system for sendmail users. DougB> Another, although more complex option would be to add code such as DougB> the following (in pseudocode) to /usr/src/etc/Makefile: DougB> if ((not grep ^smmsp: /etc/master.passwd) and DougB> (not grep ':25:25:' /etc/master.passwd)) then DougB> pw useradd -n smmsp -u 25 -c 'Sendmail Submission User' \ DougB> -g 25 -s /sbin/nologin -d /var/spool/clientmqueue DougB> And repeat for the other two entries. This is more prone to failure, DougB> since there are more variables. However, at this point I think it DougB> would be better than nothing. I agree this is more prone to failure (even your example above has problems such as just because :25:25: exists, it doesn't mean it belongs to smmsp). It has some of the same problems as above, namely the possible reuse of an existing UID. Although I really would prefer that people who are building from source pay attention to things like the handbook section on what to do when building from source: - section 19.4.1 says to read /usr/src/UPDATING. This issue is documented in that file. - section 19.4.3 says to update for new users and groups before installing. This issue is documented in the handbook itself. - section 19.4 says to subscribe to the mailing list for the branch you are using. This issue has been covered multiple times on both the mailing lists. I guess that is too much to ask for. IMHO, the best solution for that group of people would be to move the creation of /var/spool/clientmqueue to a separate mtree file and use it in src/etc/Makefile's distribution target: .if !defined(NO_SENDMAIL) mtree -deU -f ${.CURDIR}/mtree/sendmail.root.dist -p ${DESTDIR}/ .endif This solves the NO_SENDMAIL case. For users who are using sendmail, the users really do need to exist before an installworld for the reasons given above. So my solution would be to change the installworld: target in src/Makefile.inc1: - installworld: + installworld: installcheck And add the installcheck target: installcheck: .if !defined(NO_SENDMAIL) @if ! `grep -q ^smmsp: /etc/master.passwd`; then \ echo "smmsp user missing. Read /usr/src/UPDATING."; \ false; \ fi; \ if ! `grep -q ^smmsp: /etc/group`; then \ echo "smmsp group missing. Read /usr/src/UPDATING."; \ false; \ fi .endif The installcheck target may be useful for the other checks now and in the future. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 19 9:44:36 2002 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 5D1F437B417; Fri, 19 Apr 2002 09:44:32 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id g3JGiVH56199; Fri, 19 Apr 2002 10:44:31 -0600 (MDT) (envelope-from imp@village.org) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id g3JGiUx55018; Fri, 19 Apr 2002 10:44:30 -0600 (MDT) (envelope-from imp@village.org) Date: Fri, 19 Apr 2002 10:44:08 -0600 (MDT) Message-Id: <20020419.104408.120314787.imp@village.org> To: DougB@FreeBSD.ORG Cc: freebsd-current@FreeBSD.ORG Subject: Re: Proposal for dealing with sendmail [ug]id bootstrapping From: "M. Warner Losh" In-Reply-To: <20020419021942.A10172-100000@master.gorean.org> References: <20020419021942.A10172-100000@master.gorean.org> X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message: <20020419021942.A10172-100000@master.gorean.org> Doug Barton writes: : 2. Users who don't read (or don't understand) UPDATING. This is basically, : everybody. Actually, UPDATING was changed last night to be more explicit about what to do. Let's give that a chance. I don't like the numeric option. I don't like adding users automatically. I could go for a flag that says "if you can't find a user, use uid/gid 0 instead" to mtree, or creating a mtree.sendmail.dist which would only be used if sendmail wasn't disabled in the build. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 19 9:46:11 2002 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 991AC37B416; Fri, 19 Apr 2002 09:46:06 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id g3JGk4H56220; Fri, 19 Apr 2002 10:46:05 -0600 (MDT) (envelope-from imp@village.org) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id g3JGk3x55033; Fri, 19 Apr 2002 10:46:04 -0600 (MDT) (envelope-from imp@village.org) Date: Fri, 19 Apr 2002 10:45:41 -0600 (MDT) Message-Id: <20020419.104541.53227722.imp@village.org> To: gshapiro@FreeBSD.ORG Cc: DougB@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: Proposal for dealing with sendmail [ug]id bootstrapping From: "M. Warner Losh" In-Reply-To: <15552.17875.373230.467284@horsey.gshapiro.net> References: <20020419021942.A10172-100000@master.gorean.org> <15552.17875.373230.467284@horsey.gshapiro.net> X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message: <15552.17875.373230.467284@horsey.gshapiro.net> Gregory Neil Shapiro writes: : .if !defined(NO_SENDMAIL) : mtree -deU -f ${.CURDIR}/mtree/sendmail.root.dist -p ${DESTDIR}/ : .endif Wow! I hadn't read this before making my suggestion. Honest :-) I like his solution. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 19 11:52:26 2002 Delivered-To: freebsd-current@freebsd.org Received: from 12-234-22-238.client.attbi.com (12-234-90-219.client.attbi.com [12.234.90.219]) by hub.freebsd.org (Postfix) with ESMTP id C557D37B416; Fri, 19 Apr 2002 11:52:15 -0700 (PDT) Received: from Master.gorean.org (master.gorean.org [10.0.0.2]) by 12-234-22-238.client.attbi.com (8.12.2/8.12.2) with ESMTP id g3JIqFHt045247; Fri, 19 Apr 2002 11:52:15 -0700 (PDT) (envelope-from DougB@FreeBSD.org) Received: from Master.gorean.org (zoot [127.0.0.1]) by Master.gorean.org (8.12.2/8.12.2) with ESMTP id g3JIqHLr011307; Fri, 19 Apr 2002 11:52:17 -0700 (PDT) (envelope-from DougB@FreeBSD.org) Received: from localhost (doug@localhost) by Master.gorean.org (8.12.2/8.12.2/Submit) with ESMTP id g3JIqHm3011304; Fri, 19 Apr 2002 11:52:17 -0700 (PDT) X-Authentication-Warning: Master.gorean.org: doug owned process doing -bs Date: Fri, 19 Apr 2002 11:52:17 -0700 (PDT) From: Doug Barton X-X-Sender: doug@master.gorean.org To: Gregory Neil Shapiro Cc: freebsd-current@FreeBSD.org Subject: Re: Proposal for dealing with sendmail [ug]id bootstrapping In-Reply-To: <15552.17875.373230.467284@horsey.gshapiro.net> Message-ID: <20020419114901.V11273-100000@master.gorean.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 19 Apr 2002, Gregory Neil Shapiro wrote: > This could lead to security problems. Yes, I stipulated that. > Although I really would prefer that people who are building from source pay > attention to things like the handbook section on what to do when building > from source: We all prefer that. :) The fact is, users don't do it. > I guess that is too much to ask for. IMHO, the best solution for that > group of people would be to move the creation of /var/spool/clientmqueue to > a separate mtree file and use it in src/etc/Makefile's distribution target: > > .if !defined(NO_SENDMAIL) > mtree -deU -f ${.CURDIR}/mtree/sendmail.root.dist -p ${DESTDIR}/ > .endif > > This solves the NO_SENDMAIL case. I like this idea a lot. Wish I'd thought of it. :) > For users who are using sendmail, the > users really do need to exist before an installworld for the reasons given > above. So my solution would be to change the installworld: target in > src/Makefile.inc1: > > - installworld: > + installworld: installcheck I like this idea too. I am perfectly happy to have my whole suggestion shot down as long as it leads to some creative thought about this problem. The status quo is doomed to failure. If you need any help with this stuff, just let me know. Doug -- "We have known freedom's price. We have shown freedom's power. And in this great conflict, ... we will see freedom's victory." - George W. Bush, President of the United States State of the Union, January 28, 2002 Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 19 13:16:13 2002 Delivered-To: freebsd-current@freebsd.org Received: from h38n2fls34o1000.telia.com (h38n2fls34o1000.telia.com [213.64.210.38]) by hub.freebsd.org (Postfix) with ESMTP id 4EB4F37B416 for ; Fri, 19 Apr 2002 13:16:07 -0700 (PDT) Received: from veidit.net ([213.113.64.8]) (authenticated bits=0) by h38n2fls34o1000.telia.com (8.12.2/8.12.2) with ESMTP id g3JKEjq5019876 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Fri, 19 Apr 2002 22:15:59 +0200 (CEST) Message-ID: <3CC07A63.4050406@veidit.net> Date: Fri, 19 Apr 2002 22:13:23 +0200 From: John Angelmo User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.9) Gecko/20020414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: current Subject: Xfree86-4 problem Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG After yesterdays new build I found a problem Xfree86-4 can't start as regular user (exept root) this is the error message I get: AUDIT: Fri Apr 19 22:09:13 2002: 16472 XFree86: client 1 rejected from local host AUDIT: Fri Apr 19 22:09:15 2002: 16472 XFree86: client 1 rejected from local host AUDIT: Fri Apr 19 22:09:17 2002: 16472 XFree86: client 1 rejected from local host AUDIT: Fri Apr 19 22:09:19 2002: 16472 XFree86: client 1 rejected from local host Does anyone have any idea? /John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 19 13:35: 8 2002 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by hub.freebsd.org (Postfix) with ESMTP id 43BEA37B400 for ; Fri, 19 Apr 2002 13:35:06 -0700 (PDT) Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by sasami.jurai.net (8.12.2/8.12.2) with ESMTP id g3JKZ32A031213; Fri, 19 Apr 2002 16:35:04 -0400 (EDT) (envelope-from winter@jurai.net) Date: Fri, 19 Apr 2002 16:35:03 -0400 (EDT) From: "Matthew N. Dodd" To: Dag-Erling Smorgrav Cc: current@FreeBSD.ORG Subject: Re: pam_unix and missing function warnings In-Reply-To: Message-ID: <20020419163452.S42854-100000@sasami.jurai.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 18 Apr 2002, Dag-Erling Smorgrav wrote: > Try the attached patch. You'll need to rebuild libutil and restart > sshd. Works. Thanks. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 19 13:49:25 2002 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-165-226-18.dsl.lsan03.pacbell.net [64.165.226.18]) by hub.freebsd.org (Postfix) with ESMTP id 4202237B416 for ; Fri, 19 Apr 2002 13:49:20 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 97DA866C8C; Fri, 19 Apr 2002 13:49:19 -0700 (PDT) Date: Fri, 19 Apr 2002 13:49:19 -0700 From: Kris Kennaway To: John Angelmo Cc: current Subject: Re: Xfree86-4 problem Message-ID: <20020419134919.A49216@xor.obsecurity.org> References: <3CC07A63.4050406@veidit.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="0F1p//8PRICkK4MW" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <3CC07A63.4050406@veidit.net>; from john@veidit.net on Fri, Apr 19, 2002 at 10:13:23PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --0F1p//8PRICkK4MW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Apr 19, 2002 at 10:13:23PM +0200, John Angelmo wrote: > After yesterdays new build I found a problem > Xfree86-4 can't start as regular user (exept root) Read the fine message you got at install-time and install the wrapper port. Kris --0F1p//8PRICkK4MW Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8wILOWry0BWjoQKURAidwAJ4j/itXlol6Jdy+dNm/5rdH1bEn1wCgoz2j xgnxLgTIzTTAWs3BC8Hl+mA= =1bpg -----END PGP SIGNATURE----- --0F1p//8PRICkK4MW-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 19 15: 5:13 2002 Delivered-To: freebsd-current@freebsd.org Received: from h38n2fls34o1000.telia.com (h38n2fls34o1000.telia.com [213.64.210.38]) by hub.freebsd.org (Postfix) with ESMTP id 0CB2C37B400 for ; Fri, 19 Apr 2002 15:05:10 -0700 (PDT) Received: from veidit.net (c-084071d5.011-19-6762672.cust.bredbandsbolaget.se [213.113.64.8]) (authenticated bits=0) by h38n2fls34o1000.telia.com (8.12.2/8.12.2) with ESMTP id g3JM2Cq5020469 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Sat, 20 Apr 2002 00:02:17 +0200 (CEST) Message-ID: <3CC093E3.7030906@veidit.net> Date: Sat, 20 Apr 2002 00:02:11 +0200 From: John Angelmo User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.9) Gecko/20020414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway Cc: current Subject: Re: Xfree86-4 problem References: <3CC07A63.4050406@veidit.net> <20020419134919.A49216@xor.obsecurity.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Kris Kennaway wrote: > On Fri, Apr 19, 2002 at 10:13:23PM +0200, John Angelmo wrote: > >>After yesterdays new build I found a problem >>Xfree86-4 can't start as regular user (exept root) > > > Read the fine message you got at install-time and install the wrapper > port. > > Kris Wrapper is installed it allways has been, X starts but not the windowmanager (fluxbox or tmw) /John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 19 17:28:40 2002 Delivered-To: freebsd-current@freebsd.org Received: from mailsrv.otenet.gr (mailsrv.otenet.gr [195.170.0.5]) by hub.freebsd.org (Postfix) with ESMTP id 6E81E37B404 for ; Fri, 19 Apr 2002 17:28:34 -0700 (PDT) Received: from hades.hell.gr (patr530-a030.otenet.gr [212.205.215.30]) by mailsrv.otenet.gr (8.12.2/8.12.2) with ESMTP id g3K0SMX6006756; Sat, 20 Apr 2002 03:28:23 +0300 (EEST) Received: from hades.hell.gr (hades [127.0.0.1]) by hades.hell.gr (8.12.2/8.12.2) with ESMTP id g3K0SLNl002621; Sat, 20 Apr 2002 03:28:21 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from charon@localhost) by hades.hell.gr (8.12.2/8.12.2/Submit) id g3K0SI51002620; Sat, 20 Apr 2002 03:28:18 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Sat, 20 Apr 2002 03:28:18 +0300 From: Giorgos Keramidas To: Chad David Cc: current@FreeBSD.org Subject: Re: savecore Message-ID: <20020420002817.GD1464@hades.hell.gr> References: <20020419003134.A54078@colnta.acns.ab.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020419003134.A54078@colnta.acns.ab.ca> User-Agent: Mutt/1.3.28i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 2002-04-19 00:31, Chad David wrote: > Any comments / objections to these patches to savecore and friends? Since you asked ... :) > Index: savecore.8 > =================================================================== > +The > +.Nm savecore You can safely remove "savecore" from the .Nm arguments, since the macro will add it when given no arguments. (This occurs in several places below, too.) > +Print additional debugging information, including the details of the dump > +header to stdout. The following sounds a tiny bit better: +Print additional debugging information to standard output, +including the details of the dump header. > +The > +.Nm savecore > +command attempts to verify that a core image is valid by verifying it's > +header (magic number and version etc.). "its header". No apostrophe. You might also like to drop "and" in "(magic number, version, etc.)." > The ``#'' is the number from the first line of the file > .Ar directory Ns Pa /bounds , > -and it is incremented and stored back into the file each time > -.Nm > +and is incremented and stored back into the file each time > +.Nm savecore > successfully runs. Breaking the sentences, makes the whole thing easier to understand, and removes the need for the "and" joining those two parts: The ``#'' is the number from the first line of the file .Ar directory Ns Pa /bounds . It is incremented and stored back into the file each time .Nm runs successfully. > If > +.Nm savecore > +successfully saves the core dump, and the > +.Fl k > +option is not specific, the dump's header is cleared so that future s/specific/specified/ > static void > DoFile(const char *device) > { > struct kerneldumpheader kdhf, kdhl; > - char buf[BUFSIZ]; > + char buf[BUFSIZ * 64]; Is this multiplication really necessary? Was the original buf[BUFSIZ] size not adequate? Giorgos Keramidas FreeBSD Documentation Project keramida@{freebsd.org,ceid.upatras.gr} http://www.FreeBSD.org/docproj/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 19 18:17: 8 2002 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id 8F88937B417; Fri, 19 Apr 2002 18:16:47 -0700 (PDT) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.2/8.12.2) with ESMTP id g3K1GhiJ066557; Sat, 20 Apr 2002 05:16:45 +0400 (MSD) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.3/8.12.2/Submit) id g3K1Gd0t066556; Sat, 20 Apr 2002 05:16:40 +0400 (MSD) Date: Sat, 20 Apr 2002 05:16:35 +0400 From: "Andrey A. Chernov" To: current@freebsd.org, des@freebsd.org Subject: PAM & OpenSSH: two incorrect "last login" Message-ID: <20020420011633.GA66468@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.28i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I got this TWO last login lines with recent -current SSH+PAM: -------------------------- Last login: Sat Apr 20 04:50:45 from hermes.dialup.ru Last login: Sat Apr 20 04:56:06 2002 from hermes.dialup.ru Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994 ... -------------------------- The second one is semi-correct, excepting year not needed here. It is original SSH bug easy to fix, just print first 19 characters and not whole ctime() line in session.c But what about first one? Apparently it comes from pam_lastlog.so, but why there is \n in the middle? Looking at pam_lastlog.c sources I not find \n there. It seems it is inserted afterwards somehow. Notice the second \n after first lastlog line, it must not be there too. Please fix those two \n's. BTW, ONE lastlog line is enough. Please either remove pam_lastlog.so or comment "#ifndef USE_PAM" SSH one. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 19 18:22: 5 2002 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id 1A5BD37B419 for ; Fri, 19 Apr 2002 18:22:01 -0700 (PDT) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.2/8.12.2) with ESMTP id g3K1LliJ066610 for ; Sat, 20 Apr 2002 05:21:50 +0400 (MSD) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.3/8.12.2/Submit) id g3K1Lk6A066609 for current@freebsd.org; Sat, 20 Apr 2002 05:21:46 +0400 (MSD) Date: Sat, 20 Apr 2002 05:21:42 +0400 From: "Andrey A. Chernov" To: current@freebsd.org Subject: SSH: LOGIN_CAP limits & ~/.login.conf not processed now Message-ID: <20020420012140.GA66589@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.28i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Well, who damages LOGIN_CAP processing in sshd now? It not reads ~/.login_conf anymore and not sets LOGIN_CAP limits. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 19 19:43:20 2002 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id 2A23437B417; Fri, 19 Apr 2002 19:43:17 -0700 (PDT) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.2/8.12.2) with ESMTP id g3K2h6iJ097690; Sat, 20 Apr 2002 06:43:16 +0400 (MSD) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.3/8.12.2/Submit) id g3K2h53N097689; Sat, 20 Apr 2002 06:43:05 +0400 (MSD) Date: Sat, 20 Apr 2002 06:43:05 +0400 From: "Andrey A. Chernov" To: current@FreeBSD.ORG, green@FreeBSD.ORG Subject: Re: SSH: LOGIN_CAP limits & ~/.login.conf not processed now Message-ID: <20020420024304.GA95425@nagual.pp.ru> References: <20020420012140.GA66589@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020420012140.GA66589@nagual.pp.ru> User-Agent: Mutt/1.3.28i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Apr 20, 2002 at 05:21:42 +0400, Andrey A. Chernov wrote: > Well, who damages LOGIN_CAP processing in sshd now? It not reads > ~/.login_conf anymore and not sets LOGIN_CAP limits. I see parent environment seriously damaged in do_setusercontext() since not saved. I mean MAIL,BLOCKSIZE & FTP_PASSIVE_MODE variables, overwritten by /etc/login.conf Really any environment variable can be overwritten here, so please restore good old code which saves&restores parent environment before calling setusercontext(). do_setup_env() code is broken too because call setusercontext() which modify _current_ environment, and NOT child one. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 19 20: 3:12 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.acns.ab.ca (mail.acns.ab.ca [142.179.151.95]) by hub.freebsd.org (Postfix) with ESMTP id C666437B41F for ; Fri, 19 Apr 2002 20:02:55 -0700 (PDT) Received: from colnta.acns.ab.ca (colnta.acns.ab.ca [192.168.1.2]) by mail.acns.ab.ca (8.12.2/8.12.2) with ESMTP id g3K30j3S009622; Fri, 19 Apr 2002 21:00:45 -0600 (MDT) (envelope-from davidc@colnta.acns.ab.ca) Received: from colnta.acns.ab.ca (localhost [127.0.0.1]) by colnta.acns.ab.ca (8.12.2/8.11.3) with ESMTP id g3K30jsn087518; Fri, 19 Apr 2002 21:00:45 -0600 (MDT) (envelope-from davidc@colnta.acns.ab.ca) Received: (from davidc@localhost) by colnta.acns.ab.ca (8.12.2/8.12.2/Submit) id g3K30jue087517; Fri, 19 Apr 2002 21:00:45 -0600 (MDT) Date: Fri, 19 Apr 2002 21:00:45 -0600 From: Chad David To: Giorgos Keramidas Cc: current@FreeBSD.org Subject: Re: savecore Message-ID: <20020419210045.A87465@colnta.acns.ab.ca> Mail-Followup-To: Giorgos Keramidas , current@FreeBSD.org References: <20020419003134.A54078@colnta.acns.ab.ca> <20020420002817.GD1464@hades.hell.gr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020420002817.GD1464@hades.hell.gr>; from keramida@ceid.upatras.gr on Sat, Apr 20, 2002 at 03:28:18AM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Apr 20, 2002 at 03:28:18AM +0300, Giorgos Keramidas wrote: > On 2002-04-19 00:31, Chad David wrote: > > Any comments / objections to these patches to savecore and friends? > > Since you asked ... :) Yes, I did. > > > Index: savecore.8 > > =================================================================== > > > +The > > +.Nm savecore > > You can safely remove "savecore" from the .Nm arguments, > since the macro will add it when given no arguments. > (This occurs in several places below, too.) I am aware of that, but I prefer not to. I find it easier to read the raw page with the name in. Unless ru says otherwise I'm going to keep doing it that way :). > > > +Print additional debugging information, including the details of the dump > > +header to stdout. > > The following sounds a tiny bit better: > > +Print additional debugging information to standard output, > +including the details of the dump header. Works for me. > > > +The > > +.Nm savecore > > +command attempts to verify that a core image is valid by verifying it's > > +header (magic number and version etc.). > > "its header". No apostrophe. > You might also like to drop "and" in > "(magic number, version, etc.)." Ok. > > > The ``#'' is the number from the first line of the file > > .Ar directory Ns Pa /bounds , > > -and it is incremented and stored back into the file each time > > -.Nm > > +and is incremented and stored back into the file each time > > +.Nm savecore > > successfully runs. > > Breaking the sentences, makes the whole thing easier to understand, > and removes the need for the "and" joining those two parts: > > The ``#'' is the number from the first line of the file > .Ar directory Ns Pa /bounds . > It is incremented and stored back into the file each time > .Nm > runs successfully. That was taken directly from savecore.8 on -stable, but I do agree with you. > > > If > > +.Nm savecore > > +successfully saves the core dump, and the > > +.Fl k > > +option is not specific, the dump's header is cleared so that future > > s/specific/specified/ Yup. > > > static void > > DoFile(const char *device) > > { > > struct kerneldumpheader kdhf, kdhl; > > - char buf[BUFSIZ]; > > + char buf[BUFSIZ * 64]; > > Is this multiplication really necessary? > Was the original buf[BUFSIZ] size not adequate? Because on my test machine it saves me time waiting for a 512M dump to a somewhat slow disk. I didn't try to tune the value, I just increased it (I didn't think it was worth the effort). If somebody has a better number I'll use it :). I was actually hoping for a few more comments on the code, but thanks anyway ;). -- Chad David davidc@acns.ab.ca www.FreeBSD.org davidc@freebsd.org ACNS Inc. Calgary, Alberta Canada Fourthly, The constant breeders, beside the gain of eight shillings sterling per annum by the sale of their children, will be rid of the charge of maintaining them after the first year. - Johnathan Swift To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 19 20:57: 2 2002 Delivered-To: freebsd-current@freebsd.org Received: from smak.floondoon.com (12-235-41-54.client.attbi.com [12.235.41.54]) by hub.freebsd.org (Postfix) with ESMTP id C09EB37B405 for ; Fri, 19 Apr 2002 20:56:56 -0700 (PDT) Received: from sphynx (sphynx.floondoon.com. [192.168.235.15]) by smak.floondoon.com (8.11.6/8.11.6) with SMTP id g3K3caV45488; Fri, 19 Apr 2002 20:38:37 -0700 (PDT) (envelope-from james@floondoon.com) Message-ID: <008a01c1e81f$67220ec0$0feba8c0@sphynx> From: "James Satterfield" To: "John Angelmo" , "current" References: <3CC07A63.4050406@veidit.net> Subject: Re: Xfree86-4 problem Date: Fri, 19 Apr 2002 20:56:50 -0700 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 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've found that wrapper needs to be updated with XFree86-4. James. ----- Original Message ----- From: "John Angelmo" To: "current" Sent: Friday, April 19, 2002 1:13 PM Subject: Xfree86-4 problem > After yesterdays new build I found a problem > Xfree86-4 can't start as regular user (exept root) > > this is the error message I get: > > AUDIT: Fri Apr 19 22:09:13 2002: 16472 XFree86: client 1 rejected from > local host > AUDIT: Fri Apr 19 22:09:15 2002: 16472 XFree86: client 1 rejected from > local host > AUDIT: Fri Apr 19 22:09:17 2002: 16472 XFree86: client 1 rejected from > local host > AUDIT: Fri Apr 19 22:09:19 2002: 16472 XFree86: client 1 rejected from > local host > > > Does anyone have any idea? > > /John > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Apr 19 21:43:15 2002 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id C585B37B41D; Fri, 19 Apr 2002 21:43:11 -0700 (PDT) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.2/8.12.2) with ESMTP id g3K4h7iJ001156; Sat, 20 Apr 2002 08:43:10 +0400 (MSD) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.3/8.12.2/Submit) id g3K4h7o7001155; Sat, 20 Apr 2002 08:43:07 +0400 (MSD) Date: Sat, 20 Apr 2002 08:43:06 +0400 From: "Andrey A. Chernov" To: current@FreeBSD.ORG, green@FreeBSD.ORG Subject: Re: SSH: LOGIN_CAP limits & ~/.login.conf not processed now Message-ID: <20020420044306.GA1132@nagual.pp.ru> References: <20020420012140.GA66589@nagual.pp.ru> <20020420024304.GA95425@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020420024304.GA95425@nagual.pp.ru> User-Agent: Mutt/1.3.28i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Apr 20, 2002 at 06:43:05 +0400, Andrey A. Chernov wrote: > On Sat, Apr 20, 2002 at 05:21:42 +0400, Andrey A. Chernov wrote: > > Well, who damages LOGIN_CAP processing in sshd now? It not reads > > ~/.login_conf anymore and not sets LOGIN_CAP limits. > > I see parent environment seriously damaged in do_setusercontext() since > not saved. I mean MAIL,BLOCKSIZE & FTP_PASSIVE_MODE variables, > overwritten by /etc/login.conf Really any environment variable can be > overwritten here, so please restore good old code which saves&restores > parent environment before calling setusercontext(). do_setup_env() code is > broken too because call setusercontext() which modify _current_ > environment, and NOT child one. NOTE: I just commit the fix, see session.c commit log for detailed explanation. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 20 3:20:21 2002 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id 6E43137B41B for ; Sat, 20 Apr 2002 03:19:59 -0700 (PDT) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.2/8.12.2) with ESMTP id g3KAJuiJ003643 for ; Sat, 20 Apr 2002 14:19:58 +0400 (MSD) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.3/8.12.2/Submit) id g3KAJuLa003642 for current@freebsd.org; Sat, 20 Apr 2002 14:19:56 +0400 (MSD) Date: Sat, 20 Apr 2002 14:19:55 +0400 From: "Andrey A. Chernov" To: current@freebsd.org Subject: SSH: zombie appearse probably related to PAM Message-ID: <20020420101955.GA3631@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.28i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG WARNING: this bug present even _before_ my changes, tested with session.c v1.22 It happens only with 'localhost' and not in remote case. To reproduce it, call: ssh localhost login normally and then exit. At exit you'll see following message on console (or /var/log/messages): sshd[]: error: session_by_pid: unknown pid This is harmless, because this is pid of sshd zombie, but how this zombie appearse? Why it not happens with remote login? I suspect that PAM code can be involved here, but I am not sure... -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 20 3:39:24 2002 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id 0F8AA37B41B; Sat, 20 Apr 2002 03:39:21 -0700 (PDT) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.2/8.12.2) with ESMTP id g3KAd8iJ003870; Sat, 20 Apr 2002 14:39:13 +0400 (MSD) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.3/8.12.2/Submit) id g3KAd79r003869; Sat, 20 Apr 2002 14:39:07 +0400 (MSD) Date: Sat, 20 Apr 2002 14:39:06 +0400 From: "Andrey A. Chernov" To: current@freebsd.org, des@freebsd.org Subject: SSH: login record not present (PAM) Message-ID: <20020420103905.GA3850@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.28i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG WARNING: this bug appearse even _before_ my changes, I test it with session.c v1.22 When you log in, locally or remotely, login record not added, logged user is invisible for 'w' or 'who'. Of course, !use_login assumed. Yes, I have updated /etc/pam.d Please fix it. Perhaps it somehow related with zombie problem I report before. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 20 4:47: 1 2002 Delivered-To: freebsd-current@freebsd.org Received: from mailsrv.otenet.gr (mailsrv.otenet.gr [195.170.0.5]) by hub.freebsd.org (Postfix) with ESMTP id 4D7B537B400 for ; Sat, 20 Apr 2002 04:46:53 -0700 (PDT) Received: from hades.hell.gr (patr530-a217.otenet.gr [212.205.215.217]) by mailsrv.otenet.gr (8.12.2/8.12.2) with ESMTP id g3KBke5q014987; Sat, 20 Apr 2002 14:46:41 +0300 (EEST) Received: from hades.hell.gr (hades [127.0.0.1]) by hades.hell.gr (8.12.2/8.12.2) with ESMTP id g3KBkxNl008859; Sat, 20 Apr 2002 14:46:59 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from charon@localhost) by hades.hell.gr (8.12.2/8.12.2/Submit) id g3KBkvpx008858; Sat, 20 Apr 2002 14:46:57 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Sat, 20 Apr 2002 14:46:56 +0300 From: Giorgos Keramidas To: Chad David Cc: current@FreeBSD.ORG Subject: Re: savecore Message-ID: <20020420114656.GA8171@hades.hell.gr> References: <20020419003134.A54078@colnta.acns.ab.ca> <20020420002817.GD1464@hades.hell.gr> <20020419210045.A87465@colnta.acns.ab.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020419210045.A87465@colnta.acns.ab.ca> User-Agent: Mutt/1.3.28i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 2002-04-19 21:00, Chad David wrote: > I was actually hoping for a few more comments on the code, but thanks > anyway ;). Nah... Most of the code looks OK, as far as I can tell. I'm not a C guru or something similar, but it is fine. Style things like the two below were what I had written about it in my original mail, but thought they weren't worth the time. What I had written and then removed from the previous message was: + errno = 0; + ret = (int)strtol(buf, NULL, 10); + if (ret == 0) + if (errno == EINVAL || errno == ERANGE) + warnx("invalid value found in bounds, using 0"); I do have to admit seeing two if-statements is a bit weird :) if (ret == 0 && (...)), perhaps? @@ -123,7 +165,20 @@ - goto closefd; + if (force) { ... + } else { + goto closefd; + } } I have to admit I'd write this as: if (force == 0) goto closefd; /* rest of the code with one less indentation level */ But as I said, the code is fine already. But if you do commit the (BUFSIZ * 64) change I mentioned in the earlier post, please do not forget to mention the change and why it's done. If it makes dumps faster to extract, without breaking the existing savecore behavior, it's perfect :) Giorgos Keramidas FreeBSD Documentation Project keramida@{freebsd.org,ceid.upatras.gr} http://www.FreeBSD.org/docproj/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 20 5:18:26 2002 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 58DB737B405 for ; Sat, 20 Apr 2002 05:18:22 -0700 (PDT) Received: by flood.ping.uio.no (Postfix, from userid 2602) id C4BB95309; Sat, 20 Apr 2002 14:18:17 +0200 (CEST) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: "Andrey A. Chernov" Cc: current@freebsd.org Subject: Re: SSH: login record not present (PAM) References: <20020420103905.GA3850@nagual.pp.ru> From: Dag-Erling Smorgrav Date: 20 Apr 2002 14:18:16 +0200 In-Reply-To: <20020420103905.GA3850@nagual.pp.ru> Message-ID: Lines: 11 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Andrey A. Chernov" writes: > When you log in, locally or remotely, login record not added, logged user > is invisible for 'w' or 'who'. Of course, !use_login assumed. Yes, I have > updated /etc/pam.d > Please fix it. I postd a patch to -current yesterday. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 20 8:12:30 2002 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id EDE5137B421; Sat, 20 Apr 2002 08:12:23 -0700 (PDT) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 626D3534C; Sat, 20 Apr 2002 17:12:22 +0200 (CEST) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: "Andrey A. Chernov" Cc: current@FreeBSD.ORG, green@FreeBSD.ORG Subject: Re: SSH: LOGIN_CAP limits & ~/.login.conf not processed now References: <20020420012140.GA66589@nagual.pp.ru> <20020420024304.GA95425@nagual.pp.ru> <20020420044306.GA1132@nagual.pp.ru> From: Dag-Erling Smorgrav Date: 20 Apr 2002 17:12:21 +0200 In-Reply-To: <20020420044306.GA1132@nagual.pp.ru> Message-ID: Lines: 9 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Andrey A. Chernov" writes: > NOTE: I just commit the fix, see session.c commit log for detailed > explanation. Andrey, in the future please *submit patches for review*. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 20 8:28:57 2002 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id 1D78837B420; Sat, 20 Apr 2002 08:28:39 -0700 (PDT) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.2/8.12.2) with ESMTP id g3KFSaiJ006287; Sat, 20 Apr 2002 19:28:37 +0400 (MSD) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.3/8.12.2/Submit) id g3KFSZRR006286; Sat, 20 Apr 2002 19:28:35 +0400 (MSD) Date: Sat, 20 Apr 2002 19:28:34 +0400 From: "Andrey A. Chernov" To: Dag-Erling Smorgrav Cc: current@FreeBSD.ORG, green@FreeBSD.ORG Subject: Re: SSH: LOGIN_CAP limits & ~/.login.conf not processed now Message-ID: <20020420152834.GA6166@nagual.pp.ru> References: <20020420012140.GA66589@nagual.pp.ru> <20020420024304.GA95425@nagual.pp.ru> <20020420044306.GA1132@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.28i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Apr 20, 2002 at 17:12:21 +0200, Dag-Erling Smorgrav wrote: > "Andrey A. Chernov" writes: > > NOTE: I just commit the fix, see session.c commit log for detailed > > explanation. > > Andrey, in the future please *submit patches for review*. This case is special - that was old code written by me and present in all previous versions of OpenSSH we have, but lost in merge very recently. The real subject is improper merge. Those people who does merge not submit patches for my review. I start alarming probably a bit late since I don't have machine suitable for recent -current until now. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 20 8:34:23 2002 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id AE15F37B419; Sat, 20 Apr 2002 08:34:17 -0700 (PDT) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.2/8.12.2) with ESMTP id g3KFYFiJ006388; Sat, 20 Apr 2002 19:34:16 +0400 (MSD) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.3/8.12.2/Submit) id g3KFYEjM006387; Sat, 20 Apr 2002 19:34:14 +0400 (MSD) Date: Sat, 20 Apr 2002 19:34:14 +0400 From: "Andrey A. Chernov" To: current@FreeBSD.ORG, des@FreeBSD.ORG Subject: Re: SSH: login record not present (PAM) Message-ID: <20020420153414.GC6166@nagual.pp.ru> References: <20020420103905.GA3850@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020420103905.GA3850@nagual.pp.ru> User-Agent: Mutt/1.3.28i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Apr 20, 2002 at 14:39:06 +0400, Andrey A. Chernov wrote: > WARNING: this bug appearse even _before_ my changes, I test it with > session.c v1.22 > > When you log in, locally or remotely, login record not added, logged user > is invisible for 'w' or 'who'. Of course, !use_login assumed. Yes, I have > updated /etc/pam.d > Please fix it. Thanks, your recent commit fix it. This one closed. > Perhaps it somehow related with zombie problem I report before. Really, not related. That one still there. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 20 8:35:19 2002 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id 0705937B41A; Sat, 20 Apr 2002 08:35:12 -0700 (PDT) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.2/8.12.2) with ESMTP id g3KFZ9iJ006408; Sat, 20 Apr 2002 19:35:11 +0400 (MSD) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.3/8.12.2/Submit) id g3KFZ93Z006407; Sat, 20 Apr 2002 19:35:09 +0400 (MSD) Date: Sat, 20 Apr 2002 19:35:09 +0400 From: "Andrey A. Chernov" To: current@FreeBSD.ORG, des@FreeBSD.ORG Subject: Re: PAM & OpenSSH: two incorrect "last login" Message-ID: <20020420153509.GD6166@nagual.pp.ru> References: <20020420011633.GA66468@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020420011633.GA66468@nagual.pp.ru> User-Agent: Mutt/1.3.28i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This bug still present too. Please handle it somehow, it is clearly comes from PAM. On Sat, Apr 20, 2002 at 05:16:35 +0400, Andrey A. Chernov wrote: > I got this TWO last login lines with recent -current SSH+PAM: > > -------------------------- > Last login: Sat Apr 20 04:50:45 > from hermes.dialup.ru > > Last login: Sat Apr 20 04:56:06 2002 from hermes.dialup.ru > Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994 > ... > -------------------------- > > The second one is semi-correct, excepting year not needed here. It is > original SSH bug easy to fix, just print first 19 characters and not whole > ctime() line in session.c > > But what about first one? Apparently it comes from pam_lastlog.so, but why > there is \n in the middle? Looking at pam_lastlog.c sources I not find \n > there. It seems it is inserted afterwards somehow. Notice the second \n > after first lastlog line, it must not be there too. Please fix those > two \n's. > > BTW, ONE lastlog line is enough. Please either remove pam_lastlog.so or > comment "#ifndef USE_PAM" SSH one. > > -- > Andrey A. Chernov > http://ache.pp.ru/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 20 8:36:54 2002 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id C647137B434; Sat, 20 Apr 2002 08:36:26 -0700 (PDT) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.2/8.12.2) with ESMTP id g3KFaOiJ006422; Sat, 20 Apr 2002 19:36:25 +0400 (MSD) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.3/8.12.2/Submit) id g3KFaOXo006421; Sat, 20 Apr 2002 19:36:24 +0400 (MSD) Date: Sat, 20 Apr 2002 19:36:24 +0400 From: "Andrey A. Chernov" To: current@FreeBSD.ORG Cc: des@FreeBSD.ORG Subject: Re: SSH: zombie appearse probably related to PAM Message-ID: <20020420153623.GE6166@nagual.pp.ru> References: <20020420101955.GA3631@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020420101955.GA3631@nagual.pp.ru> User-Agent: Mutt/1.3.28i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This one still present, libutil/login.c commit not fix it. On Sat, Apr 20, 2002 at 14:19:55 +0400, Andrey A. Chernov wrote: > WARNING: this bug present even _before_ my changes, tested with session.c > v1.22 > > It happens only with 'localhost' and not in remote case. To > reproduce it, call: > ssh localhost > login normally and then exit. At exit you'll see following message on > console (or /var/log/messages): > > sshd[]: error: session_by_pid: unknown pid > > This is harmless, because this is pid of sshd zombie, but > how this zombie appearse? Why it not happens with remote login? > I suspect that PAM code can be involved here, but I am not sure... -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 20 9: 2: 2 2002 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id BAE8C37B400 for ; Sat, 20 Apr 2002 09:02:00 -0700 (PDT) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 588A7530B; Sat, 20 Apr 2002 18:01:59 +0200 (CEST) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: "Andrey A. Chernov" Cc: current@FreeBSD.ORG Subject: Re: PAM & OpenSSH: two incorrect "last login" References: <20020420011633.GA66468@nagual.pp.ru> <20020420153509.GD6166@nagual.pp.ru> From: Dag-Erling Smorgrav Date: 20 Apr 2002 18:01:58 +0200 In-Reply-To: <20020420153509.GD6166@nagual.pp.ru> Message-ID: Lines: 11 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Andrey A. Chernov" writes: > This bug still present too. Please handle it somehow, it is clearly comes > from PAM. Andrey, it's quite possible that you're Superman, but I'm not, so GIVE ME A BREAK. I'm doing this one step at a time. It'll happen much faster if you stay off my back. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 20 9: 6:13 2002 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id 252B837B41C for ; Sat, 20 Apr 2002 09:06:03 -0700 (PDT) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.2/8.12.2) with ESMTP id g3KG60iJ006843; Sat, 20 Apr 2002 20:06:02 +0400 (MSD) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.3/8.12.2/Submit) id g3KG609W006842; Sat, 20 Apr 2002 20:06:00 +0400 (MSD) Date: Sat, 20 Apr 2002 20:06:00 +0400 From: "Andrey A. Chernov" To: Dag-Erling Smorgrav Cc: current@FreeBSD.ORG Subject: Re: PAM & OpenSSH: two incorrect "last login" Message-ID: <20020420160559.GA6816@nagual.pp.ru> References: <20020420011633.GA66468@nagual.pp.ru> <20020420153509.GD6166@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.28i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Apr 20, 2002 at 18:01:58 +0200, Dag-Erling Smorgrav wrote: > "Andrey A. Chernov" writes: > > This bug still present too. Please handle it somehow, it is clearly comes > > from PAM. > > Andrey, it's quite possible that you're Superman, but I'm not, so GIVE > ME A BREAK. I'm doing this one step at a time. It'll happen much > faster if you stay off my back. Sorry Dag-Erling, I not mean word 'immediately' at all, I just want to be sure that this one not forgotten in whole discussion. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 20 9:10:59 2002 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 2DB4937B41B for ; Sat, 20 Apr 2002 09:10:53 -0700 (PDT) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 8F9705309; Sat, 20 Apr 2002 18:10:51 +0200 (CEST) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: "Andrey A. Chernov" Cc: current@freebsd.org Subject: Re: PAM & OpenSSH: two incorrect "last login" References: <20020420011633.GA66468@nagual.pp.ru> From: Dag-Erling Smorgrav Date: 20 Apr 2002 18:10:50 +0200 In-Reply-To: <20020420011633.GA66468@nagual.pp.ru> Message-ID: Lines: 11 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --=-=-= "Andrey A. Chernov" writes: > I got this TWO last login lines with recent -current SSH+PAM: See attached patch. DES -- Dag-Erling Smorgrav - des@ofug.org --=-=-= Content-Type: text/x-patch Content-Disposition: attachment; filename=lastlog.diff ==== //depot/user/des/pam/lib/libpam/modules/pam_lastlog/pam_lastlog.c#9 - /usr/src/lib/libpam/modules/pam_lastlog/pam_lastlog.c ==== --- /tmp/tmp.23049.0 Sat Apr 20 18:09:14 2002 +++ /usr/src/lib/libpam/modules/pam_lastlog/pam_lastlog.c Sat Apr 20 18:08:29 2002 @@ -108,15 +108,14 @@ if (lseek(fd, llpos, L_SET) != llpos) goto file_err; if ((flags & PAM_SILENT) == 0) { - if (read(fd, &ll, sizeof(ll)) == sizeof(ll) && - ll.ll_time != 0) { - pam_info(pamh, "Last login: %.*s ", 24 - 5, - ctime(&ll.ll_time)); + if (read(fd, &ll, sizeof ll) == sizeof ll && ll.ll_time != 0) { if (*ll.ll_host != '\0') - pam_info(pamh, "from %.*s\n", + pam_info(pamh, "Last login: %.*s from %.*s", + 24 - 5, ctime(&ll.ll_time), (int)sizeof(ll.ll_host), ll.ll_host); else - pam_info(pamh, "on %.*s\n", + pam_info(pamh, "Last login: %.*s on %.*s", + 24 - 5, ctime(&ll.ll_time), (int)sizeof(ll.ll_line), ll.ll_line); } if (lseek(fd, llpos, L_SET) != llpos) ==== //depot/user/des/pam/crypto/openssh/session.c#6 - /usr/src/crypto/openssh/session.c ==== --- /tmp/tmp.23049.1 Sat Apr 20 18:09:15 2002 +++ /usr/src/crypto/openssh/session.c Sat Apr 20 18:04:43 2002 @@ -647,6 +647,7 @@ } #endif +#ifndef USE_PAM /* Get the time and hostname when the user last logged in. */ if (options.print_lastlog) { hostname[0] = '\0'; @@ -654,7 +655,6 @@ hostname, sizeof(hostname)); } -#ifndef USE_PAM /* Record that there was a login on that tty from the remote host. */ record_login(pid, s->tty, pw->pw_name, pw->pw_uid, get_remote_name_or_ip(utmp_len, options.verify_reverse_mapping), --=-=-=-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 20 9:20:23 2002 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id DA2BD37B400 for ; Sat, 20 Apr 2002 09:20:18 -0700 (PDT) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.2/8.12.2) with ESMTP id g3KGK9iJ006996; Sat, 20 Apr 2002 20:20:13 +0400 (MSD) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.3/8.12.2/Submit) id g3KGK5aU006994; Sat, 20 Apr 2002 20:20:06 +0400 (MSD) Date: Sat, 20 Apr 2002 20:20:01 +0400 From: "Andrey A. Chernov" To: Dag-Erling Smorgrav Cc: current@freebsd.org Subject: Re: PAM & OpenSSH: two incorrect "last login" Message-ID: <20020420162000.GA6972@nagual.pp.ru> References: <20020420011633.GA66468@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.28i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Apr 20, 2002 at 18:10:50 +0200, Dag-Erling Smorgrav wrote: > "Andrey A. Chernov" writes: > > I got this TWO last login lines with recent -current SSH+PAM: > > See attached patch. It goes better and worse in the same time :-) Last login: Sat Apr 20 20:16:55 on ttyv4 Last login: Sun Apr 14 05:44:16 1991 Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT (HERMES) #2: Sat Apr 20 13:06:00 MSD 2002 Newlines are gone, but see second line from back 1991 (garbadge on the stack of 'last_login_time' variable). -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 20 9:31:33 2002 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id BBAB337B41F for ; Sat, 20 Apr 2002 09:31:30 -0700 (PDT) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.2/8.12.2) with ESMTP id g3KGVOiJ007114; Sat, 20 Apr 2002 20:31:26 +0400 (MSD) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.3/8.12.2/Submit) id g3KGVMqJ007113; Sat, 20 Apr 2002 20:31:22 +0400 (MSD) Date: Sat, 20 Apr 2002 20:31:20 +0400 From: "Andrey A. Chernov" To: Dag-Erling Smorgrav Cc: current@FreeBSD.ORG Subject: Re: PAM & OpenSSH: two incorrect "last login" Message-ID: <20020420163119.GA7056@nagual.pp.ru> References: <20020420011633.GA66468@nagual.pp.ru> <20020420162000.GA6972@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020420162000.GA6972@nagual.pp.ru> User-Agent: Mutt/1.3.28i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Apr 20, 2002 at 20:20:01 +0400, Andrey A. Chernov wrote: > > Newlines are gone, but see second line from back 1991 (garbadge on the > stack of 'last_login_time' variable). BTW, please notice that printing this line is very conditionalized in OpenSSH: options.print_lastlog command == NULL !options.use_login !check_quietlogin(s, command) are checked. But in your variant it seems that only !check_quietlogin(s, command) checked (or, maybe it printed even unconditionally?) I am not sure here, it is internal PAM details. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 20 12:55:34 2002 Delivered-To: freebsd-current@freebsd.org Received: from beast.freebsd.org (beast.FreeBSD.org [216.136.204.28]) by hub.freebsd.org (Postfix) with ESMTP id B0D3037B41D for ; Sat, 20 Apr 2002 12:55:26 -0700 (PDT) Received: from beast.freebsd.org (localhost [127.0.0.1]) by beast.freebsd.org (8.12.2/8.12.2) with ESMTP id g3KJtQnU083106 for ; Sat, 20 Apr 2002 12:55:26 -0700 (PDT) (envelope-from des@beast.freebsd.org) Received: (from des@localhost) by beast.freebsd.org (8.12.2/8.12.2/Submit) id g3KJtQHp083104 for current@freebsd.org; Sat, 20 Apr 2002 12:55:26 -0700 (PDT) Date: Sat, 20 Apr 2002 12:55:26 -0700 (PDT) From: Dag-Erling Smorgrav Message-Id: <200204201955.g3KJtQHp083104@beast.freebsd.org> To: current@freebsd.org Subject: alpha tinderbox failure Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ===> usr.bin/enigma ===> usr.bin/env ===> usr.bin/expand ===> usr.bin/false ===> usr.bin/fetch ===> usr.bin/file ===> usr.bin/file2c ===> usr.bin/find ===> usr.bin/finger ===> usr.bin/fmt ===> usr.bin/fold ===> usr.bin/from ===> usr.bin/fstat In file included from /.amd_mnt/freefall/host/d/home/des/tinderbox/src/usr.bin/fstat/fstat.c:69: /tmp/des/obj/alpha/.amd_mnt/freefall/host/d/home/des/tinderbox/src/alpha/usr/include/fs/devfs/devfs.h:63: warning: parameter names (without types) in function declaration /tmp/des/obj/alpha/.amd_mnt/freefall/host/d/home/des/tinderbox/src/alpha/usr/include/fs/devfs/devfs.h:63: warning: data definition has no type or storage class /.amd_mnt/freefall/host/d/home/des/tinderbox/src/usr.bin/fstat/fstat.c: In function `devfs_filestat': /.amd_mnt/freefall/host/d/home/des/tinderbox/src/usr.bin/fstat/fstat.c:610: warning: cast from pointer to integer of different size ===> usr.bin/fsync ===> usr.bin/ftp /.amd_mnt/freefall/host/d/home/des/tinderbox/src/usr.bin/ftp/../../contrib/lukemftp/src/cmds.c: In function `fget': /.amd_mnt/freefall/host/d/home/des/tinderbox/src/usr.bin/ftp/../../contrib/lukemftp/src/cmds.c:717: warning: assignment makes pointer from integer without a cast /.amd_mnt/freefall/host/d/home/des/tinderbox/src/usr.bin/ftp/../../contrib/lukemftp/src/fetch.c: In function `fetch_url': /.amd_mnt/freefall/host/d/home/des/tinderbox/src/usr.bin/ftp/../../contrib/lukemftp/src/fetch.c:749: warning: assignment makes pointer from integer without a cast /.amd_mnt/freefall/host/d/home/des/tinderbox/src/usr.bin/ftp/../../contrib/lukemftp/src/fetch.c:772: warning: assignment makes pointer from integer without a cast ===> usr.bin/gencat ===> usr.bin/getopt ===> usr.bin/gprof /.amd_mnt/freefall/host/d/home/des/tinderbox/src/usr.bin/gprof/gprof.c: In function `main': /.amd_mnt/freefall/host/d/home/des/tinderbox/src/usr.bin/gprof/gprof.c:163: warning: type mismatch in implicit declaration for built-in function `strlen' /.amd_mnt/freefall/host/d/home/des/tinderbox/src/usr.bin/gprof/gprof.c:164: warning: type mismatch in implicit declaration for built-in function `strcpy' /.amd_mnt/freefall/host/d/home/des/tinderbox/src/usr.bin/gprof/kernel.c: In function `kernel_getnfile': /.amd_mnt/freefall/host/d/home/des/tinderbox/src/usr.bin/gprof/kernel.c:41: warning: type mismatch in implicit declaration for built-in function `strlen' ===> usr.bin/head ===> usr.bin/hesinfo ===> usr.bin/hexdump ===> usr.bin/id ===> usr.bin/indent ===> usr.bin/ipcrm ===> usr.bin/ipcs ===> usr.bin/join ===> usr.bin/jot ===> usr.bin/kdump In file included from ioctl.c:76: /tmp/des/obj/alpha/.amd_mnt/freefall/host/d/home/des/tinderbox/src/alpha/usr/include/sys/memrange.h:19: warning: `MDF_ACTIVE' redefined /tmp/des/obj/alpha/.amd_mnt/freefall/host/d/home/des/tinderbox/src/alpha/usr/include/pccard/cardinfo.h:115: warning: this is the location of the previous definition ===> usr.bin/kenv ===> usr.bin/keylogin ===> usr.bin/keylogout ===> usr.bin/killall ===> usr.bin/ktrace ===> usr.bin/ktrdump ===> usr.bin/lam ===> usr.bin/last ===> usr.bin/lastcomm ===> usr.bin/ldd /.amd_mnt/freefall/host/d/home/des/tinderbox/src/usr.bin/ldd/ldd.c: In function `main': /.amd_mnt/freefall/host/d/home/des/tinderbox/src/usr.bin/ldd/ldd.c:141: warning: implicit declaration of function `ntohl' ===> usr.bin/leave ===> usr.bin/less ===> usr.bin/lessecho ===> usr.bin/lesskey ===> usr.bin/lex ===> usr.bin/lex/lib ===> usr.bin/lex/lib ===> usr.bin/limits ===> usr.bin/locate ===> usr.bin/locate/bigram ===> usr.bin/locate/code ===> usr.bin/locate/locate ===> usr.bin/lock ===> usr.bin/lockf ===> usr.bin/logger ===> usr.bin/login ===> usr.bin/logname ===> usr.bin/look ===> usr.bin/lorder ===> usr.bin/lsvfs ===> usr.bin/m4 {standard input}: Assembler messages: {standard input}:5: Warning: unterminated string; newline inserted {standard input}:6: Warning: unterminated string; newline inserted cc1: warnings being treated as errors /.amd_mnt/freefall/host/d/home/des/tinderbox/src/usr.bin/m4/gnum4.c: In function `add_sub': /.amd_mnt/freefall/host/d/home/des/tinderbox/src/usr.bin/m4/gnum4.c:282: warning: int format, different type arg (arg 2) *** Error code 1 Stop in /.amd_mnt/freefall/host/d/home/des/tinderbox/src/usr.bin/m4. *** Error code 1 Stop in /.amd_mnt/freefall/host/d/home/des/tinderbox/src/usr.bin. *** Error code 1 Stop in /.amd_mnt/freefall/host/d/home/des/tinderbox/src. *** Error code 1 Stop in /.amd_mnt/freefall/host/d/home/des/tinderbox/src. *** Error code 1 Stop in /.amd_mnt/freefall/host/d/home/des/tinderbox/src. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 20 13:34:38 2002 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-165-226-18.dsl.lsan03.pacbell.net [64.165.226.18]) by hub.freebsd.org (Postfix) with ESMTP id B074437B419 for ; Sat, 20 Apr 2002 13:34:16 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 0E45066CFD; Sat, 20 Apr 2002 13:34:15 -0700 (PDT) Date: Sat, 20 Apr 2002 13:34:15 -0700 From: Kris Kennaway To: John Angelmo Cc: Kris Kennaway , current Subject: Re: Xfree86-4 problem Message-ID: <20020420133415.A96463@xor.obsecurity.org> References: <3CC07A63.4050406@veidit.net> <20020419134919.A49216@xor.obsecurity.org> <3CC093E3.7030906@veidit.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="cWoXeonUoKmBZSoM" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <3CC093E3.7030906@veidit.net>; from john@veidit.net on Sat, Apr 20, 2002 at 12:02:11AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --cWoXeonUoKmBZSoM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Apr 20, 2002 at 12:02:11AM +0200, John Angelmo wrote: > Kris Kennaway wrote: > > On Fri, Apr 19, 2002 at 10:13:23PM +0200, John Angelmo wrote: > >=20 > >>After yesterdays new build I found a problem > >>Xfree86-4 can't start as regular user (exept root) > >=20 > >=20 > > Read the fine message you got at install-time and install the wrapper > > port. > >=20 > > Kris >=20 > Wrapper is installed >=20 > it allways has been, X starts but not the windowmanager (fluxbox or tmw) Okay, well that's not what you said, is it? :-) Please post the exact error messages. Kris --cWoXeonUoKmBZSoM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8wdDHWry0BWjoQKURAtjHAKCw4WMRLqcbYaI2Lg5lfmlTesKg9QCg2zE6 Ztam1dCAJIvn3BySsnc5jqM= =5GCH -----END PGP SIGNATURE----- --cWoXeonUoKmBZSoM-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 20 13:35:45 2002 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-165-226-18.dsl.lsan03.pacbell.net [64.165.226.18]) by hub.freebsd.org (Postfix) with ESMTP id 9011137B48E for ; Sat, 20 Apr 2002 13:35:32 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 3018666C8C; Sat, 20 Apr 2002 13:35:32 -0700 (PDT) Date: Sat, 20 Apr 2002 13:35:32 -0700 From: Kris Kennaway To: James Satterfield Cc: John Angelmo , current Subject: Re: Xfree86-4 problem Message-ID: <20020420133532.B96463@xor.obsecurity.org> References: <3CC07A63.4050406@veidit.net> <008a01c1e81f$67220ec0$0feba8c0@sphynx> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="xXmbgvnjoT4axfJE" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <008a01c1e81f$67220ec0$0feba8c0@sphynx>; from james@floondoon.com on Fri, Apr 19, 2002 at 08:56:50PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --xXmbgvnjoT4axfJE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Apr 19, 2002 at 08:56:50PM -0700, James Satterfield wrote: > I've found that wrapper needs to be updated with XFree86-4. wrapper always needs to be rebuilt when you update X, yes. Kris --xXmbgvnjoT4axfJE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8wdETWry0BWjoQKURAhjoAKDRlB0sZ1RUsTSTplG0vXM8mEW/gQCfaF4m 2G5ak+0Mxh4PwyxVY7abf4U= =BW4K -----END PGP SIGNATURE----- --xXmbgvnjoT4axfJE-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 20 13:39:37 2002 Delivered-To: freebsd-current@freebsd.org Received: from h38n2fls34o1000.telia.com (h38n2fls34o1000.telia.com [213.64.210.38]) by hub.freebsd.org (Postfix) with ESMTP id 293E737B417 for ; Sat, 20 Apr 2002 13:39:34 -0700 (PDT) Received: from veidit.net ([192.168.1.99]) (authenticated bits=0) by h38n2fls34o1000.telia.com (8.12.2/8.12.2) with ESMTP id g3KKdMq5001465 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Sat, 20 Apr 2002 22:39:32 +0200 (CEST) Message-ID: <3CC1D1FA.1090107@veidit.net> Date: Sat, 20 Apr 2002 22:39:22 +0200 From: John Angelmo User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.9) Gecko/20020414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway Cc: current Subject: Re: Xfree86-4 problem References: <3CC07A63.4050406@veidit.net> <20020419134919.A49216@xor.obsecurity.org> <3CC093E3.7030906@veidit.net> <20020420133415.A96463@xor.obsecurity.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Kris Kennaway wrote: > On Sat, Apr 20, 2002 at 12:02:11AM +0200, John Angelmo wrote: > >>Kris Kennaway wrote: >> >>>On Fri, Apr 19, 2002 at 10:13:23PM +0200, John Angelmo wrote: >>> >>> >>>>After yesterdays new build I found a problem >>>>Xfree86-4 can't start as regular user (exept root) >>> >>> >>>Read the fine message you got at install-time and install the wrapper >>>port. >>> >>>Kris >> >>Wrapper is installed >> >>it allways has been, X starts but not the windowmanager (fluxbox or tmw) > > > Okay, well that's not what you said, is it? :-) > > Please post the exact error messages. > > Kris Well X starts but just to the gray area, no windowmanager starts and the error I get(after I have exited) is: AUDIT: Fri Apr 19 22:09:13 2002: 16472 XFree86: client 1 rejected from local host AUDIT: Fri Apr 19 22:09:15 2002: 16472 XFree86: client 1 rejected from local host AUDIT: Fri Apr 19 22:09:17 2002: 16472 XFree86: client 1 rejected from local host AUDIT: Fri Apr 19 22:09:19 2002: 16472 XFree86: client 1 rejected from local host /John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 20 14:35:42 2002 Delivered-To: freebsd-current@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 9575837B485 for ; Sat, 20 Apr 2002 14:34:56 -0700 (PDT) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id g3KLYDa00428; Sat, 20 Apr 2002 14:34:13 -0700 Date: Sat, 20 Apr 2002 14:34:13 -0700 From: Brooks Davis To: John Angelmo Cc: Kris Kennaway , current Subject: Re: Xfree86-4 problem Message-ID: <20020420143413.A29253@Odin.AC.HMC.Edu> References: <3CC07A63.4050406@veidit.net> <20020419134919.A49216@xor.obsecurity.org> <3CC093E3.7030906@veidit.net> <20020420133415.A96463@xor.obsecurity.org> <3CC1D1FA.1090107@veidit.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="jI8keyz6grp/JLjh" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <3CC1D1FA.1090107@veidit.net>; from john@veidit.net on Sat, Apr 20, 2002 at 10:39:22PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --jI8keyz6grp/JLjh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Apr 20, 2002 at 10:39:22PM +0200, John Angelmo wrote: > Well X starts but just to the gray area, no windowmanager starts and the= =20 > error I get(after I have exited) is: >=20 > AUDIT: Fri Apr 19 22:09:13 2002: 16472 XFree86: client 1 rejected from=20 > local host > AUDIT: Fri Apr 19 22:09:15 2002: 16472 XFree86: client 1 rejected from=20 > local host > AUDIT: Fri Apr 19 22:09:17 2002: 16472 XFree86: client 1 rejected from=20 > local host > AUDIT: Fri Apr 19 22:09:19 2002: 16472 XFree86: client 1 rejected from=20 > local host Do you have a hostname? I've found that X does this without one set. For the purposes of X, it doesn't appear to matter if it maps to an address or not. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --jI8keyz6grp/JLjh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8wd7RXY6L6fI4GtQRAviZAKDQuC38bc3Vh4Ckt40N3RcSmLe97gCgy8K6 rBwap0jw6JPZMQBQmKD78es= =uEuO -----END PGP SIGNATURE----- --jI8keyz6grp/JLjh-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 20 14:39:23 2002 Delivered-To: freebsd-current@freebsd.org Received: from orthanc.ab.ca (orthanc.ab.ca [216.123.203.186]) by hub.freebsd.org (Postfix) with ESMTP id 8CE2F37B416 for ; Sat, 20 Apr 2002 14:39:14 -0700 (PDT) Received: from orthanc.ab.ca (localhost.orthanc.ab.ca [127.0.0.1]) by orthanc.ab.ca (8.11.6/8.11.6) with ESMTP id g3KLdEJ80591 for ; Sat, 20 Apr 2002 15:39:14 -0600 (MDT) (envelope-from lyndon@orthanc.ab.ca) Message-Id: <200204202139.g3KLdEJ80591@orthanc.ab.ca> To: freebsd-current@freebsd.org Subject: Adding a 'bpf' group for /dev/bpf* Organization: The Frobozz Magic Homing Pigeon Company X-Mailer: mh-e 5.0.92; MH 6.8.4; Emacs 21.1 Date: Sat, 20 Apr 2002 15:39:14 -0600 From: Lyndon Nerenberg Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG For the benefit of packet sniffers and other things that only want read-only access to /dev/bpf*, what do people think of adding a 'bpf' group for those programs? This allows bpf devices to be read by programs running with an effective gid of 'bpf' instead of the current requirement for an effective user of root. I've been running this way on many of our servers for several months now, and things like snort, tcpdump, etc., are quite happy with it (under stable). --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 20 14:51:45 2002 Delivered-To: freebsd-current@freebsd.org Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by hub.freebsd.org (Postfix) with ESMTP id B22BF37B404 for ; Sat, 20 Apr 2002 14:51:40 -0700 (PDT) Received: from blossom.cjclark.org ([12.234.91.48]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020420215140.JUTN1901.rwcrmhc52.attbi.com@blossom.cjclark.org>; Sat, 20 Apr 2002 21:51:40 +0000 Received: (from cjc@localhost) by blossom.cjclark.org (8.11.6/8.11.6) id g3KLpeh77663; Sat, 20 Apr 2002 14:51:40 -0700 (PDT) (envelope-from cjc) Date: Sat, 20 Apr 2002 14:51:39 -0700 From: "Crist J. Clark" To: Lyndon Nerenberg Cc: freebsd-current@FreeBSD.ORG Subject: Re: Adding a 'bpf' group for /dev/bpf* Message-ID: <20020420145139.D76898@blossom.cjclark.org> References: <200204202139.g3KLdEJ80591@orthanc.ab.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200204202139.g3KLdEJ80591@orthanc.ab.ca>; from lyndon@orthanc.ab.ca on Sat, Apr 20, 2002 at 03:39:14PM -0600 X-URL: http://people.freebsd.org/~cjc/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Apr 20, 2002 at 03:39:14PM -0600, Lyndon Nerenberg wrote: > For the benefit of packet sniffers and other things that only want > read-only access to /dev/bpf*, what do people think of adding a 'bpf' > group for those programs? This allows bpf devices to be read by > programs running with an effective gid of 'bpf' instead of the current > requirement for an effective user of root. I've been running this way > on many of our servers for several months now, and things like snort, > tcpdump, etc., are quite happy with it (under stable). I do this a lot too on systems where it makes sense. But I'm not sure I understand what you are asking to be done. Is it asking too much of an administrator to do, # echo 'sniff:*:80:' >> /etc/group # chown root:sniff /dev/bpf* # chmod 640 /dev/bpf* To do the appropriate customizations? -- Crist J. Clark | cjclark@alum.mit.edu | cjclark@jhu.edu http://people.freebsd.org/~cjc/ | cjc@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 20 15: 2:18 2002 Delivered-To: freebsd-current@freebsd.org Received: from orthanc.ab.ca (orthanc.ab.ca [216.123.203.186]) by hub.freebsd.org (Postfix) with ESMTP id B7F4E37B417; Sat, 20 Apr 2002 15:02:13 -0700 (PDT) Received: from orthanc.ab.ca (localhost.orthanc.ab.ca [127.0.0.1]) by orthanc.ab.ca (8.11.6/8.11.6) with ESMTP id g3KM2DJ93468; Sat, 20 Apr 2002 16:02:13 -0600 (MDT) (envelope-from lyndon@orthanc.ab.ca) Message-Id: <200204202202.g3KM2DJ93468@orthanc.ab.ca> From: Lyndon Nerenberg Organization: The Frobozz Magic Homing Pigeon Company To: "Crist J. Clark" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Adding a 'bpf' group for /dev/bpf* In-reply-to: Your message of "Sat, 20 Apr 2002 14:51:39 PDT." <20020420145139.D76898@blossom.cjclark.org> X-Mailer: mh-e 5.0.92; MH 6.8.4; Emacs 21.1 Date: Sat, 20 Apr 2002 16:02:13 -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >>>>> "Crist" == Crist J Clark writes: Crist> I do this a lot too on systems where it makes sense. But I'm Crist> not sure I understand what you are asking to be done. Is it Crist> asking too much of an administrator to do, There are two ways to handle this. One is to modify the ports builds to conditionally create a 'bpf' group. This requires the ports all agree on the group, and I don't like the idea of a port install messing with permissions and ownerships of things in /dev (which aren't sticky across reboots, anyway). If the OS sets the access policy there cannot be any confusion. --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 20 15:11:55 2002 Delivered-To: freebsd-current@freebsd.org Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by hub.freebsd.org (Postfix) with ESMTP id E222237B400 for ; Sat, 20 Apr 2002 15:11:52 -0700 (PDT) Received: from blossom.cjclark.org ([12.234.91.48]) by rwcrmhc51.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020420221152.VJKZ1143.rwcrmhc51.attbi.com@blossom.cjclark.org>; Sat, 20 Apr 2002 22:11:52 +0000 Received: (from cjc@localhost) by blossom.cjclark.org (8.11.6/8.11.6) id g3KMBqw77762; Sat, 20 Apr 2002 15:11:52 -0700 (PDT) (envelope-from cjc) Date: Sat, 20 Apr 2002 15:11:52 -0700 From: "Crist J. Clark" To: Lyndon Nerenberg Cc: freebsd-current@FreeBSD.ORG Subject: Re: Adding a 'bpf' group for /dev/bpf* Message-ID: <20020420151152.E76898@blossom.cjclark.org> Reply-To: cjclark@alum.mit.edu References: <20020420145139.D76898@blossom.cjclark.org> <200204202202.g3KM2DJ93468@orthanc.ab.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200204202202.g3KM2DJ93468@orthanc.ab.ca>; from lyndon@orthanc.ab.ca on Sat, Apr 20, 2002 at 04:02:13PM -0600 X-URL: http://people.freebsd.org/~cjc/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Apr 20, 2002 at 04:02:13PM -0600, Lyndon Nerenberg wrote: > >>>>> "Crist" == Crist J Clark writes: > > Crist> I do this a lot too on systems where it makes sense. But I'm > Crist> not sure I understand what you are asking to be done. Is it > Crist> asking too much of an administrator to do, > > There are two ways to handle this. One is to modify the ports builds to > conditionally create a 'bpf' group. This requires the ports all agree > on the group, and I don't like the idea of a port install messing with > permissions and ownerships of things in /dev (which aren't sticky across > reboots, anyway). If the OS sets the access policy there cannot be any > confusion. OK. Now you've really lost me. What do ports have to do with this? Which ports? None of the sniffing programs I am aware of use set{g,u}id bits. They rely on the permissions of the user running them. -- Crist J. Clark | cjclark@alum.mit.edu | cjclark@jhu.edu http://people.freebsd.org/~cjc/ | cjc@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 20 15:15:18 2002 Delivered-To: freebsd-current@freebsd.org Received: from earth.hub.org (earth.hub.org [64.49.215.11]) by hub.freebsd.org (Postfix) with ESMTP id 1F05537B416; Sat, 20 Apr 2002 15:14:54 -0700 (PDT) Received: from localhost.localdomain (earth.hub.org [64.49.215.11]) by localhost (Postfix) with ESMTP id CF4FE1033B1; Sat, 20 Apr 2002 19:14:52 -0300 (ADT) Received: from earth.hub.org (earth.hub.org [64.49.215.11]) by earth.hub.org (Postfix) with ESMTP id 9E4DF103391; Sat, 20 Apr 2002 19:14:52 -0300 (ADT) Date: Sat, 20 Apr 2002 19:14:52 -0300 (ADT) From: "Marc G. Fournier" To: freebsd-current@freebsd.org Cc: freebsd-stable@freebsd.org Subject: FreeBSD 4.5-STABLE not easily scalable to large servers ... ? Message-ID: <20020420190408.O30724-100000@mail1.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Over the past week, I've been trying to get information on how to fix a server that panics with: | panic: vm_map_entry_create: kernel resources exhausted | mp_lock = 01000001; cpuid = 1; lapic.id = 01000000 | boot() called on cpu#1 Great ... but, how do I determine what 'resources' I need to increase to avoid that crash? I've tried increasing maxusers from 512->1024, but *if* that works, I imagine I'm raising a bunch of limits (and using memory) that I don't have to ... The server is a Dual-CPU PIII-1Ghz with 3Gig of RAM and ~3Gig of swap space right now ... the data drive is 5x18gig drives in a RAID5 configuration (hardware RAID, not vinum) ... I ran top in an xterm so that I could see what was up just before the crash, and the results were: last pid: 84988; load averages: 19.82, 57.35, 44.426 up 0+23:33:12 02:05:00 5021 processes:16 running, 5005 sleeping CPU states: 8.7% user, 0.0% nice, 24.3% system, 2.2% interrupt, 64.7% idle Mem: 2320M Active, 211M Inact, 390M Wired, 92M Cache, 199M Buf, 4348K Free Swap: 3072M Total, 1048M Used, 2024M Free, 34% Inuse, 448K Out So, I have plenty of swapspace left, lots of idle CPU and a whole whack of processes ... Now, looking at the LINT file, there appears to be *alot* of things I *could* change ... for instance, NSFBUFS, KVA_FILES, etc ... but I don't imagine that changing these blindly is particularly wise ... so, how do you determine what to change? For instance, at a maxusers of 512, NSFBUFS should be ~8704, and if I've only got 5000 processes running, chances are I'm still safe at that value, no? But sysctl doesn't show any 'sf_buf' value, so how do I figure out what I'm using? Basically, are there any commands similar to "netstat -m" for nmbclusters that I can run to 'monitor' and isolate where I'm exhausting these resources? Is there a doc on this sort of stuff that I should be reading for this? Something that talks about kernel tuning for high-load/processes servers? Thanks for any help in advance .. ------------------- machine i386 cpu I686_CPU ident kernel maxusers 1024 options NMBCLUSTERS=15360 options INET #InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000 #Delay (in ms) before probing SCSI options KTRACE #ktrace(1) support options SYSVSHM options SHMMAXPGS=98304 options SHMMAX=(SHMMAXPGS*PAGE_SIZE+1) options SYSVSEM options SEMMNI=2048 options SEMMNS=4096 options SYSVMSG #SYSV-style message queues options P1003_1B #Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM #Rate limit bad replies options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O device isa device pci device scbus # SCSI bus (required) device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) device amr # AMI MegaRAID device sym device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 flags 0x1 device psm0 at atkbdc? irq 12 device vga0 at isa? pseudo-device splash device sc0 at isa? flags 0x100 device npx0 at nexus? port IO_NPX irq 13 device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 device miibus # MII bus support device fxp # Intel EtherExpress PRO/100B (82557, 82558) pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device pty 256 # Pseudo-ttys (telnet etc) pseudo-device gif # IPv6 and IPv4 tunneling pseudo-device faith 1 # IPv6-to-IPv4 relaying (translation) pseudo-device bpf #Berkeley packet filter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 20 15:27:28 2002 Delivered-To: freebsd-current@freebsd.org Received: from orthanc.ab.ca (orthanc.ab.ca [216.123.203.186]) by hub.freebsd.org (Postfix) with ESMTP id 6FE3437B41D for ; Sat, 20 Apr 2002 15:27:20 -0700 (PDT) Received: from orthanc.ab.ca (localhost.orthanc.ab.ca [127.0.0.1]) by orthanc.ab.ca (8.11.6/8.11.6) with ESMTP id g3KMRIJ39147; Sat, 20 Apr 2002 16:27:18 -0600 (MDT) (envelope-from lyndon@orthanc.ab.ca) Message-Id: <200204202227.g3KMRIJ39147@orthanc.ab.ca> From: Lyndon Nerenberg Organization: The Frobozz Magic Homing Pigeon Company To: cjclark@alum.mit.edu Cc: freebsd-current@FreeBSD.ORG Subject: Re: Adding a 'bpf' group for /dev/bpf* In-reply-to: Your message of "Sat, 20 Apr 2002 15:11:52 PDT." <20020420151152.E76898@blossom.cjclark.org> X-Mailer: mh-e 5.0.92; MH 6.8.4; Emacs 21.1 Date: Sat, 20 Apr 2002 16:27:18 -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >>>>> "Crist" == Crist J Clark writes: Crist> OK. Now you've really lost me. What do ports have to do with Crist> this? Which ports? None of the sniffing programs I am aware Crist> of use set{g,u}id bits. They rely on the permissions of the Crist> user running them. Sorry -- keyboard and brain disconnect on my part. What I was trying to get at was the need to run sniffers as root by default. The fewer things that need to be run as root, the better (e.g. I don't want snort and trafdump running as root on my firewalls if I can avoid it). Programs like snort can attempt to lose uid-0 after opening the bpf device, but others like tcpdump do not. As David Wolfskill mentioned in a previous message, this idea is the same as how the operator group is used for dump. kmem did the same thing for ps and top. --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 20 15:42:51 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.kde.org (max.tat.physik.uni-tuebingen.de [134.2.170.93]) by hub.freebsd.org (Postfix) with SMTP id 4E31737B41B for ; Sat, 20 Apr 2002 15:42:46 -0700 (PDT) Received: (qmail 31766 invoked from network); 20 Apr 2002 22:42:26 -0000 Received: from localhost (HELO ugly) (127.0.0.1) by localhost with SMTP; 20 Apr 2002 22:42:26 -0000 Received: from ossi by ugly with local (Exim 3.35 #1 (Debian)) id 16z3Yr-0003ae-00 for ; Sun, 21 Apr 2002 00:42:29 +0200 Date: Sun, 21 Apr 2002 00:42:29 +0200 From: Oswald Buddenhagen To: current@freebsd.org Subject: uthread_init.c again Message-ID: <20020420224229.GA13290@ugly.homeip.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="liOOAslEiF7prFVr" Content-Disposition: inline User-Agent: Mutt/1.3.28i X-Spam-Rating: localhost 100/1000/N Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --liOOAslEiF7prFVr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline hello, this is again about the _thread_kern_pipe issue raised a few days ago. thinking about it again, it's nonsense to create any pid-specific workarounds by creating fake stdio. the solution is straightforward; patch attached (completely untested). note, that the open() wrapper (and other calls that create fds) need to check, if the newly created fd is a stdio one and adjust _pthread_stdio_flags - at least this is my understanding of this voodoo. but then, i don't have the faintest idea of what i'm talking about. :) greetings ps: flames must be explicitly cc'd to me. >:) -- Hi! I'm a .signature virus! Copy me into your ~/.signature, please! -- The problem with making software idiot-proof is that idiots are so clever. --liOOAslEiF7prFVr Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="uthread_init.c.diff" Index: uthread_init.c =================================================================== RCS file: /home/ncvs/src/lib/libc_r/uthread/uthread_init.c,v retrieving revision 1.38 diff -u -r1.38 uthread_init.c --- uthread_init.c 19 Mar 2002 22:58:56 -0000 1.38 +++ uthread_init.c 20 Apr 2002 22:42:19 -0000 @@ -173,31 +173,6 @@ if ((references[0] == NULL) || (libgcc_references[0] == NULL)) PANIC("Failed loading mandatory references in _thread_init"); - /* - * Check for the special case of this process running as - * or in place of init as pid = 1: - */ - if (getpid() == 1) { - /* - * Setup a new session for this process which is - * assumed to be running as root. - */ - if (setsid() == -1) - PANIC("Can't set session ID"); - if (revoke(_PATH_CONSOLE) != 0) - PANIC("Can't revoke console"); - if ((fd = __sys_open(_PATH_CONSOLE, O_RDWR)) < 0) - PANIC("Can't open console"); - if (setlogin("root") == -1) - PANIC("Can't set login to root"); - if (__sys_ioctl(fd,TIOCSCTTY, (char *) NULL) == -1) - PANIC("Can't set controlling terminal"); - if (__sys_dup2(fd,0) == -1 || - __sys_dup2(fd,1) == -1 || - __sys_dup2(fd,2) == -1) - PANIC("Can't dup2"); - } - /* Get the standard I/O flags before messing with them : */ for (i = 0; i < 3; i++) if (((_pthread_stdio_flags[i] = @@ -213,6 +188,16 @@ /* Cannot create pipe, so abort: */ PANIC("Cannot create kernel pipe"); } + /* + * Make sure the pipe does not get in the way of stdio: + */ + for (i = 0; i < 2; i++) + if (_thread_kern_pipe[i] < 3) { + if ((fd = __sys_fcntl(_thread_kern_pipe[i], F_DUPFD, 3)) == -1) + PANIC("Cannot create kernel pipe"); + __sys_close(_thread_kern_pipe[i]); + _thread_kern_pipe[i] = fd; + } /* Get the flags for the read pipe: */ else if ((flags = __sys_fcntl(_thread_kern_pipe[0], F_GETFL, NULL)) == -1) { /* Abort this application: */ --liOOAslEiF7prFVr-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 20 16: 1:13 2002 Delivered-To: freebsd-current@freebsd.org Received: from earth.hub.org (earth.hub.org [64.49.215.11]) by hub.freebsd.org (Postfix) with ESMTP id 269EA37B41B; Sat, 20 Apr 2002 16:00:58 -0700 (PDT) Received: from localhost.localdomain (earth.hub.org [64.49.215.11]) by localhost (Postfix) with ESMTP id 05A4C1033B1; Sat, 20 Apr 2002 20:00:58 -0300 (ADT) Received: from earth.hub.org (earth.hub.org [64.49.215.11]) by earth.hub.org (Postfix) with ESMTP id C752310338E; Sat, 20 Apr 2002 20:00:57 -0300 (ADT) Date: Sat, 20 Apr 2002 20:00:57 -0300 (ADT) From: "Marc G. Fournier" To: freebsd-current@freebsd.org Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 4.5-STABLE not easily scalable to large servers ... ? In-Reply-To: <20020420190408.O30724-100000@mail1.hub.org> Message-ID: <20020420195845.P1721-100000@mail1.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG As a quick follow-up to this, doing more searching on the web, I came across a few suggested 'sysctl' settings, which I've added to what I had before, for a total of: kern.maxfiles=65534 jail.sysvipc_allowed=1 vm.swap_idle_enabled=1 vfs.vmiodirenable=1 kern.ipc.somaxconn=4096 I've also just reduced my maxusers to 256 from 1024, since 1024 was crashing worse then 512, and I ran across the 'tuning' man page that stated that you shouldn't go above 256 :( Just a bit more detail on the setup ... On Sat, 20 Apr 2002, Marc G. Fournier wrote: > > Over the past week, I've been trying to get information on how to fix a > server that panics with: > > | panic: vm_map_entry_create: kernel resources exhausted > | mp_lock = 01000001; cpuid = 1; lapic.id = 01000000 > | boot() called on cpu#1 > > Great ... but, how do I determine what 'resources' I need to increase to > avoid that crash? I've tried increasing maxusers from 512->1024, but *if* > that works, I imagine I'm raising a bunch of limits (and using memory) > that I don't have to ... > > The server is a Dual-CPU PIII-1Ghz with 3Gig of RAM and ~3Gig of swap > space right now ... the data drive is 5x18gig drives in a RAID5 > configuration (hardware RAID, not vinum) ... > > I ran top in an xterm so that I could see what was up just before the > crash, and the results were: > > last pid: 84988; load averages: 19.82, 57.35, 44.426 up 0+23:33:12 02:05:00 > 5021 processes:16 running, 5005 sleeping > CPU states: 8.7% user, 0.0% nice, 24.3% system, 2.2% interrupt, 64.7% idle > Mem: 2320M Active, 211M Inact, 390M Wired, 92M Cache, 199M Buf, 4348K Free > Swap: 3072M Total, 1048M Used, 2024M Free, 34% Inuse, 448K Out > > So, I have plenty of swapspace left, lots of idle CPU and a whole > whack of processes ... > > Now, looking at the LINT file, there appears to be *alot* of > things I *could* change ... for instance, NSFBUFS, KVA_FILES, etc ... but > I don't imagine that changing these blindly is particularly wise ... so, > how do you determine what to change? For instance, at a maxusers of 512, > NSFBUFS should be ~8704, and if I've only got 5000 processes running, > chances are I'm still safe at that value, no? But sysctl doesn't show any > 'sf_buf' value, so how do I figure out what I'm using? > > Basically, are there any commands similar to "netstat -m" for > nmbclusters that I can run to 'monitor' and isolate where I'm exhausting > these resources? > > Is there a doc on this sort of stuff that I should be reading for > this? Something that talks about kernel tuning for high-load/processes > servers? > > Thanks for any help in advance .. > > ------------------- > machine i386 > cpu I686_CPU > ident kernel > maxusers 1024 > > options NMBCLUSTERS=15360 > > options INET #InterNETworking > options INET6 #IPv6 communications protocols > options FFS #Berkeley Fast Filesystem > options FFS_ROOT #FFS usable as root device [keep this!] > options SOFTUPDATES #Enable FFS soft updates support > options PROCFS #Process filesystem > options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] > options SCSI_DELAY=15000 #Delay (in ms) before probing SCSI > options KTRACE #ktrace(1) support > > options SYSVSHM > options SHMMAXPGS=98304 > options SHMMAX=(SHMMAXPGS*PAGE_SIZE+1) > > options SYSVSEM > options SEMMNI=2048 > options SEMMNS=4096 > > options SYSVMSG #SYSV-style message queues > > options P1003_1B #Posix P1003_1B real-time extensions > options _KPOSIX_PRIORITY_SCHEDULING > options ICMP_BANDLIM #Rate limit bad replies > > options SMP # Symmetric MultiProcessor Kernel > options APIC_IO # Symmetric (APIC) I/O > > device isa > device pci > > device scbus # SCSI bus (required) > device da # Direct Access (disks) > device sa # Sequential Access (tape etc) > device cd # CD > device pass # Passthrough device (direct SCSI access) > > device amr # AMI MegaRAID > device sym > > device atkbdc0 at isa? port IO_KBD > device atkbd0 at atkbdc? irq 1 flags 0x1 > device psm0 at atkbdc? irq 12 > > device vga0 at isa? > > pseudo-device splash > > device sc0 at isa? flags 0x100 > > device npx0 at nexus? port IO_NPX irq 13 > > device sio0 at isa? port IO_COM1 flags 0x10 irq 4 > device sio1 at isa? port IO_COM2 irq 3 > > device miibus # MII bus support > device fxp # Intel EtherExpress PRO/100B (82557, 82558) > > pseudo-device loop # Network loopback > pseudo-device ether # Ethernet support > pseudo-device pty 256 # Pseudo-ttys (telnet etc) > pseudo-device gif # IPv6 and IPv4 tunneling > pseudo-device faith 1 # IPv6-to-IPv4 relaying (translation) > > pseudo-device bpf #Berkeley packet filter > > > > > > 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-current" in the body of the message From owner-freebsd-current Sat Apr 20 16:55:42 2002 Delivered-To: freebsd-current@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id 7207C37B417; Sat, 20 Apr 2002 16:55:38 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1192) id 41CF2AE160; Sat, 20 Apr 2002 16:55:38 -0700 (PDT) Date: Sat, 20 Apr 2002 16:55:38 -0700 From: Alfred Perlstein To: "Marc G. Fournier" Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: FreeBSD 4.5-STABLE not easily scalable to large servers ... ? Message-ID: <20020420235538.GM38320@elvis.mu.org> References: <20020420190408.O30724-100000@mail1.hub.org> <20020420195845.P1721-100000@mail1.hub.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020420195845.P1721-100000@mail1.hub.org> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * The Hermit Hacker [020420 16:01] wrote: > > > As a quick follow-up to this, doing more searching on the web, I came > across a few suggested 'sysctl' settings, which I've added to what I had > before, for a total of: > > kern.maxfiles=65534 > jail.sysvipc_allowed=1 > vm.swap_idle_enabled=1 > vfs.vmiodirenable=1 > kern.ipc.somaxconn=4096 > > I've also just reduced my maxusers to 256 from 1024, since 1024 was > crashing worse then 512, and I ran across the 'tuning' man page that > stated that you shouldn't go above 256 :( > > Just a bit more detail on the setup ... You said you're running 5000 processes. 5000 processes of what? Are they useing SYSVSHM? If so, this sysctl might help: kern.ipc.shm_use_phys=1 It'll only work if you set it before your processes setup. Some more information about what these 5000 processes are doing would help. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 20 17:33:20 2002 Delivered-To: freebsd-current@freebsd.org Received: from electricrain.com (electricrain.com [64.71.143.226]) by hub.freebsd.org (Postfix) with ESMTP id 3E10B37B435 for ; Sat, 20 Apr 2002 17:32:57 -0700 (PDT) Received: (qmail 12845 invoked by uid 629); 21 Apr 2002 00:32:57 -0000 Date: Sat, 20 Apr 2002 17:32:57 -0700 From: Bill Fenner To: freebsd-current@freebsd.org Cc: davidc@acns.ab.ca Subject: Re: savecore Message-ID: <20020421003257.GA12773@electricrain.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.27i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Yes, I'm in favor of going back to the simple sequence number too. I don't understand the advantage of the MD5. While you're in there, could you put back minfree checking too? That bit me pretty badly today, with savecore filling up my /var because it doesn't care about minfree. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 20 18: 8:25 2002 Delivered-To: freebsd-current@freebsd.org Received: from earth.hub.org (earth.hub.org [64.49.215.11]) by hub.freebsd.org (Postfix) with ESMTP id C4C7737B405; Sat, 20 Apr 2002 18:08:20 -0700 (PDT) Received: from localhost.localdomain (earth.hub.org [64.49.215.11]) by localhost (Postfix) with ESMTP id F08B31033B6; Sat, 20 Apr 2002 22:07:59 -0300 (ADT) Received: from earth.hub.org (earth.hub.org [64.49.215.11]) by earth.hub.org (Postfix) with ESMTP id 7D9A01033B5; Sat, 20 Apr 2002 22:07:59 -0300 (ADT) Date: Sat, 20 Apr 2002 22:07:59 -0300 (ADT) From: "Marc G. Fournier" To: Alfred Perlstein Cc: freebsd-current@freebsd.org, Subject: Re: FreeBSD 4.5-STABLE not easily scalable to large servers ... ? In-Reply-To: <20020420235538.GM38320@elvis.mu.org> Message-ID: <20020420220410.S1721-100000@mail1.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 20 Apr 2002, Alfred Perlstein wrote: > * The Hermit Hacker [020420 16:01] wrote: > > > > > > As a quick follow-up to this, doing more searching on the web, I came > > across a few suggested 'sysctl' settings, which I've added to what I had > > before, for a total of: > > > > kern.maxfiles=65534 > > jail.sysvipc_allowed=1 > > vm.swap_idle_enabled=1 > > vfs.vmiodirenable=1 > > kern.ipc.somaxconn=4096 > > > > I've also just reduced my maxusers to 256 from 1024, since 1024 was > > crashing worse then 512, and I ran across the 'tuning' man page that > > stated that you shouldn't go above 256 :( > > > > Just a bit more detail on the setup ... > > You said you're running 5000 processes. 5000 processes of what? > > Are they useing SYSVSHM? If so, this sysctl might help: > > kern.ipc.shm_use_phys=1 Okay, never knew of that one before ... have it set for the next reboot, as I do have a few postgresql servers going on the 'root (non-jail)' server ... > It'll only work if you set it before your processes setup. > > Some more information about what these 5000 processes are doing > would help. Sorry ... the server is running ~210 jails ... so the '5k processes' would be when they all start up their periodic scripts ... normally, it hovers around 2700 processes ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 20 19:49:30 2002 Delivered-To: freebsd-current@freebsd.org Received: from pintail.mail.pas.earthlink.net (pintail.mail.pas.earthlink.net [207.217.120.122]) by hub.freebsd.org (Postfix) with ESMTP id A8D7F37B41C; Sat, 20 Apr 2002 19:49:17 -0700 (PDT) Received: from pool0111.cvx21-bradley.dialup.earthlink.net ([209.179.192.111] helo=mindspring.com) by pintail.mail.pas.earthlink.net with esmtp (Exim 3.33 #2) id 16z7Pb-0002L3-00; Sat, 20 Apr 2002 19:49:11 -0700 Message-ID: <3CC2288B.94DDFBC1@mindspring.com> Date: Sat, 20 Apr 2002 19:48:43 -0700 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Marc G. Fournier" Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: FreeBSD 4.5-STABLE not easily scalable to large servers ... ? References: <20020420190408.O30724-100000@mail1.hub.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Marc G. Fournier" wrote: > Over the past week, I've been trying to get information on how to fix a > server that panics with: > > | panic: vm_map_entry_create: kernel resources exhausted > | mp_lock = 01000001; cpuid = 1; lapic.id = 01000000 > | boot() called on cpu#1 > > Great ... but, how do I determine what 'resources' I need to increase to > avoid that crash? I've tried increasing maxusers from 512->1024, but *if* > that works, I imagine I'm raising a bunch of limits (and using memory) > that I don't have to ... > > The server is a Dual-CPU PIII-1Ghz with 3Gig of RAM and ~3Gig of swap > space right now ... the data drive is 5x18gig drives in a RAID5 > configuration (hardware RAID, not vinum) ... You have more memory than you can allocate kernel memory to provide page table entries for. The only solution is to increase your kernel virtual address space size to accomodate the page mappings. How to do this varies widely by the version of FreeBSD you are using, and, unless you read "NOTES" and are running a recent -current, is not incredibly well documented, and requires an understanding of how the virtual address space is laid out and managed (which is also not well documented anywhere). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 20 19:51:19 2002 Delivered-To: freebsd-current@freebsd.org Received: from pintail.mail.pas.earthlink.net (pintail.mail.pas.earthlink.net [207.217.120.122]) by hub.freebsd.org (Postfix) with ESMTP id 431D437B427; Sat, 20 Apr 2002 19:51:10 -0700 (PDT) Received: from pool0111.cvx21-bradley.dialup.earthlink.net ([209.179.192.111] helo=mindspring.com) by pintail.mail.pas.earthlink.net with esmtp (Exim 3.33 #2) id 16z7RU-0003sP-00; Sat, 20 Apr 2002 19:51:09 -0700 Message-ID: <3CC22900.1C5BD346@mindspring.com> Date: Sat, 20 Apr 2002 19:50:40 -0700 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Marc G. Fournier" Cc: Alfred Perlstein , freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: FreeBSD 4.5-STABLE not easily scalable to large servers ... ? References: <20020420220410.S1721-100000@mail1.hub.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Marc G. Fournier" wrote: > > It'll only work if you set it before your processes setup. > > > > Some more information about what these 5000 processes are doing > > would help. > > Sorry ... the server is running ~210 jails ... so the '5k processes' would > be when they all start up their periodic scripts ... normally, it hovers > around 2700 processes ... Sounds like my laptop. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 20 20:10:21 2002 Delivered-To: freebsd-current@freebsd.org Received: from earth.hub.org (earth.hub.org [64.49.215.11]) by hub.freebsd.org (Postfix) with ESMTP id D5CE737B400; Sat, 20 Apr 2002 20:10:07 -0700 (PDT) Received: from localhost.localdomain (earth.hub.org [64.49.215.11]) by localhost (Postfix) with ESMTP id 6191F103372; Sun, 21 Apr 2002 00:10:05 -0300 (ADT) Received: from earth.hub.org (earth.hub.org [64.49.215.11]) by earth.hub.org (Postfix) with ESMTP id 90982103350; Sun, 21 Apr 2002 00:10:01 -0300 (ADT) Date: Sun, 21 Apr 2002 00:10:01 -0300 (ADT) From: "Marc G. Fournier" To: Terry Lambert Cc: freebsd-current@freebsd.org, Subject: Re: FreeBSD 4.5-STABLE not easily scalable to large servers ... ? In-Reply-To: <3CC2288B.94DDFBC1@mindspring.com> Message-ID: <20020421000839.A1721-100000@mail1.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 20 Apr 2002, Terry Lambert wrote: > "Marc G. Fournier" wrote: > > Over the past week, I've been trying to get information on how to fix a > > server that panics with: > > > > | panic: vm_map_entry_create: kernel resources exhausted > > | mp_lock = 01000001; cpuid = 1; lapic.id = 01000000 > > | boot() called on cpu#1 > > > > Great ... but, how do I determine what 'resources' I need to increase to > > avoid that crash? I've tried increasing maxusers from 512->1024, but *if* > > that works, I imagine I'm raising a bunch of limits (and using memory) > > that I don't have to ... > > > > The server is a Dual-CPU PIII-1Ghz with 3Gig of RAM and ~3Gig of swap > > space right now ... the data drive is 5x18gig drives in a RAID5 > > configuration (hardware RAID, not vinum) ... > > You have more memory than you can allocate kernel memory to > provide page table entries for. > > The only solution is to increase your kernel virtual address > space size to accomodate the page mappings. > > How to do this varies widely by the version of FreeBSD you are > using, and, unless you read "NOTES" and are running a recent > -current, is not incredibly well documented, and requires an > understanding of how the virtual address space is laid out and > managed (which is also not well documented anywhere). Ya, this is the roadblock I'm hitting :( I'm running 4.5-STABLE here, as of this afternoon ... thoughts/suggestiosn based on that? Also, is there somethign that I can run to monitor this, similar to running netstat -m to watch nmbclusters? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 20 20:43: 2 2002 Delivered-To: freebsd-current@freebsd.org Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by hub.freebsd.org (Postfix) with ESMTP id 3EAFD37B404 for ; Sat, 20 Apr 2002 20:42:59 -0700 (PDT) Received: from blossom.cjclark.org ([12.234.91.48]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020421034250.SNOR1901.rwcrmhc52.attbi.com@blossom.cjclark.org>; Sun, 21 Apr 2002 03:42:50 +0000 Received: (from cjc@localhost) by blossom.cjclark.org (8.11.6/8.11.6) id g3L3gjG78272; Sat, 20 Apr 2002 20:42:45 -0700 (PDT) (envelope-from cjc) Date: Sat, 20 Apr 2002 20:42:45 -0700 From: "Crist J. Clark" To: Lyndon Nerenberg Cc: freebsd-current@FreeBSD.ORG Subject: Re: Adding a 'bpf' group for /dev/bpf* Message-ID: <20020420204245.F76898@blossom.cjclark.org> Reply-To: cjclark@alum.mit.edu References: <20020420151152.E76898@blossom.cjclark.org> <200204202227.g3KMRIJ39147@orthanc.ab.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200204202227.g3KMRIJ39147@orthanc.ab.ca>; from lyndon@orthanc.ab.ca on Sat, Apr 20, 2002 at 04:27:18PM -0600 X-URL: http://people.freebsd.org/~cjc/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Apr 20, 2002 at 04:27:18PM -0600, Lyndon Nerenberg wrote: > >>>>> "Crist" == Crist J Clark writes: > > Crist> OK. Now you've really lost me. What do ports have to do with > Crist> this? Which ports? None of the sniffing programs I am aware > Crist> of use set{g,u}id bits. They rely on the permissions of the > Crist> user running them. > > Sorry -- keyboard and brain disconnect on my part. What I was trying to > get at was the need to run sniffers as root by default. The fewer > things that need to be run as root, the better (e.g. I don't want snort > and trafdump running as root on my firewalls if I can avoid it). > Programs like snort can attempt to lose uid-0 after opening the bpf > device, but others like tcpdump do not. > > As David Wolfskill mentioned in a previous message, this idea is the > same as how the operator group is used for dump. kmem did the same > thing for ps and top. These are actually very different in that they are set{u,g}id commands (well, ps(1) is not set{u,g}id anymore and is root:wheel owned). The sniffing tools we've been discussing, and pretty much all of the ones I've used, tcpdump(1), snort(8), nmap(1), etc., are not. When tcpdump(1) or one of these ports is installed, there is no reason to give it any special group ownership. The thing that determines whether someone can sniff is the {u,g}id of the user executing the command. The port's Makefile doesn't need to know anything about your /etc/group; it just installs the file -r-xr-x-r-x root:wheel. The local administrator simply needs to execute the simple commands I put in my last mail to give a group sniffing powers. The files' permissions and ownership are never changed. Since the ports would really make no use of a preordained 'bpf' group, I still don't see what purpose it really serves to add one. I really hesitate to add groups and change default ownerships after seeing the _steady_ stream of mail that the smmsp:smmsp ownership of /var/spool/mqueue the sendmail(8) upgrade created. -- Crist J. Clark | cjclark@alum.mit.edu | cjclark@jhu.edu http://people.freebsd.org/~cjc/ | cjc@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 20 20:56:51 2002 Delivered-To: freebsd-current@freebsd.org Received: from ion.gank.org (ion.gank.org [64.81.113.130]) by hub.freebsd.org (Postfix) with ESMTP id 306DE37B404 for ; Sat, 20 Apr 2002 20:56:47 -0700 (PDT) Received: from aldaris (dsl081-113-221.dfw1.dsl.speakeasy.net [64.81.113.221]) by ion.gank.org (GankMail) with ESMTP id 02F78298 for ; Sat, 20 Apr 2002 22:59:02 -0500 (CDT) Message-ID: <014601c1e8e8$8defe350$5f45a8c0@auir.gank.org> Reply-To: "Craig Boston" From: "Craig Boston" To: References: <20020420151152.E76898@blossom.cjclark.org> <200204202227.g3KMRIJ39147@orthanc.ab.ca> <20020420204245.F76898@blossom.cjclark.org> Subject: Re: Adding a 'bpf' group for /dev/bpf* Date: Sat, 20 Apr 2002 22:56:42 -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 5.50.4522.1200 X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Crist J. Clark wrote: > These are actually very different in that they are set{u,g}id commands > (well, ps(1) is not set{u,g}id anymore and is root:wheel owned). The > sniffing tools we've been discussing, and pretty much all of the ones > I've used, tcpdump(1), snort(8), nmap(1), etc., are not. When > tcpdump(1) or one of these ports is installed, there is no reason to > give it any special group ownership. The thing that determines whether > someone can sniff is the {u,g}id of the user executing the > command. The port's Makefile doesn't need to know anything about your > /etc/group; it just installs the file -r-xr-x-r-x root:wheel. The > local administrator simply needs to execute the simple commands I put > in my last mail to give a group sniffing powers. The files' > permissions and ownership are never changed. Since -current by default uses devfs, is there a standard way to make the ownership/permissions of device nodes "sticky" so that they persist across boots? Or should we just put the appropriate commands in rc.local ? Besides bpf, this would be useful, for example, for people who want to change permissions on cd-rom devices to 644 so that non-root users can make iso images (or give a special group cd burner rights). Craig To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 20 21:29:36 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 4A31E37B426 for ; Sat, 20 Apr 2002 21:29:26 -0700 (PDT) Received: from localhost (eischen@localhost) by mail.pcnet.com (8.12.1/8.12.1) with ESMTP id g3L4TO2m028040; Sun, 21 Apr 2002 00:29:25 -0400 (EDT) Date: Sun, 21 Apr 2002 00:29:24 -0400 (EDT) From: Daniel Eischen To: Oswald Buddenhagen Cc: current@FreeBSD.ORG Subject: Re: uthread_init.c again In-Reply-To: <20020420224229.GA13290@ugly.homeip.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 21 Apr 2002, Oswald Buddenhagen wrote: > hello, > > this is again about the _thread_kern_pipe issue raised a few days ago. > thinking about it again, it's nonsense to create any pid-specific > workarounds by creating fake stdio. the solution is straightforward; > patch attached (completely untested). > note, that the open() wrapper (and other calls that create fds) need to > check, if the newly created fd is a stdio one and adjust > _pthread_stdio_flags - at least this is my understanding of this voodoo. > but then, i don't have the faintest idea of what i'm talking about. :) I like this patch better :-) Thanks, -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 20 21:33:24 2002 Delivered-To: freebsd-current@freebsd.org Received: from 12-234-22-238.client.attbi.com (12-234-90-219.client.attbi.com [12.234.90.219]) by hub.freebsd.org (Postfix) with ESMTP id D39D937B419 for ; Sat, 20 Apr 2002 21:33:19 -0700 (PDT) Received: from Master.gorean.org (master.gorean.org [10.0.0.2]) by 12-234-22-238.client.attbi.com (8.12.2/8.12.2) with ESMTP id g3L4XJHt070563; Sat, 20 Apr 2002 21:33:19 -0700 (PDT) (envelope-from DougB@FreeBSD.org) Received: from Master.gorean.org (zoot [127.0.0.1]) by Master.gorean.org (8.12.2/8.12.2) with ESMTP id g3L4XLLr016431; Sat, 20 Apr 2002 21:33:21 -0700 (PDT) (envelope-from DougB@FreeBSD.org) Received: from localhost (doug@localhost) by Master.gorean.org (8.12.2/8.12.2/Submit) with ESMTP id g3L4XJqN016428; Sat, 20 Apr 2002 21:33:21 -0700 (PDT) X-Authentication-Warning: Master.gorean.org: doug owned process doing -bs Date: Sat, 20 Apr 2002 21:33:19 -0700 (PDT) From: Doug Barton X-X-Sender: doug@master.gorean.org To: Craig Boston Cc: current@FreeBSD.org Subject: Re: Adding a 'bpf' group for /dev/bpf* In-Reply-To: <014601c1e8e8$8defe350$5f45a8c0@auir.gank.org> Message-ID: <20020420213227.R15997-100000@master.gorean.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 20 Apr 2002, Craig Boston wrote: > Since -current by default uses devfs, is there a standard way to make the > ownership/permissions of device nodes "sticky" so that they persist across > boots? rc.devfs -- "We have known freedom's price. We have shown freedom's power. And in this great conflict, ... we will see freedom's victory." - George W. Bush, President of the United States State of the Union, January 28, 2002 Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Apr 20 23:10:39 2002 Delivered-To: freebsd-current@freebsd.org Received: from smtp2.wanadoo.nl (smtp2.wanadoo.nl [194.134.35.138]) by hub.freebsd.org (Postfix) with ESMTP id 1244737B405 for ; Sat, 20 Apr 2002 23:10:35 -0700 (PDT) Received: from ams-gw.sohara.org (p3358.vwr.wanadoo.nl [212.129.225.38]) by smtp2.wanadoo.nl (8.11.3/8.11.3) with SMTP id g3L63PJ06358; Sun, 21 Apr 2002 08:03:26 +0200 (MEST) Date: Sun, 21 Apr 2002 08:03:21 +0200 From: "Steve O'Hara-Smith" To: Kris Kennaway Cc: james@floondoon.com, john@veidit.net, current@FreeBSD.ORG Subject: Re: Xfree86-4 problem Message-Id: <20020421080321.32224235.steve@sohara.org> In-Reply-To: <20020420133532.B96463@xor.obsecurity.org> References: <3CC07A63.4050406@veidit.net> <008a01c1e81f$67220ec0$0feba8c0@sphynx> <20020420133532.B96463@xor.obsecurity.org> X-Mailer: Sylpheed version 0.7.4 (GTK+ 1.2.10; i386-portbld-freebsd4.5) X-Face: %]+HVL}K`P8>+8ZcY-WGHP6j@&mxMo9JH6_WdgIgUGH)JX/usO0%jy7T~IVgqjumD^OBqX,Kv^-GM6mlw(fI^$"QRKyZ$?xx/ Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 20 Apr 2002 13:35:32 -0700 Kris Kennaway wrote: KK> wrapper always needs to be rebuilt when you update X, yes. All you really need to do is reset the X symlink (unless you are upgrading from 3 to 4 in which case you need a new wrapper). -- C:>WIN | Directable Mirrors The computer obeys and wins. |A Better Way To Focus The Sun You lose and Bill collects. | licenses available - see: | http://www.sohara.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message