From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 7 00:13:11 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 25A9F16A407 for ; Sun, 7 Jan 2007 00:13:11 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [199.26.172.34]) by mx1.freebsd.org (Postfix) with ESMTP id 0B9A113C442 for ; Sun, 7 Jan 2007 00:13:10 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id l070DAMf054857 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 6 Jan 2007 16:13:10 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id l070DALc054856; Sat, 6 Jan 2007 16:13:10 -0800 (PST) Received: from fbsd61 ([192.168.200.61]) by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA10235; Sat, 6 Jan 07 16:08:13 PST Date: Sat, 06 Jan 2007 16:11:01 -0800 From: perryh@pluto.rain.com To: bra@fsn.hu Message-Id: <45a03a95.08FguubdCa9DFcxj%perryh@pluto.rain.com> References: <45A0229F.7070701@fsn.hu> In-Reply-To: <45A0229F.7070701@fsn.hu> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: ufs_rename: fvp == tvp (can't happen), but it did X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Jan 2007 00:13:11 -0000 > The problem is the following: on machine A the mail spool is on a local > disk array (via ciss). On machine B we run experiments with an FC disk > array, so the e-mails are on gmirror'ed filesystems (on ciss for the > local disks and on isp for the FC array). > > The strange thing happens when both the local and FC disks are working > in the mirrors. I get the following warning very often: > ufs_rename: fvp == tvp (can't happen) > > If I do a gmirror remove for the FC array, these go away. Also, the > other machine (with only local disks) is free from this. It sounds as if the caller of ufs_rename() is confused. You could try setting a breakpoint on the printf(), or change it to a panic() to get a dump, and try to figure out who the caller is and what is going on. From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 7 11:34:16 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1071B16A40F for ; Sun, 7 Jan 2007 11:34:16 +0000 (UTC) (envelope-from dmw@unete.cl) Received: from qmail2.ifxnetworks.com (qmail2.ifxnetworks.com [200.110.128.9]) by mx1.freebsd.org (Postfix) with ESMTP id B1A6F13C455 for ; Sun, 7 Jan 2007 11:34:15 +0000 (UTC) (envelope-from dmw@unete.cl) Received: (qmail 30798 invoked from network); 7 Jan 2007 11:34:25 -0000 X-Spam-DCC: : qmail2.ifxnetworks.com 1074; Body=1 Fuz1=1 Fuz2=1 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on qmail2.ifxnetworks.com X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled version=3.1.7 Received: from host131.200.73.82.dynamic.ifxnw.cl (HELO daemon) (dmw@unete.cl@[200.73.82.131]) (envelope-sender ) by qmail2.ifxnetworks.com (qmail-ldap-1.03) with SMTP for ; 7 Jan 2007 11:34:24 -0000 From: Daniel Molina Wegener Organization: DMW To: FreeBSD Hackers Date: Sun, 7 Jan 2007 08:34:21 -0300 User-Agent: KMail/1.9.1 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200701070834.21711.dmw@unete.cl> Subject: strange pthread keys behavior X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dmw@unete.cl List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Jan 2007 11:34:16 -0000 Hello,=20 I'm coding with pthreads, but the behavior of pthread_key_delete is strange. When I use pthread_key_delete, and I do not wait for the automatic deallocation of thread specific data, I receive a strange warning: Thread 8053800 has exited with leftover thread-specific data after \ 4 destructor iterations =BFIs this a mistake in the code or a standard warning in FreeBSD pthreads? The code bellow can be compiled with and do not use the pthread_key_delete routine: gcc -Wall -Wextra -pthread -lpthread -o key key.c But if pthread_key_delete is used, compiling the code with: gcc -Wall -Wextra -DPTHR_WARNS -pthread -lpthread -o key key.c I get warning message... =2D---- BEGIN CODE ----- /* -*- mode: c; c-default-style: "bsd"; c-basic-offset: 4; -*- */ #include #include #include #include #include #include void *rtn(void *p); pthread_attr_t attr; pthread_t thr[3]; int main (void) { int rt, c; if (!pthread_attr_init (&attr)) { printf ("%d: attr =3D %p\n", getpid (), (void *)&attr); rt =3D pthread_attr_setdetachstate (&attr, PTHREAD_CREATE_DETACHED); if (rt =3D=3D 0) { printf ("%d: attr PTHDR_ATTR_DETACHED =3D %d\n", getpid (), rt); for (c =3D 0; c < 3; c++) { rt =3D pthread_create (&(thr[c]), &attr, rtn, (void *)NULL); } } } sleep (10); pthread_attr_destroy (&attr); pthread_exit (NULL); return 0; } void * rtn (void *p) { char str1[] =3D "hi"; char str2[] =3D "bye"; size_t len1; size_t len2; pthread_key_t k1, k2; void *d1, *d2; printf ("thr arg: %p", p); len1 =3D (size_t)strlen(str1) + 1; len2 =3D (size_t)strlen(str2) + 1; pthread_key_create (&k1, free); pthread_key_create (&k2, free); pthread_setspecific (k1, malloc(len1)); pthread_setspecific (k2, malloc(len2)); memset (pthread_getspecific (k1), (int)NULL, len1); memset (pthread_getspecific (k2), (int)NULL, len2); memcpy (pthread_getspecific (k1), str1, len1); memcpy (pthread_getspecific (k2), str2, len2); d1 =3D pthread_getspecific (k1); d2 =3D pthread_getspecific (k2); printf ("k1: [%p] %s\n", d1, (char *)d1); printf ("k2: [%p] %s\n", d2, (char *)d2); #ifdef PTHR_WARNS pthread_key_delete (k2); #endif /* !PTHR_WARNS */ sleep (2); pthread_exit (NULL); } =2D---- END CODE ----- Best regards... =2D-=20 . 0 . | Daniel Molina Wegener . . 0 | dmw at unete dot cl 0 0 0 | FreeBSD User From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 7 11:44:51 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 78BD416A40F for ; Sun, 7 Jan 2007 11:44:51 +0000 (UTC) (envelope-from bra@fsn.hu) Received: from people.fsn.hu (people.fsn.hu [195.228.252.137]) by mx1.freebsd.org (Postfix) with ESMTP id 3922613C459 for ; Sun, 7 Jan 2007 11:44:51 +0000 (UTC) (envelope-from bra@fsn.hu) Received: from localhost (localhost [127.0.0.1]) by people.fsn.hu (Postfix) with ESMTP id EA9C98442F; Sun, 7 Jan 2007 12:44:49 +0100 (CET) Received: from people.fsn.hu ([127.0.0.1]) by localhost (people.fsn.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 23387-09; Sun, 7 Jan 2007 12:44:45 +0100 (CET) Received: from [172.16.164.1] (fw.axelero.hu [195.228.243.120]) by people.fsn.hu (Postfix) with ESMTP id 3D71884425; Sun, 7 Jan 2007 12:44:45 +0100 (CET) Message-ID: <45A0DD27.4020704@fsn.hu> Date: Sun, 07 Jan 2007 12:44:39 +0100 From: Attila Nagy User-Agent: Thunderbird 2.0b1 (Windows/20061206) MIME-Version: 1.0 To: perryh@pluto.rain.com References: <45A0229F.7070701@fsn.hu> <45a03a95.08FguubdCa9DFcxj%perryh@pluto.rain.com> In-Reply-To: <45a03a95.08FguubdCa9DFcxj%perryh@pluto.rain.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at fsn.hu Cc: freebsd-hackers@freebsd.org Subject: Re: ufs_rename: fvp == tvp (can't happen), but it did X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Jan 2007 11:44:51 -0000 On 2007.01.07. 1:11, perryh@pluto.rain.com wrote: > It sounds as if the caller of ufs_rename() is confused. You could > try setting a breakpoint on the printf(), or change it to a panic() > to get a dump, and try to figure out who the caller is and what is > going on. > Yes this would be very good, especially if this wouldn't be a production machine or if I could reproduce this on a test system. But neither of this are true. :( Maybe I will try it on a sleepless night, in the maintenance window, thanks for the idea. From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 7 13:36:45 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AD8AA16A40F; Sun, 7 Jan 2007 13:36:45 +0000 (UTC) (envelope-from Benjamin.Close@clearchain.com) Received: from ipmail01.adl2.internode.on.net (ipmail01.adl2.internode.on.net [203.16.214.140]) by mx1.freebsd.org (Postfix) with ESMTP id 5D29F13C44C; Sun, 7 Jan 2007 13:36:43 +0000 (UTC) (envelope-from Benjamin.Close@clearchain.com) Received: from ppp225-225.lns2.adl4.internode.on.net (HELO mail.clearchain.com) ([203.122.225.225]) by ipmail01.adl2.internode.on.net with ESMTP; 08 Jan 2007 00:06:41 +1030 X-IronPort-AV: i="4.13,157,1167571800"; d="scan'208"; a="70609416:sNHT26384540" Received: from [192.168.155.249] ([192.168.155.249]) (authenticated bits=0) by mail.clearchain.com (8.13.8/8.13.8) with ESMTP id l07DaVPL003024 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Jan 2007 00:06:37 +1030 (CST) (envelope-from Benjamin.Close@clearchain.com) Message-ID: <45A0F739.3030202@clearchain.com> Date: Mon, 08 Jan 2007 00:05:53 +1030 From: Benjamin Close User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Massimo Lusetti References: <459E6477.2010508@clearchain.com> <200701051634.00293.max@love2party.net> <459E75A5.7000309@FreeBSD.org> <200701051732.27176.max@love2party.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88.7/2418/Sun Jan 7 20:12:41 2007 on pegasus.clearchain.com X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (mail.clearchain.com [192.168.155.1]); Mon, 08 Jan 2007 00:06:39 +1030 (CST) X-Mailman-Approved-At: Sun, 07 Jan 2007 14:55:20 +0000 Cc: Florent Thoumie , freebsd-hackers@freebsd.org, freebsd-drivers@freebsd.org, Attilio Rao , damien.bergamini@free.fr, sam@freebsd.org, gabor@freebsd.org, Max Laier Subject: Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Jan 2007 13:36:45 -0000 Massimo Lusetti wrote: > On 1/5/07, Max Laier wrote: >> Thoughts? Volunteers? > I can say that the first attempt still running fine here on my laptop > on a -STABLE as of yesterday. I use it on a daily basis without any > glitch. I must say i don't do or tried to do nothing special or > network intensive job, but for reading emails, doing a lot of ssh and > http/https the drivers is working smoothly. > > I will try to compile this new one on my stable during the week end > and will see on Monday how it will perform on my office wi-lan. > > For the records: my wpi doesn't still work on OpenBSD-current cause > it's integrated and the switch used to turn it on seems an acpi one > which OpenBSD doesn't attach very well yet. Hi Folks, I did the port as my searching led me to believe that progress on a driver had stagnated. Port 1: was done by Damien himself (http://lists.freebsd.org/pipermail/freebsd-mobile/2006-July/008768.html) Port 2: was an updated version by Daminen: http://osdir.com/ml/freebsd-hackers@freebsd.org/msg58154.html which seems to be duplicated here: http://people.freebsd.org/~flz/local/wpi/ (http://www.mail-archive.com/freebsd-net@freebsd.org/msg20710.html) With version 2 being minor bug fixes to version 1 to try and get it working. Since then the driver has come a long way in netbsd with the FreeBSD version just getting older. To others working on a wpi driver, please post something indicating what you've done and even a sample of what your up to so we can one build one driver that just works. I also did the driver port as everything I found failed to work on a 64bit kernel, most the time wouldn't even compile. I'm happy to try and maintain this driver. I have the hardware. The main bugs I know about in this driver port are: * The use of the iee80211_amrr code The files exist in -current in /usr/src/sys/net80211 but the required symbols are not in a GENERIC kernel build. There is a wlan_amrr module which uses this code, though I'm not sure how to make use of this, it appears a simple dependency on the module is not enough. The use of the 80211_amrr code also means that use under -stable requires quite a bit more work as Rink pointed out. * Bus resource allocation issues Mainly related to: "bus_dmamem_alloc failed to align memory properly." I'm hoping Mike (http://lists.freebsd.org/pipermail/freebsd-stable/2006-June/026262.html) might be able to help resolve these. These allocation issues are caused while allocating of the rx & tx ring buffers - which if they are broken explain why things don't work. I'm still coming to grips to how the whole bus_dma_tag_create works. The Netbsd bus_dma_map_alloc seems much more intuitive. I've found if the module failed the first time, unloading it, then reloading it would often make the allocation issues disappear and the driver just work. Though I've also found sometimes that even though the allocation issues are reported, things still work, I'm guessing the alignment is pulled into line by higher levels of bus_dma. * ifconfig down causes timeouts reseting the tx ring I'm still chasing the cause of this. It seems non critical as the driver still works with an ifconfig up * Watch dog timer uses an obsolete interface I'm looking into the correct way to do watchdog timing * A lock order reversal in wpi_intr lock order reversal: 1st 0xffffffff812d9e20 wpi0 (network driver) @ if_wpi.c:1554 2nd 0xffffff003cee32f0 radix node head (radix node head) @ net/route.c:147 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x3a witness_checkorder() at witness_checkorder+0x4f9 _mtx_lock_flags() at _mtx_lock_flags+0x75 rtalloc1() at rtalloc1+0x7a arplookup() at arplookup+0x5c arpintr() at arpintr+0x255 ether_demux() at ether_demux+0x2d3 ether_input() at ether_input+0x1e9 ieee80211_input() at ieee80211_input+0xd05 wpi_intr() at wpi_intr+0x9d7 ithread_loop() at ithread_loop+0xfe fork_exit() at fork_exit+0xaa fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffffffa0698d40, rbp = 0 --- For those wishing to help debug the driver and get it working, I've posted a new version http://www.clearchain.com/~benjsc/download/20070107-wpi-freebsd.tar.gz To help debug: kldload wpi_ucode kldload if_wpi wlandebug -i wpi0 0xffffff (I've included a copy of the -current tool to save having to checkout the tree) sysctl debug.wpi=10 (Debug levels are explained in if_wpi.c) ifconfig wpi0 up ... wait 30 seconds then... ifconfig wpi0 down Then put /var/log/messages somewhere on the web & let me know This will dump lots of debug info to syslog but should help me work out whats happening. If the driver works for you, stick to debug level 5 max, else you'll be bombarded with logs. I'll try to install FBSD 32 -current & -stable (32/64) on the laptop in the next week to see what might be different. ANY feedback is helpful. Finally, for those who see "rx tail flags error xxx" this is caused by a 802.11 frame with an invalid CRC. Hence seeing the occasional one (with debug level 4 or higher) is quiet normal. If you see floods of them then chances are the rx ring is really out of alignment and things will just be busted. Cheers, Benjamin From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 7 15:26:36 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C761E16A47E for ; Sun, 7 Jan 2007 15:26:36 +0000 (UTC) (envelope-from kuku@www.kukulies.org) Received: from www.kukulies.org (www.kukulies.org [213.146.112.180]) by mx1.freebsd.org (Postfix) with ESMTP id 1B7F113C4A6 for ; Sun, 7 Jan 2007 15:26:35 +0000 (UTC) (envelope-from kuku@www.kukulies.org) Received: from www.kukulies.org (localhost [127.0.0.1]) by www.kukulies.org (8.13.3/8.12.10) with ESMTP id l07FF9aN088696 for ; Sun, 7 Jan 2007 16:15:09 +0100 (CET) (envelope-from kuku@www.kukulies.org) Received: (from kuku@localhost) by www.kukulies.org (8.13.3/8.12.10/Submit) id l07FF849088695 for freebsd-hackers@freebsd.org; Sun, 7 Jan 2007 16:15:08 +0100 (CET) (envelope-from kuku) Date: Sun, 7 Jan 2007 16:15:08 +0100 From: "Christoph P. Kukulies" To: freebsd-hackers@freebsd.org Message-ID: <20070107151508.GA88673@kukulies.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: VMWARE-Player X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Jan 2007 15:26:36 -0000 Hi, does FreeBSD provide the ability to run VMWARE-Player for Linux and run VMs in it? -- Chris Christoph P. U. Kukulies kuku_at_kukulies.org From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 7 15:46:20 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C407416A416 for ; Sun, 7 Jan 2007 15:46:20 +0000 (UTC) (envelope-from wmoran@collaborativefusion.com) Received: from mx00.pub.collaborativefusion.com (mx00.pub.collaborativefusion.com [206.210.89.199]) by mx1.freebsd.org (Postfix) with ESMTP id 74A8113C467 for ; Sun, 7 Jan 2007 15:46:20 +0000 (UTC) (envelope-from wmoran@collaborativefusion.com) Received: from working (c-71-60-174-60.hsd1.pa.comcast.net [71.60.174.60]) (AUTH: LOGIN wmoran, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by wingspan with esmtp; Sun, 07 Jan 2007 10:46:19 -0500 id 0005643F.45A115CB.00017025 Date: Sun, 7 Jan 2007 10:46:18 -0500 From: Bill Moran To: "Christoph P. Kukulies" Message-Id: <20070107104618.1bd69f73.wmoran@collaborativefusion.com> In-Reply-To: <20070107151508.GA88673@kukulies.org> References: <20070107151508.GA88673@kukulies.org> Organization: Collaborative Fusion Inc. X-Mailer: Sylpheed version 2.2.10 (GTK+ 2.10.6; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: VMWARE-Player X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Jan 2007 15:46:20 -0000 "Christoph P. Kukulies" wrote: > > Hi, > > does FreeBSD provide the ability to run VMWARE-Player for Linux and > run VMs in it? No. To the best of my knowledge it's not possible to run any VMWare product under FreeBSD. Qemu will run VMWare virtual machines under some conditions. -Bill From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 7 15:52:33 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6A80A16A407; Sun, 7 Jan 2007 15:52:33 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.177]) by mx1.freebsd.org (Postfix) with ESMTP id 4377D13C44C; Sun, 7 Jan 2007 15:52:32 +0000 (UTC) (envelope-from max@love2party.net) Received: from [88.64.178.23] (helo=amd64.laiers.local) by mrelayeu.kundenserver.de (node=mrelayeu4) with ESMTP (Nemesis), id 0ML21M-1H3aJt3IbO-0000RV; Sun, 07 Jan 2007 16:52:26 +0100 From: Max Laier Organization: FreeBSD To: freebsd-hackers@freebsd.org Date: Sun, 7 Jan 2007 16:52:14 +0100 User-Agent: KMail/1.9.5 References: <459E6477.2010508@clearchain.com> <45A0F739.3030202@clearchain.com> In-Reply-To: <45A0F739.3030202@clearchain.com> X-Face: ,,8R(x[kmU]tKN@>gtH1yQE4aslGdu+2]; R]*pL,U>^H?)gW@49@wdJ`H<=?utf-8?q?=25=7D*=5FBD=0A=09U=5For=3D=5CmOZf764=26nYj=3DJYbR1PW0ud?=>|!~,,CPC.1-D$FG@0h3#'5"k{V]a~.<=?utf-8?q?mZ=7D44=23Se=7Em=0A=09Fe=7E=5C=5DX5B=5D=5Fxj?=(ykz9QKMw_l0C2AQ]}Ym8)fU MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart12044061.EdYQbaGecM"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200701071652.24674.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 Cc: Massimo Lusetti , Benjamin Close , Florent Thoumie , freebsd-drivers@freebsd.org, Attilio Rao , damien.bergamini@free.fr, sam@freebsd.org, gabor@freebsd.org Subject: Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Jan 2007 15:52:33 -0000 --nextPart12044061.EdYQbaGecM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sunday 07 January 2007 14:35, Benjamin Close wrote: > Massimo Lusetti wrote: > > On 1/5/07, Max Laier wrote: > >> Thoughts? Volunteers? > > > > I can say that the first attempt still running fine here on my laptop > > on a -STABLE as of yesterday. I use it on a daily basis without any > > glitch. I must say i don't do or tried to do nothing special or > > network intensive job, but for reading emails, doing a lot of ssh and > > http/https the drivers is working smoothly. > > > > I will try to compile this new one on my stable during the week end > > and will see on Monday how it will perform on my office wi-lan. > > > > For the records: my wpi doesn't still work on OpenBSD-current cause > > it's integrated and the switch used to turn it on seems an acpi one > > which OpenBSD doesn't attach very well yet. > > Hi Folks, > I did the port as my searching led me to believe that progress on a > driver had stagnated. > Port 1: was done by Damien himself > (http://lists.freebsd.org/pipermail/freebsd-mobile/2006-July/008768.htm >l) Port 2: was an updated version by Daminen: > http://osdir.com/ml/freebsd-hackers@freebsd.org/msg58154.html > which seems to be duplicated here: > http://people.freebsd.org/~flz/local/wpi/ > (http://www.mail-archive.com/freebsd-net@freebsd.org/msg20710.html) > With version 2 being minor bug fixes to version 1 to try and get it > working. Since then the driver has come a long way in netbsd with the > FreeBSD version just getting older. > > To others working on a wpi driver, please post something indicating > what you've done and even a sample of what your up to so we can one > build one driver that just works. I also did the driver port as > everything I found failed to work on a 64bit kernel, most the time > wouldn't even compile. > > I'm happy to try and maintain this driver. I have the hardware. Excellent! > The main bugs I know about in this driver port are: > > * The use of the iee80211_amrr code > The files exist in -current in /usr/src/sys/net80211 but the required > symbols are not in a GENERIC kernel build. There is a wlan_amrr module > which uses this code, though I'm not sure how to make use of this, it > appears a simple dependency on the module is not enough. The use of the > 80211_amrr code also means that use under -stable requires quite a bit > more work as Rink pointed out. > > * Bus resource allocation issues > Mainly related to: "bus_dmamem_alloc failed to align memory properly." > I'm hoping Mike > (http://lists.freebsd.org/pipermail/freebsd-stable/2006-June/026262.htm >l) might be able to help resolve these. > > These allocation issues are caused while allocating of the rx & tx ring > buffers - which if they are broken explain why things don't work. > I'm still coming to grips to how the whole bus_dma_tag_create works. > The Netbsd bus_dma_map_alloc seems much more intuitive. > I've found if the module failed the first time, unloading it, then > reloading it would often make the allocation issues disappear and the > driver just work. > Though I've also found sometimes that even though the allocation issues > are reported, things still work, I'm guessing the alignment is pulled > into line by higher levels of bus_dma. > > * ifconfig down causes timeouts reseting the tx ring > I'm still chasing the cause of this. It seems non critical as the > driver still works with an ifconfig up > > * Watch dog timer uses an obsolete interface > I'm looking into the correct way to do watchdog timing I have patches for iwi(4) somewhere and should finally get to doing=20 something with them ... > * A lock order reversal in wpi_intr > lock order reversal: > 1st 0xffffffff812d9e20 wpi0 (network driver) @ if_wpi.c:1554 > 2nd 0xffffff003cee32f0 radix node head (radix node head) @ > net/route.c:147 KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x3a > witness_checkorder() at witness_checkorder+0x4f9 > _mtx_lock_flags() at _mtx_lock_flags+0x75 > rtalloc1() at rtalloc1+0x7a > arplookup() at arplookup+0x5c > arpintr() at arpintr+0x255 > ether_demux() at ether_demux+0x2d3 > ether_input() at ether_input+0x1e9 > ieee80211_input() at ieee80211_input+0xd05 > wpi_intr() at wpi_intr+0x9d7 > ithread_loop() at ithread_loop+0xfe > fork_exit() at fork_exit+0xaa > fork_trampoline() at fork_trampoline+0xe > --- trap 0, rip =3D 0, rsp =3D 0xffffffffa0698d40, rbp =3D 0 --- This one looks like the same issue as if_iwi.c, 1.43:=20 http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/iwi/if_iwi.c#rev1.43 i.e. just drop the driver lock when calling back into the (net80211)=20 stack. There is some discussion about how the "ic" is protected, but for=20 now dropping the lock is the right thing to do. > For those wishing to help debug the driver and get it working, I've > posted a new version > http://www.clearchain.com/~benjsc/download/20070107-wpi-freebsd.tar.gz Your box seems to have a reasonable uptime. Is that right, or should I=20 continue to mirror your tarballs? > To help debug: > > kldload wpi_ucode > kldload if_wpi > wlandebug -i wpi0 0xffffff (I've included a copy of the -current > tool to save having to checkout the tree) > sysctl debug.wpi=3D10 (Debug levels are explained in if_wpi.c) > ifconfig wpi0 up > ... wait 30 seconds then... > ifconfig wpi0 down > > Then put /var/log/messages somewhere on the web & let me know > > This will dump lots of debug info to syslog but should help me work out > whats happening. If the driver works for you, stick to debug level 5 > max, else you'll be bombarded with logs. I'll try to install FBSD 32 > -current & -stable (32/64) on the laptop in the next week to see what > might be different. ANY feedback is helpful. > > Finally, for those who see "rx tail flags error xxx" this is caused by > a 802.11 frame with an invalid CRC. Hence seeing the occasional one > (with debug level 4 or higher) is quiet normal. If you see floods of > them then chances are the rx ring is really out of alignment and things > will just be busted. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart12044061.EdYQbaGecM Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQBFoRc4XyyEoT62BG0RAv9WAJ91z7RP+C+Gw0wnG0clMYjgwcXkBwCfRjYd VSfCAbUxoC/az+NIzIzDfKM= =rmVB -----END PGP SIGNATURE----- --nextPart12044061.EdYQbaGecM-- From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 7 15:54:54 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 62D9816A40F for ; Sun, 7 Jan 2007 15:54:54 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id 24B0313C44C for ; Sun, 7 Jan 2007 15:54:54 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.8/8.13.8/NETPLEX) with ESMTP id l07Fif2v015063; Sun, 7 Jan 2007 10:44:42 -0500 (EST) Date: Sun, 7 Jan 2007 10:44:41 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Daniel Molina Wegener In-Reply-To: <200701070834.21711.dmw@unete.cl> Message-ID: References: <200701070834.21711.dmw@unete.cl> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-959030623-1168184681=:5044" X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-3.0 (mail.ntplx.net [204.213.176.10]); Sun, 07 Jan 2007 10:44:42 -0500 (EST) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: FreeBSD Hackers Subject: Re: strange pthread keys behavior X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Jan 2007 15:54:54 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---559023410-959030623-1168184681=:5044 Content-Type: TEXT/PLAIN; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Sun, 7 Jan 2007, Daniel Molina Wegener wrote: > Hello, > > I'm coding with pthreads, but the behavior of pthread_key_delete > is strange. When I use pthread_key_delete, and I do not wait for the > automatic deallocation of thread specific data, I receive a strange > warning: > > Thread 8053800 has exited with leftover thread-specific data after \ > 4 destructor iterations > > =BFIs this a mistake in the code or a standard warning in FreeBSD > pthreads? Yes, it looks like a buggy program... > The code bellow can be compiled with and do not use the > pthread_key_delete routine: See the POSIX spec with regard to pthread_key_create(): http://www.opengroup.org/onlinepubs/009695399/functions/pthread_key_crea= te.html You may have to create an account (free) in order to view it. Also look at pthread_key_delete(). I think the problem is that you are calling pthread_key_delete() from the thread that is creating the key and before the thread has exited (when the thread-specific key data is destroyed). You have invalidated the key by deleting it, so when the thread exits, it can't call the destructor and it iterates PTHREAD_KEY_MAX times trying to deallocate the key data. That is where the error message is generated. --=20 DE ---559023410-959030623-1168184681=:5044-- From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 7 16:34:17 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 21EDD16A40F; Sun, 7 Jan 2007 16:34:17 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.174]) by mx1.freebsd.org (Postfix) with ESMTP id 7BAA813C480; Sun, 7 Jan 2007 16:34:16 +0000 (UTC) (envelope-from max@love2party.net) Received: from [88.64.178.23] (helo=amd64.laiers.local) by mrelayeu.kundenserver.de (node=mrelayeu1) with ESMTP (Nemesis), id 0MKwpI-1H3ayN0wpt-0000Qd; Sun, 07 Jan 2007 17:34:15 +0100 From: Max Laier Organization: FreeBSD To: freebsd-hackers@freebsd.org Date: Sun, 7 Jan 2007 17:34:07 +0100 User-Agent: KMail/1.9.5 X-Face: ,,8R(x[kmU]tKN@>gtH1yQE4aslGdu+2]; R]*pL,U>^H?)gW@49@wdJ`H<%}*_BD U_or=\mOZf764&nYj=JYbR1PW0ud>|!~, , CPC.1-D$FG@0h3#'5"k{V]a~. X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 Cc: freebsd-current@freebsd.org Subject: Call for FreeBSD Status Reports X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: monthly@freebsd.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Jan 2007 16:34:17 -0000 --nextPart2269241.SVitMojiki Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, and a good 2007 to everyone! It's time to reminisce about last year, in=20 particular about the last three month aka. forth quarter. This is the=20 call for Status Reports covering this timeframe! Submission due has just=20 been moved to January 14th. Submissions must be in the report xml format. You can either use the=20 template[1] or the generator cgi[2]. Please mail the result of either to=20 monthly@ by January 14th. Every project related to FreeBSD should submit=20 a report. Past reports can be browsered from the Status Report=20 homepage[3]. Looking forward to your submissions! I'd also like to remind you that the BSDCan Call for Papers ends at=20 January 19th. While you are writting a Status Report - consider=20 submitting a talk about your work, too! [1] http://www.freebsd.org/news/status/report-sample.xml [2] http://www.freebsd.org/cgi/monthly.cgi [3] http://www.freebsd.org/news/status/ =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart2269241.SVitMojiki Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQBFoSEFXyyEoT62BG0RAu5nAJ43/Qz5D+MSqFWWSbbpYeNxoURsJwCfc0g2 BWFYR71E0fiwaeZQ9l3cpXk= =XxzT -----END PGP SIGNATURE----- --nextPart2269241.SVitMojiki-- From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 7 16:51:50 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9318716A403 for ; Sun, 7 Jan 2007 16:51:50 +0000 (UTC) (envelope-from fcash@ocis.net) Received: from smtp.sd73.bc.ca (smtp.sd73.bc.ca [142.24.13.140]) by mx1.freebsd.org (Postfix) with ESMTP id 728E313C428 for ; Sun, 7 Jan 2007 16:51:50 +0000 (UTC) (envelope-from fcash@ocis.net) Received: from localhost (localhost [127.0.0.1]) by localhost.sd73.bc.ca (Postfix) with ESMTP id AF2B01A000ED3 for ; Sun, 7 Jan 2007 08:33:05 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at smtp.sd73.bc.ca Received: from smtp.sd73.bc.ca ([127.0.0.1]) by localhost (smtp.sd73.bc.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id yeEky80FR5xx for ; Sun, 7 Jan 2007 08:33:03 -0800 (PST) Received: from webmail.sd73.bc.ca (webmail.sd73.bc.ca [10.10.10.17]) by smtp.sd73.bc.ca (Postfix) with ESMTP id 293FE1A0007A4 for ; Sun, 7 Jan 2007 08:33:03 -0800 (PST) Received: from 24.71.119.183 (SquirrelMail authenticated user fcash) by webmail.sd73.bc.ca with HTTP; Sun, 7 Jan 2007 08:33:03 -0800 (PST) Message-ID: <62445.24.71.119.183.1168187583.squirrel@webmail.sd73.bc.ca> In-Reply-To: <20070107104618.1bd69f73.wmoran@collaborativefusion.com> References: <20070107151508.GA88673@kukulies.org> <20070107104618.1bd69f73.wmoran@collaborativefusion.com> Date: Sun, 7 Jan 2007 08:33:03 -0800 (PST) From: "Freddie Cash" To: hackers@freebsd.org User-Agent: SquirrelMail/1.5.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: Subject: Re: VMWARE-Player X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Jan 2007 16:51:50 -0000 On Sun, January 7, 2007 7:46 am, Bill Moran wrote: > "Christoph P. Kukulies" wrote: >> does FreeBSD provide the ability to run VMWARE-Player for Linux and >> run VMs in it? > > No. To the best of my knowledge it's not possible to run any VMWare > product under FreeBSD. VMWare 3 is in the ports tree. That is the latest version of VMWare that works on FreeBSD, and a lot of people are having problems running that on -CURRENT. Runs fine on 6.x though. ---- Freddie Cash fcash@ocis.net From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 7 19:36:51 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1AD0316A403 for ; Sun, 7 Jan 2007 19:36:51 +0000 (UTC) (envelope-from dmw@unete.cl) Received: from qmail1.ifxnetworks.com (qmail1.ifxnetworks.com [200.110.128.7]) by mx1.freebsd.org (Postfix) with ESMTP id B8B7013C455 for ; Sun, 7 Jan 2007 19:36:50 +0000 (UTC) (envelope-from dmw@unete.cl) Received: (qmail 24997 invoked from network); 7 Jan 2007 19:36:49 -0000 X-Spam-DCC: sonic.net: qmail1.ifxnetworks.com 1156; Body=1 Fuz1=1 Fuz2=1 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on qmail1.ifxnetworks.com X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled version=3.1.7 Received: from host181.200.73.29.dynamic.ifxnw.cl (HELO daemon) (dmw@unete.cl@[200.73.29.181]) (envelope-sender ) by qmail1.ifxnetworks.com (qmail-ldap-1.03) with SMTP for ; 7 Jan 2007 19:36:49 -0000 From: Daniel Molina Wegener Organization: DMW To: freebsd-hackers@freebsd.org, Daniel Eischen Date: Sun, 7 Jan 2007 16:36:57 -0300 User-Agent: KMail/1.9.1 References: <200701070834.21711.dmw@unete.cl> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200701071636.57861.dmw@unete.cl> Cc: Subject: Re: strange pthread keys behavior X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dmw@unete.cl List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Jan 2007 19:36:51 -0000 On Sunday 07 January 2007 12:44, Daniel Eischen wrote: > [SNIP] > > > > =BFIs this a mistake in the code or a standard warning in > > FreeBSD pthreads? > > Yes, it looks like a buggy program... > > > The code bellow can be compiled with and do not use the > > pthread_key_delete routine: > > See the POSIX spec with regard to pthread_key_create(): > > =20 > http://www.opengroup.org/onlinepubs/009695399/functions/pthre >ad_key_create.html > > You may have to create an account (free) in order to view it. > Also look at pthread_key_delete(). > > I think the problem is that you are calling > pthread_key_delete() from the thread that is creating the key > and before the thread has exited (when the thread-specific > key data is destroyed). You have invalidated the key by > deleting it, so when the thread exits, it can't call the > destructor and it iterates PTHREAD_KEY_MAX times trying to > deallocate the key data. That is where the error message is > generated. Thanks, really... Best regards... =2D-=20 . 0 . | Daniel Molina Wegener . . 0 | dmw at unete dot cl 0 0 0 | FreeBSD User From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 7 20:05:18 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5F65D16A40F for ; Sun, 7 Jan 2007 20:05:18 +0000 (UTC) (envelope-from freebsd-hackers@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 0D0C313C459 for ; Sun, 7 Jan 2007 20:05:15 +0000 (UTC) (envelope-from freebsd-hackers@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1H3dWn-0006VP-9k for freebsd-hackers@freebsd.org; Sun, 07 Jan 2007 20:17:57 +0100 Received: from 89-172-46-216.adsl.net.t-com.hr ([89.172.46.216]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 07 Jan 2007 20:17:57 +0100 Received: from ivoras by 89-172-46-216.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 07 Jan 2007 20:17:57 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-hackers@freebsd.org From: Ivan Voras Date: Sun, 07 Jan 2007 20:17:19 +0100 Lines: 26 Message-ID: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigDABA33E81A83749121AD8011" X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 89-172-46-216.adsl.net.t-com.hr User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) X-Enigmail-Version: 0.94.1.2 Sender: news Subject: kqueue NOTE_RENAME X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Jan 2007 20:05:18 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigDABA33E81A83749121AD8011 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I trying to use kqueue to monitor what happens to a directory tree, and one of the issues is how to handle NOTE_RENAME. In particular, while I can connect the event with the old filename (by storing (fd,filename) pairs), I don't know how to get the new name. Any ideas? --------------enigDABA33E81A83749121AD8011 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFoUdGldnAQVacBcgRAntmAJ0SAPYVuaYDazG8FAU+hiKt5HB3rwCePzVt VImLOi8rhNKWFZAHeOLdKOk= =f1AG -----END PGP SIGNATURE----- --------------enigDABA33E81A83749121AD8011-- From owner-freebsd-hackers@FreeBSD.ORG Sun Jan 7 17:08:47 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 769E216A407; Sun, 7 Jan 2007 17:08:47 +0000 (UTC) (envelope-from joel@FreeBSD.org) Received: from av7-2-sn3.vrr.skanova.net (av7-2-sn3.vrr.skanova.net [81.228.9.182]) by mx1.freebsd.org (Postfix) with ESMTP id 2DD1713C44C; Sun, 7 Jan 2007 17:08:46 +0000 (UTC) (envelope-from joel@FreeBSD.org) Received: by av7-2-sn3.vrr.skanova.net (Postfix, from userid 502) id 53D2137EC0; Sun, 7 Jan 2007 17:39:38 +0100 (CET) Received: from smtp3-1-sn3.vrr.skanova.net (smtp3-1-sn3.vrr.skanova.net [81.228.9.101]) by av7-2-sn3.vrr.skanova.net (Postfix) with ESMTP id 16C1B37E60; Sun, 7 Jan 2007 17:39:38 +0100 (CET) Received: from [192.168.1.199] (81-234-214-163-no68.tbcn.telia.com [81.234.214.163]) by smtp3-1-sn3.vrr.skanova.net (Postfix) with ESMTP id D55E237E49; Sun, 7 Jan 2007 17:40:00 +0100 (CET) From: Joel Dahl To: Benjamin Close In-Reply-To: <45A0F739.3030202@clearchain.com> References: <459E6477.2010508@clearchain.com> <200701051634.00293.max@love2party.net> <459E75A5.7000309@FreeBSD.org> <200701051732.27176.max@love2party.net> <45A0F739.3030202@clearchain.com> Content-Type: text/plain; charset=iso8859-1 Date: Sun, 07 Jan 2007 17:39:59 +0100 Message-Id: <1168187999.1124.4.camel@jesus.automatvapen.se> Mime-Version: 1.0 X-Mailer: Evolution 2.8.2.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit X-Mailman-Approved-At: Sun, 07 Jan 2007 21:32:36 +0000 Cc: Massimo Lusetti , gavin.atkinson@ury.york.ac.uk, Florent Thoumie , freebsd-hackers@freebsd.org, freebsd-drivers@freebsd.org, Attilio Rao , damien.bergamini@free.fr, sam@freebsd.org, gabor@freebsd.org, Max Laier Subject: Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Jan 2007 17:08:47 -0000 Mån 2007-01-08 klockan 00:05 +1030 skrev Benjamin Close: > Hi Folks, > I did the port as my searching led me to believe that progress on a > driver had stagnated. > Port 1: was done by Damien himself > (http://lists.freebsd.org/pipermail/freebsd-mobile/2006-July/008768.html) > Port 2: was an updated version by Daminen: > http://osdir.com/ml/freebsd-hackers@freebsd.org/msg58154.html > which seems to be duplicated here: > http://people.freebsd.org/~flz/local/wpi/ > (http://www.mail-archive.com/freebsd-net@freebsd.org/msg20710.html) > With version 2 being minor bug fixes to version 1 to try and get it > working. Since then the driver has come a long way in netbsd with the > FreeBSD version just getting older. > > To others working on a wpi driver, please post something indicating what > you've done and even a sample of what your up to so we can one build one > driver that just works. I also did the driver port as everything I found > failed to work on a 64bit kernel, most the time wouldn't even compile. Gavin Atkinson (CC'ed) is AFAIK also working on wpi(4) for FreeBSD, according to his announcement on net@: http://lists.freebsd.org/pipermail/freebsd-net/2006-December/012808.html -- Joel From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 8 01:22:34 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6B48816A40F for ; Mon, 8 Jan 2007 01:22:34 +0000 (UTC) (envelope-from SRS0=AaDHVk=GR=vvelox.net=v.velox@yourhostingaccount.com) Received: from mailout11.yourhostingaccount.com (mailout11.yourhostingaccount.com [65.254.253.88]) by mx1.freebsd.org (Postfix) with ESMTP id 427AD13C457 for ; Mon, 8 Jan 2007 01:22:34 +0000 (UTC) (envelope-from SRS0=AaDHVk=GR=vvelox.net=v.velox@yourhostingaccount.com) Received: from scan02.yourhostingaccount.com ([10.1.1.232] helo=scan02.yourhostingaccount.com) by mailout11.yourhostingaccount.com with esmtp (Exim) id 1H3ixe-0000a4-Lq for freebsd-hackers@freebsd.org; Sun, 07 Jan 2007 20:06:02 -0500 Received: from authsmtp11.yourhostingaccount.com ([10.1.18.11] ident=exim) by scan02.yourhostingaccount.com with spamscanlookuphost (Exim) id 1H3ixe-00013z-GC for freebsd-hackers@freebsd.org; Sun, 07 Jan 2007 20:06:02 -0500 Received: from authsmtp11.yourhostingaccount.com ([10.1.18.11] helo=authsmtp11.yourhostingaccount.com) by scan02.yourhostingaccount.com with esmtp (Exim) id 1H3ixd-00013u-I3 for freebsd-hackers@freebsd.org; Sun, 07 Jan 2007 20:06:01 -0500 Received: from [69.92.217.33] (helo=vixen42) by authsmtp11.yourhostingaccount.com with esmtpa (Exim) id 1H3ixd-0005ek-0H for freebsd-hackers@freebsd.org; Sun, 07 Jan 2007 20:06:01 -0500 Date: Sun, 7 Jan 2007 19:06:16 -0600 From: Vulpes Velox To: freebsd-hackers@freebsd.org Message-ID: <20070107190616.73dee7b0@vixen42> X-Mailer: Claws Mail 2.6.1 (GTK+ 2.10.7; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-EN-UserInfo: 0d1ca1697cdb7a831d4877828571b7ab:1570f0de6936c69fef9e164fffc541bc X-EN-AuthUser: vvelox2 Sender: Vulpes Velox Subject: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2007 01:22:34 -0000 I was just wondering. How many people here have given lots of though about integrating FreeBSD configuration with LDAP. I've just begun looking at it a lot more and was curious as to what other people think in this area. From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 8 02:51:58 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 53E4716A403 for ; Mon, 8 Jan 2007 02:51:58 +0000 (UTC) (envelope-from dgilbert@daveg.ca) Received: from ox.eicat.ca (ox.eicat.ca [66.96.30.35]) by mx1.freebsd.org (Postfix) with ESMTP id 24C6213C465 for ; Mon, 8 Jan 2007 02:51:58 +0000 (UTC) (envelope-from dgilbert@daveg.ca) Received: by ox.eicat.ca (Postfix, from userid 66) id 32C73C40B; Sun, 7 Jan 2007 21:34:17 -0500 (EST) Received: by canoe.dclg.ca (Postfix, from userid 101) id 9FD9150840; Sun, 7 Jan 2007 21:34:16 -0500 (EST) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17825.44456.556954.545497@canoe.dclg.ca> Date: Sun, 7 Jan 2007 21:34:16 -0500 To: freebsd-hackers@freebsd.org X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid Subject: dump reads more than restore writes? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2007 02:51:58 -0000 I've got a command line like the following: dump -0af - /dev/ad1s1g | restore -rf - ... and I'm watching gstat. ad1s1g is not mounted. The disk on which the restore is running is also quiet (nobody using the disk). And gstat says that ad1 is consistently reading 31 to 37 megabytes per second and ad2 (the restore disk) is consistently writing 10 to 13 megabytes per second. This is over hours --- the figures never catch up. So... is gstat wrong? Is dump reading substantially more than restore is writing? Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================ From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 8 03:42:16 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4AE1A16A407 for ; Mon, 8 Jan 2007 03:42:16 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.freebsd.org (Postfix) with ESMTP id EDE6913C448 for ; Mon, 8 Jan 2007 03:42:15 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.6/8.13.8) id l083UkOc015608; Sun, 7 Jan 2007 21:30:46 -0600 (CST) (envelope-from dan) Date: Sun, 7 Jan 2007 21:30:46 -0600 From: Dan Nelson To: David Gilbert Message-ID: <20070108033046.GA41724@dan.emsphone.com> References: <17825.44456.556954.545497@canoe.dclg.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17825.44456.556954.545497@canoe.dclg.ca> X-OS: FreeBSD 6.2-PRERELEASE User-Agent: Mutt/1.5.13 (2006-08-11) Cc: freebsd-hackers@freebsd.org Subject: Re: dump reads more than restore writes? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2007 03:42:16 -0000 In the last episode (Jan 07), David Gilbert said: > I've got a command line like the following: > > dump -0af - /dev/ad1s1g | restore -rf - > > ... and I'm watching gstat. ad1s1g is not mounted. The disk on which > the restore is running is also quiet (nobody using the disk). > > And gstat says that ad1 is consistently reading 31 to 37 megabytes > per second and ad2 (the restore disk) is consistently writing 10 to > 13 megabytes per second. This is over hours --- the figures never > catch up. If you have a lot of small files, dump may be rereading directory information. Dump has a cache option that can help, but make sure you also dump a snapshot (i.e. always use -L when using -C). -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 8 04:02:31 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3E8F816A403 for ; Mon, 8 Jan 2007 04:02:31 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [199.26.172.34]) by mx1.freebsd.org (Postfix) with ESMTP id 08DD713C46B for ; Mon, 8 Jan 2007 04:02:30 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id l0842MFh025602 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 7 Jan 2007 20:02:22 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id l0842MqS025601; Sun, 7 Jan 2007 20:02:22 -0800 (PST) Received: from fbsd61 ([192.168.200.61]) by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA12281; Sun, 7 Jan 07 19:59:53 PST Date: Sun, 07 Jan 2007 20:02:40 -0800 From: perryh@pluto.rain.com To: dgilbert@dclg.ca Message-Id: <45a1c260./gHVPL2TJkCotGTS%perryh@pluto.rain.com> References: <17825.44456.556954.545497@canoe.dclg.ca> In-Reply-To: <17825.44456.556954.545497@canoe.dclg.ca> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: dump reads more than restore writes? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2007 04:02:31 -0000 > Is dump reading substantially more than restore is writing? Quite possibly, esp. if the source disk is nowhere near full and/or most of the files being handled are small. dump reads every inode on the disk, including those which are unallocated, and probably reads entire data blocks -- or even entire FS blocks -- even when only part of the block contains useful data. Restore writes only what it has to. From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 8 04:19:26 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A501116A416 for ; Mon, 8 Jan 2007 04:19:26 +0000 (UTC) (envelope-from dgilbert@daveg.ca) Received: from ox.eicat.ca (ox.eicat.ca [66.96.30.35]) by mx1.freebsd.org (Postfix) with ESMTP id 7C43C13C455 for ; Mon, 8 Jan 2007 04:19:26 +0000 (UTC) (envelope-from dgilbert@daveg.ca) Received: by ox.eicat.ca (Postfix, from userid 66) id 88CB7C18A; Sun, 7 Jan 2007 23:19:23 -0500 (EST) Received: by canoe.dclg.ca (Postfix, from userid 101) id CFBA750840; Sun, 7 Jan 2007 23:19:23 -0500 (EST) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17825.50763.781656.393704@canoe.dclg.ca> Date: Sun, 7 Jan 2007 23:19:23 -0500 To: Dan Nelson In-Reply-To: <20070108033046.GA41724@dan.emsphone.com> References: <17825.44456.556954.545497@canoe.dclg.ca> <20070108033046.GA41724@dan.emsphone.com> X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid Cc: freebsd-hackers@freebsd.org, David Gilbert Subject: Re: dump reads more than restore writes? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2007 04:19:26 -0000 >>>>> "Dan" == Dan Nelson writes: Dan> If you have a lot of small files, dump may be rereading directory Dan> information. Dump has a cache option that can help, but make Dan> sure you also dump a snapshot (i.e. always use -L when using -C). Several people have suggested this, but actually it has the same behaviour when using -C (I often use -C 32). This filesystem is not mounted, so -L is not required, but I do use -L when required. But the filesystem is 95% full (aren't they all) and the vast majority of the files on it are "media" files --- ie: movies, mp3's, ISOs, etc. Very few files under a meg. Probably not too many files over 100 meg as most of the files on the disk are in rar format. ... now Azurus (used to obtain most of the files) writes holey files. One chunk at a time (512k-ish to 4meg-ish). Those could end up being not-very-contiguous, but I'd expect them to consist (by majority) of full filesystem blocks. The amazing part (to me) is how consistent it is. If this is not a reporting error of gstat, it makes dump look _very_ wasteful. If the numbers are being reported correctly, it means that dump is reading 600 gig to copy a 200 gig disk. !?! Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================ From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 8 00:30:19 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2419A16A403 for ; Mon, 8 Jan 2007 00:30:19 +0000 (UTC) (envelope-from SRS0=xtncvP=GR=vvelox.net=vvelox@yourhostingaccount.com) Received: from mailout07.yourhostingaccount.com (mailout07.yourhostingaccount.com [65.254.253.56]) by mx1.freebsd.org (Postfix) with ESMTP id EA59713C442 for ; Mon, 8 Jan 2007 00:30:18 +0000 (UTC) (envelope-from SRS0=xtncvP=GR=vvelox.net=vvelox@yourhostingaccount.com) Received: from scan07.yourhostingaccount.com ([10.1.1.237] helo=scan07.yourhostingaccount.com) by mailout07.yourhostingaccount.com with esmtp (Exim) id 1H3hv9-0001hI-NC for freebsd-hackers@freebsd.org; Sun, 07 Jan 2007 18:59:23 -0500 Received: from authsmtp10.yourhostingaccount.com ([10.1.18.10] ident=exim) by scan07.yourhostingaccount.com with spamscanlookuphost (Exim) id 1H3hv9-0007Fi-J8 for freebsd-hackers@freebsd.org; Sun, 07 Jan 2007 18:59:23 -0500 Received: from authsmtp10.yourhostingaccount.com ([10.1.18.10] helo=authsmtp10.yourhostingaccount.com) by scan07.yourhostingaccount.com with esmtp (Exim) id 1H3hv9-0007Ff-8y for freebsd-hackers@freebsd.org; Sun, 07 Jan 2007 18:59:23 -0500 Received: from [69.92.217.33] (helo=vixen42) by authsmtp10.yourhostingaccount.com with esmtpsa (TLSv1:DES-CBC3-SHA:168) (Exim) id 1H3hv8-00063G-Pk for freebsd-hackers@freebsd.org; Sun, 07 Jan 2007 18:59:23 -0500 Date: Sun, 7 Jan 2007 17:59:35 -0600 From: "Z.C.B." To: freebsd-hackers@freebsd.org Message-ID: <20070107175935.753132f3@vixen42> X-Mailer: Claws Mail 2.6.1 (GTK+ 2.10.7; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_16Vd_DBNLiQAVQ/NfqxQ1iK"; protocol="application/pgp-signature"; micalg=PGP-SHA1 X-EN-UserInfo: f1c157ec5ebebd12a8182d58c6ceecd9:1570f0de6936c69fef9e164fffc541bc X-EN-AuthUser: vvelox3 Sender: "Z.C.B." X-Mailman-Approved-At: Mon, 08 Jan 2007 04:19:32 +0000 Subject: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2007 00:30:19 -0000 --Sig_16Vd_DBNLiQAVQ/NfqxQ1iK Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable I was just wondering. How many people here have given lots of though about integrating FreeBSD configuration with LDAP. I've just begun looking at it a lot more and was curious as to what other people think in this area. --Sig_16Vd_DBNLiQAVQ/NfqxQ1iK Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFoYlpC1tfcMGJid4RAoN3AJ9t92YquygAevfSRHWddNf2cFxezgCgkObw ofb4ccnl00DWR5hZUX7h0Eg= =oXnw -----END PGP SIGNATURE----- --Sig_16Vd_DBNLiQAVQ/NfqxQ1iK-- From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 8 06:02:36 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8E9F716A407 for ; Mon, 8 Jan 2007 06:02:36 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with SMTP id 2EC3713C442 for ; Mon, 8 Jan 2007 06:02:35 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 23099 invoked by uid 399); 8 Jan 2007 06:02:34 -0000 Received: from localhost (HELO ?192.168.0.5?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 8 Jan 2007 06:02:34 -0000 X-Originating-IP: 127.0.0.1 Message-ID: <45A1DE76.7000201@FreeBSD.org> Date: Sun, 07 Jan 2007 22:02:30 -0800 From: Doug Barton Organization: http://www.freebsd.org/ User-Agent: Thunderbird 1.5.0.8 (X11/20061215) MIME-Version: 1.0 To: Vulpes Velox References: <20070107190616.73dee7b0@vixen42> In-Reply-To: <20070107190616.73dee7b0@vixen42> X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2007 06:02:36 -0000 Vulpes Velox wrote: > I was just wondering. How many people here have given lots of though > about integrating FreeBSD configuration with LDAP. I've just begun > looking at it a lot more and was curious as to what other people > think in this area. It would be more useful to have this discussion if you defined what you meant by "FreeBSD configuration" in more detail. You might also want to search the archives first, there is a lot of discussion about various proposals in this area, all of which end up getting shot down because they don't offer sufficient added value to justify the pain of the change. hth, Doug -- This .signature sanitized for your protection From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 8 08:23:58 2007 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.ORG Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BD8D016A407 for ; Mon, 8 Jan 2007 08:23:58 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.freebsd.org (Postfix) with ESMTP id 4A34913C441 for ; Mon, 8 Jan 2007 08:23:57 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (eryjgx@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id l088Ng7p082553; Mon, 8 Jan 2007 09:23:47 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id l088Nfqe082552; Mon, 8 Jan 2007 09:23:41 +0100 (CET) (envelope-from olli) Date: Mon, 8 Jan 2007 09:23:41 +0100 (CET) Message-Id: <200701080823.l088Nfqe082552@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hackers@FreeBSD.ORG, dgilbert@dclg.ca, perryh@pluto.rain.com In-Reply-To: <45a1c260./gHVPL2TJkCotGTS%perryh@pluto.rain.com> X-Newsgroups: list.freebsd-hackers User-Agent: tin/1.8.2-20060425 ("Shillay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Mon, 08 Jan 2007 09:23:48 +0100 (CET) Cc: Subject: Re: dump reads more than restore writes? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-hackers@FreeBSD.ORG, dgilbert@dclg.ca, perryh@pluto.rain.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2007 08:23:58 -0000 perryh@pluto.rain.com wrote: > [...] > > Is dump reading substantially more than restore is writing? > > Quite possibly, esp. if the source disk is nowhere near full and/or > most of the files being handled are small. dump reads every inode > on the disk, including those which are unallocated, I don't think it does that. Why should it read inodes that are unallocated? It reads the directory tree of the file system, so it knows which inodes are allocated, and there's no reason to read anything beyond that. However, it is true that dump|restore is a slow way to copy a file system. It's much faster to mount it and then use something like "cd $SRC; find -d . | cpio -dump $DST", or cpdup (from ports/sysutils/cpdup), or even tar. If the file systems are the same size and nearly full, then dd(1) is probably the fastest way to copy it (but neither of them must be mounted, of course). If it's not nearly full, dd is inefficient because it simply copies the device without regard to what areas are actually unallocated to files. However, I think that there must be a bug in gstat when it displays 600 GB read to copy a 200 GB file system. dump(8) is inefficient, but not _that_ inefficient. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "anyone new to programming should be kept as far from C++ as possible; actually showing the stuff should be considered a criminal offence" -- Jacek Generowicz From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 8 08:46:40 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 34BAE16A417 for ; Mon, 8 Jan 2007 08:46:40 +0000 (UTC) (envelope-from vanhu@zeninc.net) Received: from smtp.zeninc.net (reverse-25.fdn.fr [80.67.176.25]) by mx1.freebsd.org (Postfix) with ESMTP id ECDF413C461 for ; Mon, 8 Jan 2007 08:46:39 +0000 (UTC) (envelope-from vanhu@zeninc.net) Received: by smtp.zeninc.net (smtpd, from userid 1000) id DBF513F17; Mon, 8 Jan 2007 09:21:21 +0100 (CET) Date: Mon, 8 Jan 2007 09:21:21 +0100 From: VANHULLEBUS Yvan To: freebsd-hackers@freebsd.org Message-ID: <20070108082121.GA10185@zen.inc> References: <20070107175935.753132f3@vixen42> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070107175935.753132f3@vixen42> User-Agent: All mail clients suck. This one just sucks less. Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2007 08:46:40 -0000 On Sun, Jan 07, 2007 at 05:59:35PM -0600, Z.C.B. wrote: > I was just wondering. How many people here have given lots of though > about integrating FreeBSD configuration with LDAP. I've just begun > looking at it a lot more and was curious as to what other people > think in this area. Hi. What do you want exactly to "integrate" in LDAP ? If you mean using a FreeBSD workstation whith users stored in an extrenal LDAP, yes, it works correctly, and it is not really more difficult than with a Linux box... Yvan. -- NETASQ http://www.netasq.com From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 8 09:05:31 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 56EFF16A40F for ; Mon, 8 Jan 2007 09:05:31 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.239]) by mx1.freebsd.org (Postfix) with ESMTP id 1947213C455 for ; Mon, 8 Jan 2007 09:05:30 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: by wr-out-0506.google.com with SMTP id i22so1239710wra for ; Mon, 08 Jan 2007 01:05:30 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ChCvesuvlgQv1iF4xRxixtfeloAE+EP/Y3XIUyrKxlXW5y/8j6sqlnhdOGFdACMhhADgk9G0WFjOpC2YTUsgcPgGq2B2GR0jjv3ZfbZUldEzHT6WyI7OLx7sy16yLYaAhoSR/52jbE7csOqMAiPC35B+A5ZrA8qnRqu844errZo= Received: by 10.78.205.7 with SMTP id c7mr3931913hug.1168245451295; Mon, 08 Jan 2007 00:37:31 -0800 (PST) Received: by 10.78.165.8 with HTTP; Mon, 8 Jan 2007 00:37:31 -0800 (PST) Message-ID: <7ad7ddd90701080037p3ade4c12tca3163d3de1aeef7@mail.gmail.com> Date: Mon, 8 Jan 2007 09:37:31 +0100 From: "Ulrich Spoerlein" To: freebsd-hackers@freebsd.org, dgilbert@dclg.ca, perryh@pluto.rain.com In-Reply-To: <200701080823.l088Nfqe082552@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <45a1c260./gHVPL2TJkCotGTS%perryh@pluto.rain.com> <200701080823.l088Nfqe082552@lurza.secnetix.de> Cc: Subject: Re: dump reads more than restore writes? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2007 09:05:31 -0000 On 1/8/07, Oliver Fromme wrote: > However, I think that there must be a bug in gstat when it > displays 600 GB read to copy a 200 GB file system. dump(8) > is inefficient, but not _that_ inefficient. When doing the dump|restore dance to copy filesystems, I make it a habit to have iostat(1) running. It is _always_ displaying a read rate twice as high as the write rate. And since the iostat/gstat numbers usually match up, eg., dd(1) numbers, I heavily doubt that it's a reporting/statistics glitch. It has to be dump(8). Uli From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 8 10:21:50 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3629016A403 for ; Mon, 8 Jan 2007 10:21:50 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from s200aog11.obsmtp.com (s200aog11.obsmtp.com [207.126.144.125]) by mx1.freebsd.org (Postfix) with SMTP id 7F73C13C45B for ; Mon, 8 Jan 2007 10:21:49 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from source ([217.206.187.80]) by eu1sys200aob011.postini.com ([207.126.147.11]) with SMTP; Mon, 08 Jan 2007 10:21:48 UTC Received: from [10.0.0.79] (bwb.mintel.co.uk [10.0.0.79]) by rodney.mintel.co.uk (Postfix) with ESMTP id 12C1518141D; Mon, 8 Jan 2007 09:54:39 +0000 (GMT) Message-ID: <45A21491.3010704@tomjudge.com> Date: Mon, 08 Jan 2007 09:53:21 +0000 From: Tom Judge User-Agent: Thunderbird 1.5.0.7 (X11/20060922) MIME-Version: 1.0 To: VANHULLEBUS Yvan References: <20070107175935.753132f3@vixen42> <20070108082121.GA10185@zen.inc> In-Reply-To: <20070108082121.GA10185@zen.inc> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2007 10:21:50 -0000 VANHULLEBUS Yvan wrote: > On Sun, Jan 07, 2007 at 05:59:35PM -0600, Z.C.B. wrote: >> I was just wondering. How many people here have given lots of though >> about integrating FreeBSD configuration with LDAP. I've just begun >> looking at it a lot more and was curious as to what other people >> think in this area. > > Hi. > > What do you want exactly to "integrate" in LDAP ? > > If you mean using a FreeBSD workstation whith users stored in an > extrenal LDAP, yes, it works correctly, and it is not really more > difficult than with a Linux box... > I would recommend the "LDAP System Administration" book published by O'Reilly. Our LDAP directory currently controls most of the core system for both FreeBSD and Linux Systems (Users/Groups, Mail Delivery/Routing, Sudo access rights, SSH Public keys). Tom From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 8 11:26:29 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3FB1216A492 for ; Mon, 8 Jan 2007 11:26:29 +0000 (UTC) (envelope-from dave@horsfall.org) Received: from dave.horsfall.org (mrdavi2.lnk.telstra.net [139.130.75.233]) by mx1.freebsd.org (Postfix) with ESMTP id D3B3A13C4A7 for ; Mon, 8 Jan 2007 11:26:27 +0000 (UTC) (envelope-from dave@horsfall.org) Received: from localhost (dave@localhost) by dave.horsfall.org (8.11.4/8.11.4) with ESMTP id l08BQPh05498 for ; Mon, 8 Jan 2007 22:26:25 +1100 (EST) Date: Mon, 8 Jan 2007 22:26:24 +1100 (EST) From: Dave Horsfall To: FreeBSD Hackers In-Reply-To: <45A21491.3010704@tomjudge.com> Message-ID: References: <20070107175935.753132f3@vixen42> <20070108082121.GA10185@zen.inc> <45A21491.3010704@tomjudge.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2007 11:26:29 -0000 On Mon, 8 Jan 2007, Tom Judge wrote: > I would recommend the "LDAP System Administration" book published by > O'Reilly. I wouldn't, unless a recipe book is your style; there are better books (which will have to wait until I get into work tomorrow). Out of all the O'Reilly books I have, the LDAP one was the most useless. -- Dave From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 8 11:57:14 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B7FC616A40F for ; Mon, 8 Jan 2007 11:57:14 +0000 (UTC) (envelope-from dave@horsfall.org) Received: from dave.horsfall.org (mrdavi2.lnk.telstra.net [139.130.75.233]) by mx1.freebsd.org (Postfix) with ESMTP id 5292113C44B for ; Mon, 8 Jan 2007 11:57:12 +0000 (UTC) (envelope-from dave@horsfall.org) Received: from localhost (dave@localhost) by dave.horsfall.org (8.11.4/8.11.4) with ESMTP id l08BvB705570 for ; Mon, 8 Jan 2007 22:57:11 +1100 (EST) Date: Mon, 8 Jan 2007 22:57:10 +1100 (EST) From: Dave Horsfall To: FreeBSD Hackers In-Reply-To: Message-ID: References: <20070107175935.753132f3@vixen42> <20070108082121.GA10185@zen.inc> <45A21491.3010704@tomjudge.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2007 11:57:14 -0000 On Mon, 8 Jan 2007, Dave Horsfall wrote: > Out of all the O'Reilly books I have, the LDAP one was the most useless. I forgot to say, "and out of all the LDAP books I have *as well*". -- Dave From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 8 12:11:39 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9854F16A40F for ; Mon, 8 Jan 2007 12:11:39 +0000 (UTC) (envelope-from bob@tamara-b.org) Received: from l2mail1.panix.com (l2mail1.panix.com [166.84.1.75]) by mx1.freebsd.org (Postfix) with ESMTP id 44E6D13C44C for ; Mon, 8 Jan 2007 12:11:37 +0000 (UTC) (envelope-from bob@tamara-b.org) Received: from mail2.panix.com (mail2.panix.com [166.84.1.73]) by l2mail1.panix.com (Postfix) with ESMTP id 0D1B75FA7F for ; Mon, 8 Jan 2007 06:54:15 -0500 (EST) Received: from mailspool3.panix.com (mailspool3.panix.com [166.84.1.78]) by mail2.panix.com (Postfix) with ESMTP id 8D4BECACE6 for ; Mon, 8 Jan 2007 06:54:14 -0500 (EST) Received: from tania.servebbs.org (pool-71-247-37-145.nycmny.east.verizon.net [71.247.37.145]) by mailspool3.panix.com (Postfix) with ESMTP id CC65F10594A5 for ; Mon, 8 Jan 2007 06:54:14 -0500 (EST) Date: Mon, 8 Jan 2007 06:54:58 -0500 From: Bob To: freebsd-hackers@freebsd.org Message-ID: <20070108065458.558b98d2@tania.servebbs.org> Organization: Tamara B X-Mailer: Claws Mail 2.6.1 (GTK+ 2.10.6; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: discrepancy between WV2 and LIBGSF Header files? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2007 12:11:39 -0000 Greetings: Let me preface this by saying that I am not C programmer. I am running on FreeBSD 6.1-RELEASE-p10, and my ports and source trees are up to date. While attempting to compile koffice-1.6.1 I ran into this error: In file included from /usr/local/include/wv2/olestream.h:22, from graphicshandler.cpp:23: The offending code is in the file /usr/local/include/wv2/olestorage.h and reads: #include I have libgsf-1.14.1 installed and it installs gsf.h at: /usr/local/include/libgsf-1/gsf/gsf.h I also have wv2-0.2.3 Installed To fix this error, I edited the file /usr/local/include/wv2/olestorage.h and changed: #include to #include This fixed the error. There seems to be a discrepancy between WV2 and LIBGSF as to the proper location of gsf.h Either that, or my installation is not correct. Can someone either tell me who to report this to, or go ahead and report this to the proper maintainer? Perhaps the maintainer of koffice should add a patch? What is strange, and bothers me is that koffice 1.6.1 has been released for a while now, and nobody has run into this? Surely I am not the first to build koffice from sources. Best Regards Bob From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 8 12:35:34 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2474916A492 for ; Mon, 8 Jan 2007 12:35:34 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) Received: from pobox.codelabs.ru (pobox.codelabs.ru [144.206.177.45]) by mx1.freebsd.org (Postfix) with ESMTP id EA4A513C45A for ; Mon, 8 Jan 2007 12:35:32 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) Received: from codelabs.ru (pobox.codelabs.ru [144.206.177.45]) by pobox.codelabs.ru with esmtpsa (TLSv1:AES256-SHA:256) id 1H3tis-000ICq-JJ; Mon, 08 Jan 2007 15:35:30 +0300 Date: Mon, 8 Jan 2007 15:35:25 +0300 From: Eygene Ryabinkin To: Bob Message-ID: <20070108123525.GM37482@codelabs.ru> References: <20070108065458.558b98d2@tania.servebbs.org> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20070108065458.558b98d2@tania.servebbs.org> Sender: rea-fbsd@codelabs.ru X-Spam-Status: No, score=-3.4 required=4.0 tests=ALL_TRUSTED,AWL,BAYES_00 Cc: freebsd-hackers@freebsd.org Subject: Re: discrepancy between WV2 and LIBGSF Header files? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2007 12:35:34 -0000 Bob, good day! I doubt that this posting should go into the freebsd-hackers, but nevertheless ;)) > While attempting to compile koffice-1.6.1 I ran into this error: > > In file included from /usr/local/include/wv2/olestream.h:22, > from graphicshandler.cpp:23: > > The offending code is in the file /usr/local/include/wv2/olestorage.h > and reads: > #include > > I have libgsf-1.14.1 installed and it installs gsf.h at: > /usr/local/include/libgsf-1/gsf/gsf.h > > I also have wv2-0.2.3 Installed > > To fix this error, I edited the file /usr/local/include/wv2/olestorage.h > and changed: > #include > to > #include Please, undo these changes and try to build your port with command 'CFLAGS=-I/usr/local/include/libgsf-1 make clean install clean'. This should clean your build, point the preprocessor to the right location of the gsf/gsf.h, build your port once again, install it and clean the build area. > Can someone either tell me who to report this to, or go ahead and > report this to the proper maintainer? Perhaps the maintainer of koffice > should add a patch? PRs are welcome: they are made through send-pr utility. The maintainer for the port can be looked up using the following command: $ grep MAINTAINER /usr/ports/editors/koffice-kde3/Makefile MAINTAINER= kde@FreeBSD.org You can Cc your problem report to him. And if 'CFLAGS' trick will do the work, you can mention it in the report. But previous to sending the PR, look into the PR database: maybe your bug is already reported, but was not handled yet. See http://www.freebsd.org/send-pr.html for the long explanation and links. -- Eygene From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 8 08:31:16 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6848116A407 for ; Mon, 8 Jan 2007 08:31:16 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from redbull.bpaserver.net (redbullneu.bpaserver.net [213.198.78.217]) by mx1.freebsd.org (Postfix) with ESMTP id 18C5313C468 for ; Mon, 8 Jan 2007 08:31:16 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from outgoing.leidinger.net (p54A5D130.dip.t-dialin.net [84.165.209.48]) by redbull.bpaserver.net (Postfix) with ESMTP id 6D55C2E18F; Mon, 8 Jan 2007 09:36:34 +0100 (CET) Received: from webmail.leidinger.net (webmail.Leidinger.net [192.168.1.102]) by outgoing.leidinger.net (Postfix) with ESMTP id D0C045B497E; Mon, 8 Jan 2007 09:31:09 +0100 (CET) Received: (from www@localhost) by webmail.leidinger.net (8.13.8/8.13.8/Submit) id l088V9uM093620; Mon, 8 Jan 2007 09:31:09 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from pslux.cec.eu.int (pslux.cec.eu.int [158.169.9.14]) by webmail.leidinger.net (Horde MIME library) with HTTP; Mon, 08 Jan 2007 09:31:09 +0100 Message-ID: <20070108093109.6xq4kzr7k040sg00@webmail.leidinger.net> X-Priority: 3 (Normal) Date: Mon, 08 Jan 2007 09:31:09 +0100 From: Alexander Leidinger To: Doug Barton References: <20070107190616.73dee7b0@vixen42> <45A1DE76.7000201@FreeBSD.org> In-Reply-To: <45A1DE76.7000201@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) H3 (4.1.3) / FreeBSD-7.0 X-BPAnet-MailScanner-Information: Please contact the ISP for more information X-BPAnet-MailScanner: Found to be clean X-BPAnet-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-14.864, required 6, autolearn=not spam, BAYES_00 -15.00, DK_POLICY_SIGNSOME 0.00, FORGED_RCVD_HELO 0.14) X-BPAnet-MailScanner-From: alexander@leidinger.net X-Spam-Status: No X-Mailman-Approved-At: Mon, 08 Jan 2007 12:38:09 +0000 Cc: freebsd-hackers@FreeBSD.org, Vulpes Velox Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2007 08:31:16 -0000 Quoting Doug Barton (from Sun, 07 Jan 2007 =20 22:02:30 -0800): > Vulpes Velox wrote: >> I was just wondering. How many people here have given lots of though >> about integrating FreeBSD configuration with LDAP. I've just begun >> looking at it a lot more and was curious as to what other people >> think in this area. > > It would be more useful to have this discussion if you defined what > you meant by "FreeBSD configuration" in more detail. You might also > want to search the archives first, there is a lot of discussion about > various proposals in this area, all of which end up getting shot down > because they don't offer sufficient added value to justify the pain of > the change. I had the impression that in general the opinion is that it would be =20 nice to have it in the tree, but that the generic infrastructure =20 should be committed first (the GSoC 2006 nss work without the LDAP =20 part) and then a patch should be presented to let the people have a =20 look at the complete picture. Bye, Alexander. --=20 It's a poor workman who blames his tools. http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID =3D B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID =3D 72077137 From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 8 19:21:01 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6245816A8A5; Mon, 8 Jan 2007 19:21:01 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.freebsd.org (Postfix) with ESMTP id 20A8C13C457; Mon, 8 Jan 2007 19:20:43 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id l08JKDdm068399; Mon, 8 Jan 2007 14:20:34 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Oliver Fromme Date: Mon, 8 Jan 2007 14:20:06 -0500 User-Agent: KMail/1.9.1 References: <200701061927.l06JRWoB095827@lurza.secnetix.de> In-Reply-To: <200701061927.l06JRWoB095827@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200701081420.07376.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Mon, 08 Jan 2007 14:20:35 -0500 (EST) X-Virus-Scanned: ClamAV 0.88.3/2424/Mon Jan 8 11:46:49 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: erik.udo@gmail.com, freebsd-hackers@freebsd.org, dougb@freebsd.org Subject: Re: Init.c, making it chroot X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2007 19:21:01 -0000 On Saturday 06 January 2007 14:27, Oliver Fromme wrote: > M. Warner Losh wrote: > > Also, kenv(KENV_GET, ... is used a lot. Maybe it makes sense to have > > a simple kenvget call. Would make a few lines a little shorter if > > nothing else. > > KENV_GET is used three times. Using a wrapper function > would save 7 characters per call. I don't think it's > really worth it. But if you insist, I can update the > patch with such a function. I think just using kenv() is fine. -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 8 20:01:26 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 24A2916A417 for ; Mon, 8 Jan 2007 20:01:26 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from multiplay.co.uk (core6.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 1BC2B13C46A for ; Mon, 8 Jan 2007 20:01:24 +0000 (UTC) (envelope-from killing@multiplay.co.uk) X-Spam-Checker-Version: SpamAssassin 3.1.5 (2006-08-29) on core6.multiplay.co.uk X-Spam-Level: X-Spam-Status: No, score=-24.7 required=6.0 tests=BAYES_00, USER_IN_WHITELIST, USER_IN_WHITELIST_TO autolearn=ham version=3.1.5 Received: from vader ([212.135.219.179]) by multiplay.co.uk (multiplay.co.uk [85.236.96.23]) (MDaemon PRO v9.5.4) with ESMTP id md50003369924.msg; Mon, 08 Jan 2007 19:58:46 +0000 Message-ID: <066101c7335f$611c41e0$b3db87d4@multiplay.co.uk> From: "Steven Hartland" To: , Date: Mon, 8 Jan 2007 19:58:26 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3028 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 X-MDRemoteIP: 212.135.219.179 X-Return-Path: killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-Spam-Processed: multiplay.co.uk, Mon, 08 Jan 2007 19:58:47 +0000 X-MDAV-Processed: multiplay.co.uk, Mon, 08 Jan 2007 19:58:47 +0000 Cc: Subject: Slow FreeBSD -> Windows performance with inflight enabled X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2007 20:01:26 -0000 I've just been looking at an issue reported by some of our users that downloads from our one of our sites run on FreeBSD 6.1 and Apache 1.3 where strangely slow. After doing some digging around I found that two remote machines on the same network had wildly different results. The difference being one was Windows (slow) and one was FreeBSD 6.1 (fast). The results where 380Kb/s download speeds on Windows vs 500Kb/s on FreeBSD. I played around and Googled to find that this appears to caused by inflight. Disabling it and restarting apache cures the problem. This has been mentioned a few times in the past e.g. http://lists.freebsd.org/pipermail/freebsd-stable/2006-February/022622.html http://lists.freebsd.org/pipermail/freebsd-net/2005-November/008989.html But I cant find any real conclusive results. For reference the connection between the test machines is initially GE on both ends but at one point goes via DSL but is still relatively low latency the trace being: Host Loss% Snt Last Avg Best Wrst StDev 1. x.x.x.x 0.0% 12 0.3 0.3 0.3 0.3 0.0 2. x.x.x.x 0.0% 12 0.4 0.4 0.4 0.4 0.0 3. x.x.x.x 8.3% 12 1.4 1.7 1.3 3.1 0.6 4. x.x.x.x 0.0% 11 5.5 10.1 5.5 21.6 5.9 5. x.x.x.x 0.0% 11 7.6 6.8 6.3 7.6 0.3 6. x.x.x.x 0.0% 11 7.7 7.2 6.7 8.1 0.4 Looking at the before and after traces using wireshark on the windows box there are no notable changes just an increased throughput in exchanges. Possibly of note is that the server in question is running a 200HZ kernel. With the common client being Windows I'd say it would be good to get the default improved either by disabling inflight or changing it so that it better detects this sort of common connection arrangement. Does anyone have any ideas why inflight is causing such poor performance? Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 8 20:19:41 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5329216A412 for ; Mon, 8 Jan 2007 20:19:41 +0000 (UTC) (envelope-from victorloureirolima@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.244]) by mx1.freebsd.org (Postfix) with ESMTP id 15F7513C43E for ; Mon, 8 Jan 2007 20:19:40 +0000 (UTC) (envelope-from victorloureirolima@gmail.com) Received: by an-out-0708.google.com with SMTP id c24so2181347ana for ; Mon, 08 Jan 2007 12:19:40 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=ryGhXAAqa8HuRSIoUApH95lp9UwAtnCWzixxFp3Ews3xXYpoAW+VWjFTQEgGM+9wAEJYWEzTLfEcV6JmZKNMtlJpsNNgdaVk6N52au7h31VvO+ZEJf9HwzWqkhvSgzaOrezMd7xr6KJFO2HD2qaH9GINmA0l/wqorXLAlwTJVho= Received: by 10.100.7.18 with SMTP id 18mr10176290ang.1168285959868; Mon, 08 Jan 2007 11:52:39 -0800 (PST) Received: by 10.100.109.16 with HTTP; Mon, 8 Jan 2007 11:52:39 -0800 (PST) Message-ID: Date: Mon, 8 Jan 2007 16:52:39 -0300 From: "Victor Loureiro Lima" To: freebsd-hackers@freebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_5513_18887186.1168285959825" References: X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Fwd: [patch] - random(6) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2007 20:19:41 -0000 ------=_Part_5513_18887186.1168285959825 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline I am forwarding this to -hackers, since I havent got any response from the author (seanc@freebsd.org) in months ;/ Maybe someone in here could take a few minutes and check this patch out and maybe commit it to the source tree att, victor loureiro lima ---------- Forwarded message ---------- From: Victor Loureiro Lima Date: 27/11/2006 15:19 Subject: [patch] - random(6) To: seanc@freebsd.org Hello Sean, My name is Victor, I've sent you a patch which solved the "bug" in which random(6) would be way to slow to handle files that are greater than 10MB+, well, I am re-sending you that same patch with little modifications, do you think you could include it in the src tree? This patch also increases random(6) performance dramatically even when working with small-to-medium file sizes, it should be a good addition to the random(6) source tree, and its also been extensivelly tested against all features of random(6) and it scale really well with big files, for example: -- setuid@zion$ yes | head -200000 > test setuid@zion$ time ./random -f test > /dev/null 0.257u 0.015s 0:00.27 96.2% 11+14460k 0+0io 0pf+0w setuid@zion$ time random -f test > /dev/null 187.366u 0.007s 3:07.39 99.9% 10+12945k 0+0io 0pf+0w -- And this was on a Intel Core Duo 2 1.8ghz with 1GB of RAM, with one process taking less than a second to randomize it all, and the other taking 3 minutes, I think its a good patch to be applied on the source tree. I also took the time to change the man page of random(6) to better describe the changes, basically removed the BUGS sections (since that bug is solved by the patch) and included a new line on the HISTORY section describing my contribution to the program :). Attached are the patches for randomize_fd.c and random.6, also a little description of the changes made in randomize_fd.c is in the readme file. Hope you find that this is patch is commitable, I would appreciate to have contributed to FreeBSD even if its just this little contribution :) ciao, victor loureiro lima ------=_Part_5513_18887186.1168285959825-- From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 8 19:48:52 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id ADC3716A40F; Mon, 8 Jan 2007 19:48:52 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.freebsd.org (Postfix) with ESMTP id 1FD5913C442; Mon, 8 Jan 2007 19:48:51 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (qpszcd@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id l08JmeRU069498; Mon, 8 Jan 2007 20:48:46 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id l08JmeS5069496; Mon, 8 Jan 2007 20:48:40 +0100 (CET) (envelope-from olli) From: Oliver Fromme Message-Id: <200701081948.l08JmeS5069496@lurza.secnetix.de> To: jhb@freebsd.org (John Baldwin) Date: Mon, 8 Jan 2007 20:48:40 +0100 (CET) In-Reply-To: <200701081420.07376.jhb@freebsd.org> X-Mailer: ELM [version 2.5 PL8] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Mon, 08 Jan 2007 20:48:46 +0100 (CET) X-Mailman-Approved-At: Mon, 08 Jan 2007 20:30:17 +0000 Cc: erik.udo@gmail.com, freebsd-hackers@freebsd.org, dougb@freebsd.org Subject: Re: Init.c, making it chroot X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2007 19:48:52 -0000 John Baldwin wrote: > On Saturday 06 January 2007 14:27, Oliver Fromme wrote: > > M. Warner Losh wrote: > > > Also, kenv(KENV_GET, ... is used a lot. Maybe it makes sense to have > > > a simple kenvget call. Would make a few lines a little shorter if > > > nothing else. > > > > KENV_GET is used three times. Using a wrapper function > > would save 7 characters per call. I don't think it's > > really worth it. But if you insist, I can update the > > patch with such a function. > > I think just using kenv() is fine. OK, so how do we proceed now? Should I submit a PR containing the patch? I'm also willing to write a bit of documentation for the new init_* kenv variables, but I'm not sure where to put it. The existing init_path variable is documented in loader(8), so maybe it should go there? Also there should be sample entries in /boot/defaults/loader.conf, of course, like this: --- loader.conf.orig Mon Jan 8 20:45:23 2007 +++ loader.conf Mon Jan 8 20:47:48 2007 @@ -77,6 +77,9 @@ #boot_verbose="" # -v: Causes extra debugging information to be printed #init_path="/sbin/init:/sbin/oinit:/sbin/init.bak:/rescue/init:/stand/sysinstall" # Sets the list of init candidates +#init_shell="/bin/sh" # The shell binary used by init(8). +#init_shript="" # Initial script to run by init(8) before chrooting. +#init_chroot="" # Directory for init(8) to chroot into. ############################################################## By the way, I just verified in the CVS repository that the init.c code is identical in HEAD (1.62) and in RELENG_6 (1.60.2.2). Therefore the patch should apply cleanly to both HEAD and RELENG_6. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 8 21:07:15 2007 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3783B16A415; Mon, 8 Jan 2007 21:07:15 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id B6D8413C455; Mon, 8 Jan 2007 21:07:14 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id l08L44tb019718; Mon, 8 Jan 2007 14:04:05 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 08 Jan 2007 14:04:17 -0700 (MST) Message-Id: <20070108.140417.1176919806.imp@bsdimp.com> To: olli@lurza.secnetix.de From: "M. Warner Losh" In-Reply-To: <200701081948.l08JmeS5069496@lurza.secnetix.de> References: <200701081420.07376.jhb@freebsd.org> <200701081948.l08JmeS5069496@lurza.secnetix.de> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Mon, 08 Jan 2007 14:04:07 -0700 (MST) Cc: erik.udo@gmail.com, freebsd-hackers@FreeBSD.org, dougb@FreeBSD.org, jhb@FreeBSD.org Subject: Re: Init.c, making it chroot X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2007 21:07:15 -0000 In message: <200701081948.l08JmeS5069496@lurza.secnetix.de> Oliver Fromme writes: : : John Baldwin wrote: : > On Saturday 06 January 2007 14:27, Oliver Fromme wrote: : > > M. Warner Losh wrote: : > > > Also, kenv(KENV_GET, ... is used a lot. Maybe it makes sense to have : > > > a simple kenvget call. Would make a few lines a little shorter if : > > > nothing else. : > > : > > KENV_GET is used three times. Using a wrapper function : > > would save 7 characters per call. I don't think it's : > > really worth it. But if you insist, I can update the : > > patch with such a function. : > : > I think just using kenv() is fine. : : OK, so how do we proceed now? : Should I submit a PR containing the patch? Send me the final patch as an attachment to an email, and I'll make sure it gets committed. Warner : I'm also willing to write a bit of documentation for the : new init_* kenv variables, but I'm not sure where to put : it. The existing init_path variable is documented in : loader(8), so maybe it should go there? Also there should : be sample entries in /boot/defaults/loader.conf, of course, : like this: Both ideas are good. : --- loader.conf.orig Mon Jan 8 20:45:23 2007 : +++ loader.conf Mon Jan 8 20:47:48 2007 : @@ -77,6 +77,9 @@ : #boot_verbose="" # -v: Causes extra debugging information to be printed : #init_path="/sbin/init:/sbin/oinit:/sbin/init.bak:/rescue/init:/stand/sysinstall" : # Sets the list of init candidates : +#init_shell="/bin/sh" # The shell binary used by init(8). : +#init_shript="" # Initial script to run by init(8) before chrooting. : +#init_chroot="" # Directory for init(8) to chroot into. : : : ############################################################## : : By the way, I just verified in the CVS repository that the : init.c code is identical in HEAD (1.62) and in RELENG_6 : (1.60.2.2). Therefore the patch should apply cleanly to : both HEAD and RELENG_6. Excellent! I look forward to it. BTW, if you have other patches/PRs, please contact me privately and I'll review/commit them. Warner : Best regards : Oliver : : -- : Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing : Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd : Any opinions expressed in this message may be personal to the author : and may not necessarily reflect the opinions of secnetix in any way. : : 'Instead of asking why a piece of software is using "1970s technology," : start asking why software is ignoring 30 years of accumulated wisdom.' : : From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 8 21:09:00 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 63B1416A412 for ; Mon, 8 Jan 2007 21:09:00 +0000 (UTC) (envelope-from lee@nerds.org.uk) Received: from furby.nerds.org.uk (furby.nerds.org.uk [82.70.196.65]) by mx1.freebsd.org (Postfix) with ESMTP id 08A6013C45B for ; Mon, 8 Jan 2007 21:08:59 +0000 (UTC) (envelope-from lee@nerds.org.uk) Received: from lee by furby.nerds.org.uk with local (Exim 4.65 (FreeBSD)) (envelope-from ) id 1H41AB-000B8J-4m for freebsd-hackers@freebsd.org; Mon, 08 Jan 2007 20:32:11 +0000 Date: Mon, 8 Jan 2007 20:32:11 +0000 From: Lee Brotherston To: freebsd-hackers@freebsd.org Message-ID: <20070108203211.GF41066@nerds.org.uk> MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="BOKacYhQ+x31HxR3" Content-Disposition: inline User-Agent: Mutt/1.5.13 (2006-08-11) X-Mailman-Approved-At: Mon, 08 Jan 2007 21:21:40 +0000 Subject: TCP Checksums in mbufs X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2007 21:09:00 -0000 --BOKacYhQ+x31HxR3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, I have a bit of code I have written that uses pfil to access network traffic as it passes between interfaces on a FreeBSD router. One of the functions it performs is some incredibly basic rewrites of certain packets (keeping the same length, so no issues about sequence numbers), but it does alter the payload. I just wanted to check what is the "proper" way to be going about recalculating the checksums on the packet? I can write a function to do this and write this into the packet stored in the mbuf directly, however I wasn't sure if there was a more acceptable method such as flagging it to be re-checksum'd as it's routed, or to offload the computation to the NIC or something? Any thoughts, suggestions, etc very welcome! By the way, I'm not subscribed to the list right now, so I'd appreciate it if people could CC me on replies. Many thanks Lee --=20 Lee Brotherston - --BOKacYhQ+x31HxR3 Content-Type: application/x-pkcs7-signature Content-Disposition: attachment; filename="smime.p7s" Content-Transfer-Encoding: base64 MIIIvQYJKoZIhvcNAQcCoIIIrjCCCKoCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC BjQwggLtMIICVqADAgECAhBuQYdNaKuFQWQVFA/nyFETMA0GCSqGSIb3DQEBBAUAMGIxCzAJ BgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYD VQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQTAeFw0wNjA1MDUxNTU4 NTJaFw0wNzA1MDUxNTU4NTJaMEIxHzAdBgNVBAMTFlRoYXd0ZSBGcmVlbWFpbCBNZW1iZXIx HzAdBgkqhkiG9w0BCQEWEGxlZUBuZXJkcy5vcmcudWswggEiMA0GCSqGSIb3DQEBAQUAA4IB DwAwggEKAoIBAQDZHAa7GJzL38gNE59SYrjnN+Wu2cK0fdRhCRW4/ow+UDsggQyQkUBH11Tg NaHXl488J8faed8aHAN9Djdv1nfE1hk+AvV8BF6ehZ6pYfhi/ceTP1nwX6B+fRYyoKp5dTVv pE7IRxWxeouaePGuIyzNgn/cCHxQgUP92NjK8FCi0g+xd+ZGqivVrvIlgNqWlNGJOSevELmm 2Ro8CJ2JUDkTv02fSjdL9vnhNu6uLW/T/e4jnjOYR69jIapJYDV9PlvR3i5YmTzquxmnLN0J qDGUbMtfX/mEnzerlikA9BJGuR9o0w0lgVb7x3x/8yECz9RxLoCdv2z6keX9pydr8PfvAgMB AAGjQDA+MBEGCWCGSAGG+EIBAQQEAwIFIDAbBgNVHREEFDASgRBsZWVAbmVyZHMub3JnLnVr MAwGA1UdEwEB/wQCMAAwDQYJKoZIhvcNAQEEBQADgYEAq11z0cvhjvXRd/Li144Zyg/sksZc 7z05aibMw45oOUDfA/H5ZtaN2qg6cQgj2JP7eDy3w7GYNRw38AJI7+TIGOzKs+EZbLurc3eg 7FzUmXEzEr3J9EXDsX0cVe7l6vBZmY6t+qwEHtAYTIPAo3Ka7ih7fMSRpwFi/WDJ4l963oEw ggM/MIICqKADAgECAgENMA0GCSqGSIb3DQEBBQUAMIHRMQswCQYDVQQGEwJaQTEVMBMGA1UE CBMMV2VzdGVybiBDYXBlMRIwEAYDVQQHEwlDYXBlIFRvd24xGjAYBgNVBAoTEVRoYXd0ZSBD b25zdWx0aW5nMSgwJgYDVQQLEx9DZXJ0aWZpY2F0aW9uIFNlcnZpY2VzIERpdmlzaW9uMSQw IgYDVQQDExtUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgQ0ExKzApBgkqhkiG9w0BCQEWHHBl cnNvbmFsLWZyZWVtYWlsQHRoYXd0ZS5jb20wHhcNMDMwNzE3MDAwMDAwWhcNMTMwNzE2MjM1 OTU5WjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkg THRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0EwgZ8w DQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAMSmPFVzVftOucqZWh5owHUEcJ3f6f+jHuy9zfVb 8hp2vX8MOmHyv1HOAdTlUAow1wJjWiyJFXCO3cnwK4Vaqj9xVsuvPAsH5/EfkTYkKhPPK9Xz gnc9A74r/rsYPge/QIACZNenprufZdHFKlSFD0gEf6e20TxhBEAeZBlyYLf7AgMBAAGjgZQw gZEwEgYDVR0TAQH/BAgwBgEB/wIBADBDBgNVHR8EPDA6MDigNqA0hjJodHRwOi8vY3JsLnRo YXd0ZS5jb20vVGhhd3RlUGVyc29uYWxGcmVlbWFpbENBLmNybDALBgNVHQ8EBAMCAQYwKQYD VR0RBCIwIKQeMBwxGjAYBgNVBAMTEVByaXZhdGVMYWJlbDItMTM4MA0GCSqGSIb3DQEBBQUA A4GBAEiM0VCD6gsuzA2jZqxnD3+vrL7CF6FDlpSdf0whuPg2H6otnzYvwPQcUCCTcDz9reFh YsPZOhl+hLGZGwDFGguCdJ4lUJRix9sncVcljd2pnDmOjCBPZV+V2vf3h9bGCE6u9uo05RAa WzVNd+NWIXiC3CEZNd4ksdMdRv9dX2VPMYICUTCCAk0CAQEwdjBiMQswCQYDVQQGEwJaQTEl MCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3Rl IFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEG5Bh01oq4VBZBUUD+fIURMwCQYFKw4D AhoFAKCBsTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wNzAx MDgyMDMyMTBaMCMGCSqGSIb3DQEJBDEWBBTJnpXzUgFvNUrgo0dyPKDRiiXxrzBSBgkqhkiG 9w0BCQ8xRTBDMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAH BgUrDgMCBzANBggqhkiG9w0DAgIBKDANBgkqhkiG9w0BAQEFAASCAQB67v1LgOKP0nGo7aY0 3v8UaZy758W+jzXCaH0NY+ML6mbdG7Hvzi/zu4FPtbJcJ3vihJEJGG7AJvqwKNWMRv0OU9Ic 5PSNhL0wfLODqEPbUYI5QVyNeiGQ8DrVKfBFXU2rHifSmgXNh0HzZQ8wI/4HZMnC4R8CExEG ra5PWSkdzxw0jSEefAFI4LNdktXEc8m0/hC0n+mH/lP0+LnYAiFwhr3keug4jiN7vhL6v+Zj z1Uq+L8eHkU7M5h1TdvWaUWqpb7cpmhVIVl5wsi18D44M0nvUR2ZQ5OBNBvjL3CG15R7b8lO ZBrNvx8tYl7tTAjgsp0YGICO5xnoBOd19EaH --BOKacYhQ+x31HxR3-- From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 8 22:00:22 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7699016A412 for ; Mon, 8 Jan 2007 22:00:22 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outQ.internet-mail-service.net (outQ.internet-mail-service.net [216.240.47.240]) by mx1.freebsd.org (Postfix) with ESMTP id 0616C13C45B for ; Mon, 8 Jan 2007 22:00:21 +0000 (UTC) (envelope-from julian@elischer.org) Received: from shell.idiom.com (HELO idiom.com) (216.240.47.20) by out.internet-mail-service.net (qpsmtpd/0.32) with ESMTP; Mon, 08 Jan 2007 13:41:52 -0800 Received: from [10.251.23.190] (nat.ironport.com [63.251.108.100]) by idiom.com (8.12.11/8.12.11) with ESMTP id l08M0Fjf004811; Mon, 8 Jan 2007 14:00:16 -0800 (PST) (envelope-from julian@elischer.org) Message-ID: <45A2BEEE.5010202@elischer.org> Date: Mon, 08 Jan 2007 14:00:14 -0800 From: Julian Elischer User-Agent: Thunderbird 1.5.0.9 (Macintosh/20061207) MIME-Version: 1.0 To: Lee Brotherston References: <20070108203211.GF41066@nerds.org.uk> In-Reply-To: <20070108203211.GF41066@nerds.org.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: TCP Checksums in mbufs X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2007 22:00:22 -0000 Lee Brotherston wrote: > Hi, > > I have a bit of code I have written that uses pfil to access network > traffic as it passes between interfaces on a FreeBSD router. One of > the functions it performs is some incredibly basic rewrites of certain > packets (keeping the same length, so no issues about sequence > numbers), but it does alter the payload. > > I just wanted to check what is the "proper" way to be going about > recalculating the checksums on the packet? I can write a function to > do this and write this into the packet stored in the mbuf directly, > however I wasn't sure if there was a more acceptable method such as > flagging it to be re-checksum'd as it's routed, or to offload the > computation to the NIC or something? > > Any thoughts, suggestions, etc very welcome! > > By the way, I'm not subscribed to the list right now, so I'd > appreciate it if people could CC me on replies. > > Many thanks > > Lee there is an algorythm to recalculate the tcp/ip checksum when you replace a byte. you subtract the old value from the csum and add the new one, but not quite a as easy as that. I think it's given in one of the RFCs but I think it may also be used in the tcpmss port, or possibly the mss fixup code in ppp. I know I've used it somewhere but forget where :-) From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 8 23:31:34 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E45AC16A412 for ; Mon, 8 Jan 2007 23:31:34 +0000 (UTC) (envelope-from pawel.worach@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.169]) by mx1.freebsd.org (Postfix) with ESMTP id 7DF0813C461 for ; Mon, 8 Jan 2007 23:31:34 +0000 (UTC) (envelope-from pawel.worach@gmail.com) Received: by ug-out-1314.google.com with SMTP id o2so5692030uge for ; Mon, 08 Jan 2007 15:31:33 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=us0XJs19vJNyKXygtWDmskAeU73R2IKB6bw12ox5lmvioKMgxjnsXXHpw5s/8vYUT/6GtzZVcHtXrP+RxnUMwY/Y1m3UbQUCb+SXGsrxL9XeR6mSpD1bVNGi5aVFRiWDZktcZP8o50x/SuopZwYZZh2/NI4fj4uesKFMjIUGmeA= Received: by 10.67.117.2 with SMTP id u2mr35419514ugm.1168297509274; Mon, 08 Jan 2007 15:05:09 -0800 (PST) Received: from ?192.168.1.200? ( [80.217.194.157]) by mx.google.com with ESMTP id s1sm33543459uge.2007.01.08.15.05.08; Mon, 08 Jan 2007 15:05:08 -0800 (PST) Message-ID: <45A2CE23.6040909@gmail.com> Date: Tue, 09 Jan 2007 00:05:07 +0100 From: Pawel Worach User-Agent: Thunderbird 2.0b1 (X11/20070106) MIME-Version: 1.0 To: Bob References: <20070108065458.558b98d2@tania.servebbs.org> In-Reply-To: <20070108065458.558b98d2@tania.servebbs.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: discrepancy between WV2 and LIBGSF Header files? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2007 23:31:35 -0000 Bob wrote: > > Greetings: > > Let me preface this by saying that I am not C programmer. > > I am running on FreeBSD 6.1-RELEASE-p10, and my ports and source trees > are up to date. > > While attempting to compile koffice-1.6.1 I ran into this error: > > In file included from /usr/local/include/wv2/olestream.h:22, > from graphicshandler.cpp:23: > > The offending code is in the file /usr/local/include/wv2/olestorage.h > and reads: > #include > > I have libgsf-1.14.1 installed and it installs gsf.h at: > /usr/local/include/libgsf-1/gsf/gsf.h > > I also have wv2-0.2.3 Installed > > To fix this error, I edited the file /usr/local/include/wv2/olestorage.h > and changed: > #include > to > #include > Hi, Assuming that the port uses autotools it probably runs pkg-config to get the proper CFLAGS, so make sure the output from the command below produces the right output. pkg-config --cflags libgsf-1 -- Pawel From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 9 01:01:15 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 952F716A407 for ; Tue, 9 Jan 2007 01:01:15 +0000 (UTC) (envelope-from SRS0=pr74Nt=GS=vvelox.net=v.velox@yourhostingaccount.com) Received: from mailout12.yourhostingaccount.com (mailout12.yourhostingaccount.com [65.254.253.96]) by mx1.freebsd.org (Postfix) with ESMTP id EC2E913C43E for ; Tue, 9 Jan 2007 01:01:07 +0000 (UTC) (envelope-from SRS0=pr74Nt=GS=vvelox.net=v.velox@yourhostingaccount.com) Received: from scan07.yourhostingaccount.com ([10.1.1.237] helo=scan07.yourhostingaccount.com) by mailout12.yourhostingaccount.com with esmtp (Exim) id 1H456W-0005Wv-Eh for freebsd-hackers@freebsd.org; Mon, 08 Jan 2007 19:44:40 -0500 Received: from authsmtp09.yourhostingaccount.com ([10.1.18.9] ident=exim) by scan07.yourhostingaccount.com with spamscanlookuphost (Exim) id 1H456W-0005LM-A5 for freebsd-hackers@freebsd.org; Mon, 08 Jan 2007 19:44:40 -0500 Received: from authsmtp09.yourhostingaccount.com ([10.1.18.9] helo=authsmtp09.yourhostingaccount.com) by scan07.yourhostingaccount.com with esmtp (Exim) id 1H456V-0005LG-RP for freebsd-hackers@freebsd.org; Mon, 08 Jan 2007 19:44:39 -0500 Received: from [69.92.217.33] (helo=vixen42) by authsmtp09.yourhostingaccount.com with esmtpa (Exim) id 1H456V-0001p0-Cn; Mon, 08 Jan 2007 19:44:39 -0500 Date: Mon, 8 Jan 2007 18:44:36 -0600 From: Vulpes Velox To: VANHULLEBUS Yvan Message-ID: <20070108184436.402c8769@vixen42> In-Reply-To: <20070108082121.GA10185@zen.inc> References: <20070107175935.753132f3@vixen42> <20070108082121.GA10185@zen.inc> X-Mailer: Claws Mail 2.6.1 (GTK+ 2.10.7; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-EN-UserInfo: 0d1ca1697cdb7a831d4877828571b7ab:1570f0de6936c69fef9e164fffc541bc X-EN-AuthUser: vvelox2 Sender: Vulpes Velox Cc: freebsd-hackers@freebsd.org Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jan 2007 01:01:15 -0000 On Mon, 8 Jan 2007 09:21:21 +0100 VANHULLEBUS Yvan wrote: > On Sun, Jan 07, 2007 at 05:59:35PM -0600, Z.C.B. wrote: > > I was just wondering. How many people here have given lots of > > though about integrating FreeBSD configuration with LDAP. I've > > just begun looking at it a lot more and was curious as to what > > other people think in this area. > > Hi. > > What do you want exactly to "integrate" in LDAP ? Exactly what I said. :) Initially I have been looking at rc.conf. > If you mean using a FreeBSD workstation whith users stored in an > extrenal LDAP, yes, it works correctly, and it is not really more > difficult than with a Linux box... Yeah, I am aware of it and use it myself. From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 9 01:07:53 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EDF6F16A40F for ; Tue, 9 Jan 2007 01:07:53 +0000 (UTC) (envelope-from SRS0=pr74Nt=GS=vvelox.net=v.velox@yourhostingaccount.com) Received: from mailout17.yourhostingaccount.com (mailout17.yourhostingaccount.com [65.254.253.139]) by mx1.freebsd.org (Postfix) with ESMTP id AC8A613C45D for ; Tue, 9 Jan 2007 01:07:53 +0000 (UTC) (envelope-from SRS0=pr74Nt=GS=vvelox.net=v.velox@yourhostingaccount.com) Received: from scan04.yourhostingaccount.com ([10.1.1.234] helo=scan04.yourhostingaccount.com) by mailout17.yourhostingaccount.com with esmtp (Exim) id 1H45EQ-00075X-Nz for freebsd-hackers@freebsd.org; Mon, 08 Jan 2007 19:52:50 -0500 Received: from authsmtp10.yourhostingaccount.com ([10.1.18.10] ident=exim) by scan04.yourhostingaccount.com with spamscanlookuphost (Exim) id 1H45EQ-00065G-LK for freebsd-hackers@freebsd.org; Mon, 08 Jan 2007 19:52:50 -0500 Received: from authsmtp10.yourhostingaccount.com ([10.1.18.10] helo=authsmtp10.yourhostingaccount.com) by scan04.yourhostingaccount.com with esmtp (Exim) id 1H45EQ-00065B-8v for freebsd-hackers@freebsd.org; Mon, 08 Jan 2007 19:52:50 -0500 Received: from [69.92.217.33] (helo=vixen42) by authsmtp10.yourhostingaccount.com with esmtpa (Exim) id 1H45EP-0007GW-Ph; Mon, 08 Jan 2007 19:52:50 -0500 Date: Mon, 8 Jan 2007 18:52:47 -0600 From: Vulpes Velox To: freebsd-hackers@freebsd.org, Doug Barton Message-ID: <20070108185247.2b6e1f69@vixen42> In-Reply-To: <45A1DE76.7000201@FreeBSD.org> References: <20070107190616.73dee7b0@vixen42> <45A1DE76.7000201@FreeBSD.org> X-Mailer: Claws Mail 2.6.1 (GTK+ 2.10.7; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-EN-UserInfo: 0d1ca1697cdb7a831d4877828571b7ab:1570f0de6936c69fef9e164fffc541bc X-EN-AuthUser: vvelox2 Sender: Vulpes Velox Cc: Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jan 2007 01:07:54 -0000 On Sun, 07 Jan 2007 22:02:30 -0800 Doug Barton wrote: > Vulpes Velox wrote: > > I was just wondering. How many people here have given lots of > > though about integrating FreeBSD configuration with LDAP. I've > > just begun looking at it a lot more and was curious as to what > > other people think in this area. > > It would be more useful to have this discussion if you defined what > you meant by "FreeBSD configuration" in more detail. You might also > want to search the archives first, there is a lot of discussion > about various proposals in this area, all of which end up getting > shot down because they don't offer sufficient added value to > justify the pain of the change. I mean exactly that. Initially I have begun looking at rc.conf as a logical starting point. Initially I think seeing a rc.d stuck right in right after NETWORKING would be very interesting to have. Right after NETWORKING is finished, a program is kicked off that updates a rc file that is then included after parsing rc.conf. I am currently wondering if any one else working on this, before I start digging to much into it. The only LDAP stuff I am finding on this list has been recently in regards to integration of a ldap nss module into the base system. From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 8 22:24:03 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D875E16A403 for ; Mon, 8 Jan 2007 22:24:03 +0000 (UTC) (envelope-from lgusenet@be-well.ilk.org) Received: from mail1.sea5.speakeasy.net (mail1.sea5.speakeasy.net [69.17.117.3]) by mx1.freebsd.org (Postfix) with ESMTP id B677A13C458 for ; Mon, 8 Jan 2007 22:24:03 +0000 (UTC) (envelope-from lgusenet@be-well.ilk.org) Received: (qmail 29423 invoked from network); 8 Jan 2007 22:17:23 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail1.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 8 Jan 2007 22:17:23 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id CCCB02842F; Mon, 8 Jan 2007 17:17:22 -0500 (EST) To: freebsd-hackers@freebsd.org References: <20070108203211.GF41066@nerds.org.uk> <45A2BEEE.5010202@elischer.org> From: Lowell Gilbert In-Reply-To: <45A2BEEE.5010202@elischer.org> (Julian Elischer's message of "Mon, 08 Jan 2007 14:00:14 -0800") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (berkeley-unix) Date: Mon, 08 Jan 2007 17:17:22 -0500 Message-ID: <44fyal88p9.fsf@be-well.ilk.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailman-Approved-At: Tue, 09 Jan 2007 01:52:15 +0000 Subject: Re: TCP Checksums in mbufs X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2007 22:24:03 -0000 Julian Elischer writes: > Lee Brotherston wrote: >> Hi, >> >> I have a bit of code I have written that uses pfil to access network >> traffic as it passes between interfaces on a FreeBSD router. One of >> the functions it performs is some incredibly basic rewrites of certain >> packets (keeping the same length, so no issues about sequence >> numbers), but it does alter the payload. >> >> I just wanted to check what is the "proper" way to be going about >> recalculating the checksums on the packet? I can write a function to >> do this and write this into the packet stored in the mbuf directly, >> however I wasn't sure if there was a more acceptable method such as >> flagging it to be re-checksum'd as it's routed, or to offload the >> computation to the NIC or something? >> >> Any thoughts, suggestions, etc very welcome! >> >> By the way, I'm not subscribed to the list right now, so I'd >> appreciate it if people could CC me on replies. >> >> Many thanks >> >> Lee > > there is an algorythm to recalculate the tcp/ip > checksum when you replace a byte. you subtract the old value from the > csum and add the new one, but not quite a as easy as that. Actually, it is as easy as that (once you handle the possible overflow). And it's exactly the way this kind of case is usually handled. > I think it's given in one of the RFCs but I think it may also > be used in the tcpmss port, or possibly the mss fixup code in ppp. > I know I've used it somewhere but forget where :-) RFC 1071, but that doesn't include the code. Just the one-sentence explanation of what to do. [And several more sentences of explanation...] From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 8 22:38:40 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 45C1216A412 for ; Mon, 8 Jan 2007 22:38:40 +0000 (UTC) (envelope-from lgusenet@be-well.ilk.org) Received: from mail3.sea5.speakeasy.net (mail3.sea5.speakeasy.net [69.17.117.5]) by mx1.freebsd.org (Postfix) with ESMTP id 23B7613C467 for ; Mon, 8 Jan 2007 22:38:40 +0000 (UTC) (envelope-from lgusenet@be-well.ilk.org) Received: (qmail 31805 invoked from network); 8 Jan 2007 22:12:00 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail3.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 8 Jan 2007 22:12:00 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 03AC82842F; Mon, 8 Jan 2007 17:11:58 -0500 (EST) To: freebsd-hackers@freebsd.org References: <20070108203211.GF41066@nerds.org.uk> <45A2BEEE.5010202@elischer.org> From: Lowell Gilbert Date: Mon, 08 Jan 2007 17:11:58 -0500 In-Reply-To: <45A2BEEE.5010202@elischer.org> (Julian Elischer's message of "Mon, 08 Jan 2007 14:00:14 -0800") Message-ID: <44hcv188y9.fsf@be-well.ilk.org> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailman-Approved-At: Tue, 09 Jan 2007 01:53:46 +0000 Subject: Re: TCP Checksums in mbufs X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2007 22:38:40 -0000 Julian Elischer writes: > Lee Brotherston wrote: >> Hi, >> >> I have a bit of code I have written that uses pfil to access network >> traffic as it passes between interfaces on a FreeBSD router. One of >> the functions it performs is some incredibly basic rewrites of certain >> packets (keeping the same length, so no issues about sequence >> numbers), but it does alter the payload. >> >> I just wanted to check what is the "proper" way to be going about >> recalculating the checksums on the packet? I can write a function to >> do this and write this into the packet stored in the mbuf directly, >> however I wasn't sure if there was a more acceptable method such as >> flagging it to be re-checksum'd as it's routed, or to offload the >> computation to the NIC or something? >> >> Any thoughts, suggestions, etc very welcome! >> >> By the way, I'm not subscribed to the list right now, so I'd >> appreciate it if people could CC me on replies. >> >> Many thanks >> >> Lee > > there is an algorythm to recalculate the tcp/ip > checksum when you replace a byte. you subtract the old value from the > csum and add the new one, but not quite a as easy as that. Actually, it is as easy as that. And it's exactly the way this kind of case is usually handled. > I think it's given in one of the RFCs but I think it may also > be used in the tcpmss port, or possibly the mss fixup code in ppp. > I know I've used it somewhere but forget where :-) RFC 1071, but that doesn't include the code. Just the one-sentence explanation of what to do. [And several more sentences of explanation...] From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 8 23:29:03 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BD1BF16A40F for ; Mon, 8 Jan 2007 23:29:03 +0000 (UTC) (envelope-from lee@nerds.org.uk) Received: from furby.nerds.org.uk (furby.nerds.org.uk [82.70.196.65]) by mx1.freebsd.org (Postfix) with ESMTP id 7244B13C44B for ; Mon, 8 Jan 2007 23:29:03 +0000 (UTC) (envelope-from lee@nerds.org.uk) Received: from lee by furby.nerds.org.uk with local (Exim 4.65 (FreeBSD)) (envelope-from ) id 1H43vH-000BQH-9y; Mon, 08 Jan 2007 23:28:59 +0000 Date: Mon, 8 Jan 2007 23:28:59 +0000 From: Lee Brotherston To: Julian Elischer Message-ID: <20070108232859.GI41066@nerds.org.uk> References: <20070108203211.GF41066@nerds.org.uk> <45A2BEEE.5010202@elischer.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45A2BEEE.5010202@elischer.org> User-Agent: Mutt/1.5.13 (2006-08-11) X-Mailman-Approved-At: Tue, 09 Jan 2007 01:53:54 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: TCP Checksums in mbufs X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2007 23:29:03 -0000 On Mon, Jan 08, 2007 at 02:00:14PM -0800, Julian Elischer wrote: > there is an algorythm to recalculate the tcp/ip > checksum when you replace a byte. you subtract the old value from the > csum and add the new one, but not quite a as easy as that. > > I think it's given in one of the RFCs but I think it may also > be used in the tcpmss port, or possibly the mss fixup code in ppp. > I know I've used it somewhere but forget where :-) Aha! Would it be this one per chance? /*- * The following macro is used to update an * internet checksum. "acc" is a 32-bit * accumulation of all the changes to the * checksum (adding in old 16-bit words and * subtracting out new words), and "cksum" * is the checksum value to be updated. */ #define ADJUST_CHECKSUM(acc, cksum) { \ acc += cksum; \ if (acc < 0) { \ acc = -acc; \ acc = (acc >> 16) + (acc & 0xffff); \ acc += acc >> 16; \ cksum = (u_short) ~acc; \ } else { \ acc = (acc >> 16) + (acc & 0xffff); \ acc += acc >> 16; \ cksum = (u_short) acc; \ } \ } If so I'll set about using this... once I work out what the 32-bit accumulation bit is :) Thanks! Lee -- Lee Brotherston - From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 9 02:59:20 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0F6AD16A407 for ; Tue, 9 Jan 2007 02:59:20 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outL.internet-mail-service.net (outL.internet-mail-service.net [216.240.47.235]) by mx1.freebsd.org (Postfix) with ESMTP id DC82513C458 for ; Tue, 9 Jan 2007 02:59:19 +0000 (UTC) (envelope-from julian@elischer.org) Received: from shell.idiom.com (HELO idiom.com) (216.240.47.20) by out.internet-mail-service.net (qpsmtpd/0.32) with ESMTP; Mon, 08 Jan 2007 18:40:49 -0800 Received: from [10.251.23.190] (nat.ironport.com [63.251.108.100]) by idiom.com (8.12.11/8.12.11) with ESMTP id l092xG2K038454; Mon, 8 Jan 2007 18:59:18 -0800 (PST) (envelope-from julian@elischer.org) Message-ID: <45A30500.4040705@elischer.org> Date: Mon, 08 Jan 2007 18:59:12 -0800 From: Julian Elischer User-Agent: Thunderbird 1.5.0.9 (Macintosh/20061207) MIME-Version: 1.0 To: Lowell Gilbert References: <20070108203211.GF41066@nerds.org.uk> <45A2BEEE.5010202@elischer.org> <44hcv188y9.fsf@be-well.ilk.org> In-Reply-To: <44hcv188y9.fsf@be-well.ilk.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: TCP Checksums in mbufs X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jan 2007 02:59:20 -0000 Lowell Gilbert wrote: > > > Actually, it is as easy as that. And it's exactly the way this kind > of case is usually handled. almost.. you need to account for the fact that our computers are 2-s compliment machines and the checksum is a 1-s compliment checksum > >> I think it's given in one of the RFCs but I think it may also >> be used in the tcpmss port, or possibly the mss fixup code in ppp. >> I know I've used it somewhere but forget where :-) > > RFC 1071, but that doesn't include the code. Just the one-sentence > explanation of what to do. [And several more sentences of > explanation...] > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 9 07:22:33 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2F9CB16A40F for ; Tue, 9 Jan 2007 07:22:33 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.freebsd.org (Postfix) with ESMTP id DB88C13C459 for ; Tue, 9 Jan 2007 07:22:32 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1H4BJX-0002XZ-3O; Tue, 09 Jan 2007 09:22:31 +0200 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Vulpes Velox In-reply-to: <20070108185247.2b6e1f69@vixen42> References: <20070107190616.73dee7b0@vixen42> <45A1DE76.7000201@FreeBSD.org> <20070108185247.2b6e1f69@vixen42> Comments: In-reply-to Vulpes Velox message dated "Mon, 08 Jan 2007 18:52:47 -0600." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 09 Jan 2007 09:22:31 +0200 From: Danny Braniss Message-ID: Cc: freebsd-hackers@freebsd.org, Doug Barton Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jan 2007 07:22:33 -0000 > On Sun, 07 Jan 2007 22:02:30 -0800 > Doug Barton wrote: > > > Vulpes Velox wrote: > > > I was just wondering. How many people here have given lots of > > > though about integrating FreeBSD configuration with LDAP. I've > > > just begun looking at it a lot more and was curious as to what > > > other people think in this area. > > > > It would be more useful to have this discussion if you defined what > > you meant by "FreeBSD configuration" in more detail. You might also > > want to search the archives first, there is a lot of discussion > > about various proposals in this area, all of which end up getting > > shot down because they don't offer sufficient added value to > > justify the pain of the change. > > I mean exactly that. Initially I have begun looking at rc.conf as a > logical starting point. > > Initially I think seeing a rc.d stuck right in right after NETWORKING > would be very interesting to have. Right after NETWORKING is > finished, a program is kicked off that updates a rc file that is then > included after parsing rc.conf. > > I am currently wondering if any one else working on this, before I > start digging to much into it. The only LDAP stuff I am finding > on this list has been recently in regards to integration of a ldap nss > module into the base system. i realy don't know what this has to do with LDAP, but in our diskless environment, /etc/rc.initdiskless, has some coded added that based on info from DHCP will build a 'personalized' rc.conf (the DHCP info is loaded into kenv by boot). ... confpath=`kenv conf-path` if [ -n "$confpath" ] ; then if [ "`expr $confpath : '\(.*\):'`" ] ; then echo Mounting $confpath on /conf mount_nfs $confpath /conf chkerr $? "mount_nfs $confpath /conf" to_umount="${to_umount} $confpath" fi fi ... eval `kenv | sed -n 's/^rc\.//p'` rm -f /etc/rc.conf /etc/rc.conf.local for fc in $conf0 $conf1 $conf2 $conf3 $conf4 $conf5 $conf6 $conf7 $conf8 $conf9 rc.conf.$hostname do ho=`expr $fc : '\(.*\):'` fl=`expr $fc : '.*/\(.*\)'` if [ "${ho}" != "" ]; then mp=`expr $fc : '\(.*\)/.*'` mount_nfs $mp /mnt > /dev/null 2>&1 if [ -f /mnt/$fl ]; then echo "# from $fc /mnt/$fl" >> /etc/rc.conf cat /mnt/$fl >> /etc/rc.conf fi umount /mnt > /dev/null 2>&1 elif [ -e /conf/$fc ] ; then echo "# from /conf/$fc" >> /etc/rc.conf cat /conf/$fc >> /etc/rc.conf fi done From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 9 07:32:04 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AEBA616A407; Tue, 9 Jan 2007 07:32:04 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.freebsd.org (Postfix) with ESMTP id 6A4C013C459; Tue, 9 Jan 2007 07:32:04 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1H4B4I-0001eX-UC; Tue, 09 Jan 2007 09:06:46 +0200 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: freebsd-scsi@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 09 Jan 2007 09:06:46 +0200 From: Danny Braniss Message-ID: Cc: freebsd-hackers@freebsd.org Subject: iSCSI disconnects dilema X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jan 2007 07:32:04 -0000 Hi, While I think I have almost solved the problem of network disconnects, It downed on me a major problem: When a 'local' disk crashes, the kernel will probably hang/panic/crash. if i don't try to recover, then there is no change in the above scenario. if i try to recover, then the client does not know that it should umount/fsck/mount. While all this seems familiar, removing a floppy/disk-on-key while it's mounted, we could always say "you shouldn't have done that!", with a network connection, it can happen very often - rebooting the target, a network hickup, etc. So, any ideas? danny From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 9 07:50:06 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0D61616A403 for ; Tue, 9 Jan 2007 07:50:05 +0000 (UTC) (envelope-from SRS0=pr74Nt=GS=vvelox.net=v.velox@yourhostingaccount.com) Received: from mailout09.yourhostingaccount.com (mailout09.yourhostingaccount.com [65.254.253.72]) by mx1.freebsd.org (Postfix) with ESMTP id A7D0713C43E for ; Tue, 9 Jan 2007 07:50:05 +0000 (UTC) (envelope-from SRS0=pr74Nt=GS=vvelox.net=v.velox@yourhostingaccount.com) Received: from scan05.yourhostingaccount.com ([10.1.1.235] helo=scan05.yourhostingaccount.com) by mailout09.yourhostingaccount.com with esmtp (Exim) id 1H4BkB-0006l5-6q for freebsd-hackers@freebsd.org; Tue, 09 Jan 2007 02:50:03 -0500 Received: from authsmtp09.yourhostingaccount.com ([10.1.18.9] ident=exim) by scan05.yourhostingaccount.com with spamscanlookuphost (Exim) id 1H4BkB-0000BR-1s for freebsd-hackers@freebsd.org; Tue, 09 Jan 2007 02:50:03 -0500 Received: from authsmtp09.yourhostingaccount.com ([10.1.18.9] helo=authsmtp09.yourhostingaccount.com) by scan05.yourhostingaccount.com with esmtp (Exim) id 1H4Bk9-0000BG-UX for freebsd-hackers@freebsd.org; Tue, 09 Jan 2007 02:50:02 -0500 Received: from [69.92.217.33] (helo=vixen42) by authsmtp09.yourhostingaccount.com with esmtpa (Exim) id 1H4Bk9-0002mQ-0K; Tue, 09 Jan 2007 02:50:01 -0500 Date: Tue, 9 Jan 2007 01:49:59 -0600 From: Vulpes Velox To: Danny Braniss Message-ID: <20070109014959.7a2d62a5@vixen42> In-Reply-To: References: <20070107190616.73dee7b0@vixen42> <45A1DE76.7000201@FreeBSD.org> <20070108185247.2b6e1f69@vixen42> X-Mailer: Claws Mail 2.6.1 (GTK+ 2.10.7; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-EN-UserInfo: 0d1ca1697cdb7a831d4877828571b7ab:1570f0de6936c69fef9e164fffc541bc X-EN-AuthUser: vvelox2 Sender: Vulpes Velox Cc: freebsd-hackers@freebsd.org, Doug Barton Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jan 2007 07:50:06 -0000 On Tue, 09 Jan 2007 09:22:31 +0200 Danny Braniss wrote: > > On Sun, 07 Jan 2007 22:02:30 -0800 > > Doug Barton wrote: > > > > > Vulpes Velox wrote: > > > > I was just wondering. How many people here have given lots of > > > > though about integrating FreeBSD configuration with LDAP. I've > > > > just begun looking at it a lot more and was curious as to what > > > > other people think in this area. > > > > > > It would be more useful to have this discussion if you defined > > > what you meant by "FreeBSD configuration" in more detail. You > > > might also want to search the archives first, there is a lot of > > > discussion about various proposals in this area, all of which > > > end up getting shot down because they don't offer sufficient > > > added value to justify the pain of the change. > > > > I mean exactly that. Initially I have begun looking at rc.conf as > > a logical starting point. > > > > Initially I think seeing a rc.d stuck right in right after > > NETWORKING would be very interesting to have. Right after > > NETWORKING is finished, a program is kicked off that updates a rc > > file that is then included after parsing rc.conf. > > > > I am currently wondering if any one else working on this, before I > > start digging to much into it. The only LDAP stuff I am finding > > on this list has been recently in regards to integration of a > > ldap nss module into the base system. > > i realy don't know what this has to do with LDAP, but in our > diskless environment, /etc/rc.initdiskless, has some coded added > that based on info from DHCP will build a 'personalized' rc.conf > (the DHCP info is loaded into kenv by boot). Cool. I will look into that a bit more. Thanks for the heads up on that. > ... > confpath=`kenv conf-path` > if [ -n "$confpath" ] ; then > if [ "`expr $confpath : '\(.*\):'`" ] ; then > echo Mounting $confpath on /conf > mount_nfs $confpath /conf > chkerr $? "mount_nfs $confpath /conf" > to_umount="${to_umount} $confpath" > fi > fi > ... > eval `kenv | sed -n 's/^rc\.//p'` > rm -f /etc/rc.conf /etc/rc.conf.local > for fc in $conf0 $conf1 $conf2 $conf3 $conf4 $conf5 $conf6 $conf7 > $conf8 $conf9 rc.conf.$hostname > do > ho=`expr $fc : '\(.*\):'` > fl=`expr $fc : '.*/\(.*\)'` > if [ "${ho}" != "" ]; then > mp=`expr $fc : '\(.*\)/.*'` > mount_nfs $mp /mnt > /dev/null 2>&1 > if [ -f /mnt/$fl ]; then > echo "# from $fc /mnt/$fl" >> /etc/rc.conf > cat /mnt/$fl >> /etc/rc.conf > fi > umount /mnt > /dev/null 2>&1 > elif [ -e /conf/$fc ] ; then > echo "# from /conf/$fc" >> /etc/rc.conf > cat /conf/$fc >> /etc/rc.conf > fi > done From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 9 09:16:04 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 737C116A407 for ; Tue, 9 Jan 2007 09:16:04 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 1233013C44B for ; Tue, 9 Jan 2007 09:16:03 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp211-97.lns1.adl2.internode.on.net [203.122.211.97]) (authenticated bits=0) by cain.gsoft.com.au (8.13.5/8.13.4) with ESMTP id l098fXEL075219 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Jan 2007 19:11:34 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-hackers@freebsd.org Date: Tue, 9 Jan 2007 19:11:17 +1030 User-Agent: KMail/1.9.5 References: <20070107190616.73dee7b0@vixen42> In-Reply-To: <20070107190616.73dee7b0@vixen42> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1512753.V9YvoaoZlS"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200701091911.24377.doconnor@gsoft.com.au> X-Spam-Score: 0 () X-Scanned-By: MIMEDefang 2.57 on 203.31.81.10 Cc: Vulpes Velox Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jan 2007 09:16:04 -0000 --nextPart1512753.V9YvoaoZlS Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 08 January 2007 11:36, Vulpes Velox wrote: > I was just wondering. How many people here have given lots of though > about integrating FreeBSD configuration with LDAP. I've just begun > looking at it a lot more and was curious as to what other people > think in this area. I use OpenLDAP with smbldap-tools to do shared auth between FreeBSD and=20 Windows. I was going to write up a nice tute about it but it got eaten when my lapto= p=20 HD crashed and I haven't had the enthusiasm to redo it :( It wasn't *too* hard but not exactly trivial either :) =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1512753.V9YvoaoZlS Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQBFo1U05ZPcIHs/zowRAuFsAKCk3UPayfXzPuHcyp+lERWd3PBlvACaA8Hy QAMgRWwg8dUitjcnjs7ULas= =MMuV -----END PGP SIGNATURE----- --nextPart1512753.V9YvoaoZlS-- From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 9 10:53:03 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4304C16A415 for ; Tue, 9 Jan 2007 10:53:03 +0000 (UTC) (envelope-from jacques.fourie@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.168]) by mx1.freebsd.org (Postfix) with ESMTP id D12A213C4A8 for ; Tue, 9 Jan 2007 10:53:00 +0000 (UTC) (envelope-from jacques.fourie@gmail.com) Received: by ug-out-1314.google.com with SMTP id o2so5819145uge for ; Tue, 09 Jan 2007 02:52:59 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=FV2la3F1HQdViiFGSdiJ7yuq4LS3MclmSwRybEgGCS6OW3hDAPSgbpQpfn/piJkyad2qydzpgCxIw+iIKR/mV+Qe78JjJ1CdFCUQwR/B5OhRZsSf+cV0PoW+2hizTUdp88g3TLnyo1ghAAcGeQw0XmBGZy4DxaHczB4Sq79SzNk= Received: by 10.78.183.15 with SMTP id g15mr4429264huf.1168338390794; Tue, 09 Jan 2007 02:26:30 -0800 (PST) Received: by 10.78.198.12 with HTTP; Tue, 9 Jan 2007 02:26:30 -0800 (PST) Message-ID: Date: Tue, 9 Jan 2007 12:26:30 +0200 From: "Jacques Fourie" To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Reserving large contiguous block of RAM for device X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jan 2007 10:53:03 -0000 Hi, I am in the process of porting a Linux device driver to FreeBSD. In Linux, a large block of RAM (256MB) is reserved by using the 'mem=' and 'memmap=' arguments to the kernel. In the device driver, ioremap() is used to map this memory into kernel virtual memory. In FreeBSD contigmalloc() is available but due to the large amount of physical memory required this may not work reliably. Is there an existing method to reserve a large block of RAM early in the boot process? regards, jacques From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 9 08:19:31 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1939016A403; Tue, 9 Jan 2007 08:19:31 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from redbull.bpaserver.net (redbullneu.bpaserver.net [213.198.78.217]) by mx1.freebsd.org (Postfix) with ESMTP id C555213C43E; Tue, 9 Jan 2007 08:19:30 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from outgoing.leidinger.net (p54A5F8B7.dip.t-dialin.net [84.165.248.183]) by redbull.bpaserver.net (Postfix) with ESMTP id 8E02F2E1A6; Tue, 9 Jan 2007 09:25:00 +0100 (CET) Received: from webmail.leidinger.net (webmail.Leidinger.net [192.168.1.102]) by outgoing.leidinger.net (Postfix) with ESMTP id C9CA05B497E; Tue, 9 Jan 2007 09:19:20 +0100 (CET) Received: (from www@localhost) by webmail.leidinger.net (8.13.8/8.13.8/Submit) id l098JKPx035490; Tue, 9 Jan 2007 09:19:20 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from pslux.cec.eu.int (pslux.cec.eu.int [158.169.9.14]) by webmail.leidinger.net (Horde MIME library) with HTTP; Tue, 09 Jan 2007 09:19:20 +0100 Message-ID: <20070109091920.5l66ow3exww04ckk@webmail.leidinger.net> X-Priority: 3 (Normal) Date: Tue, 09 Jan 2007 09:19:20 +0100 From: Alexander Leidinger To: Vulpes Velox References: <20070107190616.73dee7b0@vixen42> <45A1DE76.7000201@FreeBSD.org> <20070108185247.2b6e1f69@vixen42> In-Reply-To: <20070108185247.2b6e1f69@vixen42> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) H3 (4.1.3) / FreeBSD-7.0 X-BPAnet-MailScanner-Information: Please contact the ISP for more information X-BPAnet-MailScanner: Found to be clean X-BPAnet-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-14.864, required 6, autolearn=not spam, BAYES_00 -15.00, DK_POLICY_SIGNSOME 0.00, FORGED_RCVD_HELO 0.14) X-BPAnet-MailScanner-From: alexander@leidinger.net X-Spam-Status: No X-Mailman-Approved-At: Tue, 09 Jan 2007 12:38:41 +0000 Cc: freebsd-hackers@freebsd.org, Doug Barton Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jan 2007 08:19:31 -0000 Quoting Vulpes Velox (from Mon, 8 Jan 2007 =20 18:52:47 -0600): > On Sun, 07 Jan 2007 22:02:30 -0800 > Doug Barton wrote: > >> Vulpes Velox wrote: >> > I was just wondering. How many people here have given lots of >> > though about integrating FreeBSD configuration with LDAP. I've >> > just begun looking at it a lot more and was curious as to what >> > other people think in this area. >> >> It would be more useful to have this discussion if you defined what >> you meant by "FreeBSD configuration" in more detail. You might also >> want to search the archives first, there is a lot of discussion >> about various proposals in this area, all of which end up getting >> shot down because they don't offer sufficient added value to >> justify the pain of the change. > > I mean exactly that. Initially I have begun looking at rc.conf as a > logical starting point. It seems I did misunderstand you initially. I thought you where =20 talking about integrating LDAP into the base to allow NSS/PAM stuff to =20 be provided via LDAP. > I am currently wondering if any one else working on this, before I > start digging to much into it. The only LDAP stuff I am finding > on this list has been recently in regards to integration of a ldap nss > module into the base system. Right, this is the only major discussion we had in the last months in =20 the public lists. And as long as we (FreeBSD) don't have this, we =20 don't even need to think about getting an rc.conf out of LDAP (we =20 wouldn't be self-hosting anymore if we do this before we have LDAP =20 stuff in the base). Bye, Alexander. --=20 Far duller than a serpent's tooth it is to spend a quiet youth. http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID =3D B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID =3D 72077137 From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 9 14:08:50 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2FAEE16A47B for ; Tue, 9 Jan 2007 14:08:50 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from smtp101.rog.mail.re2.yahoo.com (smtp101.rog.mail.re2.yahoo.com [206.190.36.79]) by mx1.freebsd.org (Postfix) with SMTP id AA5C413C44C for ; Tue, 9 Jan 2007 14:08:49 +0000 (UTC) (envelope-from mikej@rogers.com) Received: (qmail 95232 invoked from network); 9 Jan 2007 13:42:09 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:X-YMail-OSG:Received:Message-ID:In-Reply-To:References:Date:Subject:From:To:Cc:User-Agent:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:Importance; b=xo0vYWRYVaynMwqomMLV9HAYnbOJrqm2isNbVyxhfPhhOuCqRj4oxG7hNok+DOEnvEgYjk2K9Ajgkr49zfFah7RwbWGSwDukzDGcQZOhvtImhwiJKEGav5FKRzpMQ5VQxa2ns9vUnnkX9agQfT9uKtGand2xKvgKXAvKOsfrpug= ; Received: from unknown (HELO wettoast.dyndns.org) (mikej@rogers.com@74.111.253.239 with login) by smtp101.rog.mail.re2.yahoo.com with SMTP; 9 Jan 2007 13:42:09 -0000 X-YMail-OSG: 4E1_ek4VM1mSBdcI.dtRz5_FsjMxIC_OiJObr3YXAq5SuwU3KQ.l395iP2enTTGv1g-- Received: from 209.47.38.69 (SquirrelMail authenticated user mikej) by wettoast.dyndns.org with HTTP; Tue, 9 Jan 2007 08:42:06 -0500 (EST) Message-ID: <44647.209.47.38.69.1168350126.squirrel@wettoast.dyndns.org> In-Reply-To: <066101c7335f$611c41e0$b3db87d4@multiplay.co.uk> References: <066101c7335f$611c41e0$b3db87d4@multiplay.co.uk> Date: Tue, 9 Jan 2007 08:42:06 -0500 (EST) From: "Mike Jakubik" To: "Steven Hartland" User-Agent: SquirrelMail/1.4.9a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Mailman-Approved-At: Tue, 09 Jan 2007 14:45:29 +0000 Cc: freebsd-hackers@freebsd.org, freebsd-net@freebsd.org Subject: Re: Slow FreeBSD -> Windows performance with inflight enabled X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jan 2007 14:08:50 -0000 On Mon, January 8, 2007 2:58 pm, Steven Hartland wrote: > I've just been looking at an issue reported by some > of our users that downloads from our one of our sites > run on FreeBSD 6.1 and Apache 1.3 where strangely > slow. > > After doing some digging around I found that two remote > machines on the same network had wildly different results. > The difference being one was Windows (slow) and one was > FreeBSD 6.1 (fast). > > The results where 380Kb/s download speeds on Windows vs > 500Kb/s on FreeBSD. I played around and Googled to find > that this appears to caused by inflight. Disabling it > and restarting apache cures the problem. AFAIK there was some work done on this to make it more adaptive for LAN networks, but im not sure which version got this. From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 9 14:53:25 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8683A16A412; Tue, 9 Jan 2007 14:53:25 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from ns1.jnielsen.net (ns1.jnielsen.net [69.55.238.237]) by mx1.freebsd.org (Postfix) with ESMTP id 4D25013C44C; Tue, 9 Jan 2007 14:53:25 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from localhost (jn@ns1 [69.55.238.237]) (authenticated bits=0) by ns1.jnielsen.net (8.12.9p2/8.12.9) with ESMTP id l09EY44o042517; Tue, 9 Jan 2007 06:34:05 -0800 (PST) (envelope-from lists@jnielsen.net) From: John Nielsen To: freebsd-hackers@freebsd.org Date: Tue, 9 Jan 2007 09:31:28 -0500 User-Agent: KMail/1.9.5 References: In-Reply-To: X-Face: #X5#Y*q>F:]zT!DegL3z5Xo'^MN[$8k\[4^3rN~wm=s=Uw(sW}R?3b^*f1Wu*.<=?utf-8?q?of=5F4NrS=0A=09P*M/9CpxDo!D6?=)IY1w<9B1jB; tBQf[RU-R<,I)e"$q7N7 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200701090931.28786.lists@jnielsen.net> X-Virus-Scanned: ClamAV version 0.88.4, clamav-milter version 0.88.4 on ns1.jnielsen.net X-Virus-Status: Clean Cc: freebsd-scsi@freebsd.org Subject: Re: iSCSI disconnects dilema X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jan 2007 14:53:25 -0000 On Tuesday 09 January 2007 02:06, Danny Braniss wrote: > Hi, > While I think I have almost solved the problem of network disconnects, > It downed on me a major problem: > When a 'local' disk crashes, the kernel will probably hang/panic/crash. > if i don't try to recover, then there is no change in the above scenario. > if i try to recover, then the client does not know that it should > umount/fsck/mount. > While all this seems familiar, removing a floppy/disk-on-key while it's > mounted, we could always say "you shouldn't have done that!", with > a network connection, it can happen very often - rebooting the target, a > network hickup, etc. > > So, any ideas? I think that an iSCSI network disconnect (if handled properly) is more like a bad/flakey set of sectors and/or extremely high latency than a total disk crash. The initiator should stall as long as it can while trying to reconnect the session, and then send "hardware" timeout errors up the stack. The the rest of the OS should handle those the same as it would any other timeout errors--retry a certain number of times and then fail. I don't know how graceful the failure case is (perhaps not very), but it's an honest approximation. The above approach is IMO more than adequate for network interruptions lasting a few seconds (or a bit more). I'm not sure there's anything you can realistically do more than that. Administrators who intentionally reboot a nonredundant iSCSI target while it has active sessions are asking for trouble, and if the reboot is accidental they should do one or more of a) know to run fsck manually, b) get a better UPS, c) get a more stable/redundant iSCSI target device. Disclaimer: I know next to nothing about kernel programming, device driver development, or scsi in general. I've just been playing with and thinking about iSCSI on FreeBSD a fair amount lately. Thanks for your continued work on this. JN From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 9 15:40:10 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 673D916A403 for ; Tue, 9 Jan 2007 15:40:10 +0000 (UTC) (envelope-from life@sitevalley.com) Received: from sitevalley.com (sitevalley.com [209.67.60.43]) by mx1.freebsd.org (Postfix) with SMTP id 0FD6713C45E for ; Tue, 9 Jan 2007 15:40:09 +0000 (UTC) (envelope-from life@sitevalley.com) Received: from unknown (HELO life) (217.144.69.37) by sitevalley.com with SMTP; 9 Jan 2007 15:13:27 -0000 Message-ID: <005701c73400$b6747bc0$2401010a@zone3000.net> From: "Vitali Malicky" To: References: <20070107190616.73dee7b0@vixen42><45A1DE76.7000201@FreeBSD.org> <20070108185247.2b6e1f69@vixen42> <20070109091920.5l66ow3exww04ckk@webmail.leidinger.net> Date: Tue, 9 Jan 2007 17:12:57 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Vitali Malicky List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jan 2007 15:40:10 -0000 ----- Original Message ----- From: "Alexander Leidinger" To: "Vulpes Velox" Cc: ; "Doug Barton" Sent: Tuesday, January 09, 2007 10:19 AM Subject: Re: LDAP integration Quoting Vulpes Velox (from Mon, 8 Jan 2007 18:52:47 -0600): > On Sun, 07 Jan 2007 22:02:30 -0800 > Doug Barton wrote: > >> Vulpes Velox wrote: >> > I was just wondering. How many people here have given lots of >> > though about integrating FreeBSD configuration with LDAP. I've >> > just begun looking at it a lot more and was curious as to what >> > other people think in this area. I''ve been using LDAP a year and a half already: OpenLDAP master OpenLDAP slave TLS supposed of course system users' logins (pam_ldap, nss_ldap) samba (integration with windowz/domain controlling) squid authentication (squid_ldap_auth) apache authentication (modauthldap_apache2) native apache's module is incredibly raw :( vpopmail authentication (I had to write a patch to make vpop work correctly with openldap, but it wasn't accepted in vpopmail community and I dropped it, and now using it only in the house's projects) am going to do qmail with ldap (qmail cluster I mean) a nice management tool phpLDAPadmin helps a lot to manage the DB tree... actually it's been said above: the LDAP play is not trivial and LDAP doesn't give up to a high hand. much reading and experimenting is supposed, - but the output is worthy of it. a year an a half of smooth work and flexibility. I want to describe it step by step and publish, even have some drafts of the future documentation (actually they are scripts with the comments and configuration files), anyway one must learn LDAP very hard to be understanding it very cleary, because any documentation won't help if you're just going to take LDAP with a high hand... -- "Making it complicated is easy, making it SIMPLE is an art" From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 9 16:16:55 2007 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.ORG Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B568916A416 for ; Tue, 9 Jan 2007 16:16:55 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.freebsd.org (Postfix) with ESMTP id 28F6F13C45E for ; Tue, 9 Jan 2007 16:16:54 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (uvqlwx@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id l09GGUZT020582; Tue, 9 Jan 2007 17:16:35 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id l09GGTJu020581; Tue, 9 Jan 2007 17:16:29 +0100 (CET) (envelope-from olli) Date: Tue, 9 Jan 2007 17:16:29 +0100 (CET) Message-Id: <200701091616.l09GGTJu020581@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hackers@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG, danny@cs.huji.ac.il In-Reply-To: X-Newsgroups: list.freebsd-hackers User-Agent: tin/1.8.2-20060425 ("Shillay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Tue, 09 Jan 2007 17:16:35 +0100 (CET) Cc: Subject: Re: iSCSI disconnects dilema X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-hackers@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG, danny@cs.huji.ac.il List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jan 2007 16:16:55 -0000 Danny Braniss wrote: > While I think I have almost solved the problem of network disconnects, > It downed on me a major problem: > When a 'local' disk crashes, the kernel will probably hang/panic/crash. > if i don't try to recover, then there is no change in the above scenario. > if i try to recover, then the client does not know that it should > umount/fsck/mount. > While all this seems familiar, removing a floppy/disk-on-key while it's > mounted, we could always say "you shouldn't have done that!", with > a network connection, it can happen very often - rebooting the target, a > network hickup, etc. The IEEE1394 code (firewire) contains a hack so you can remove a _mounted_ drive (yes, pull the plug!) and later reconnect it and continue to use the filesystem. I think processes that try to access the file system during the drive being unavailable are blocked ("D" state a.k.a. "diskwait"). The purpose of that feature is that you can change the topology (e.g. remove a device that's not at the end of the bus) without having to unmount all other devices. Well, it's just a hack, and I don't know if something similar is applicable to the iSCSI situation. But I thought it wouldn't hurt to mention it anyhow. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "If you think C++ is not overly complicated, just what is a protected abstract virtual base pure virtual private destructor, and when was the last time you needed one?" -- Tom Cargil, C++ Journal From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 9 16:27:19 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B934316A492 for ; Tue, 9 Jan 2007 16:27:19 +0000 (UTC) (envelope-from victorloureirolima@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.250]) by mx1.freebsd.org (Postfix) with ESMTP id 7985413C455 for ; Tue, 9 Jan 2007 16:27:19 +0000 (UTC) (envelope-from victorloureirolima@gmail.com) Received: by an-out-0708.google.com with SMTP id c24so2305482ana for ; Tue, 09 Jan 2007 08:27:18 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=XSDLt6cOhCHBroUE55lGN0BjCbXphiGh0TfuPkD7G+c39U/V5/VWtLrJaMapo+AXsLGwgYPCCRZKPP203jqY6ZKraBsQiFyWuM5+8a7B7XovnXfCpIr5ZQCr6GAdJdWE9fPRrY7jxF2rbfixcBrrqtIx4J+7/bag1Zz1tyh+ENQ= Received: by 10.100.191.5 with SMTP id o5mr6801818anf.1168360038800; Tue, 09 Jan 2007 08:27:18 -0800 (PST) Received: by 10.100.109.16 with HTTP; Tue, 9 Jan 2007 08:27:18 -0800 (PST) Message-ID: Date: Tue, 9 Jan 2007 13:27:18 -0300 From: "Victor Loureiro Lima" To: freebsd-hackers@freebsd.org In-Reply-To: <0CFD7310-5CCE-4346-871A-270F7614919C@foolishgames.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_6487_3714788.1168360038767" References: <0CFD7310-5CCE-4346-871A-270F7614919C@foolishgames.com> X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: [patch] - random(6) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jan 2007 16:27:19 -0000 ------=_Part_6487_3714788.1168360038767 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Probly got stripped of the email somehow, somewhere ;) The patch is attached above... att, victor loureiro lima 2007/1/9, Lucas Holt : > Your patch appeared to get stripped from the mailing list. I would > like to try your patch in MidnightBSD which is based on FreeBSD 6 if > you'd be willing to email it to me. :) > > Luke > > > On Jan 8, 2007, at 2:52 PM, Victor Loureiro Lima wrote: > > > I am forwarding this to -hackers, since I havent got any response from > > the author (seanc@freebsd.org) in months ;/ Maybe someone in here > > could take a few minutes and check this patch out and maybe commit it > > to the source tree > > > > att, > > victor loureiro lima > > > > ---------- Forwarded message ---------- > > From: Victor Loureiro Lima > > Date: 27/11/2006 15:19 > > Subject: [patch] - random(6) > > To: seanc@freebsd.org > > > > > > Hello Sean, > > > > My name is Victor, I've sent you a patch which solved the "bug" in > > which random(6) would > > be way to slow to handle files that are greater than 10MB+, well, I am > > re-sending you that > > same patch with little modifications, do you think you could include > > it in the src tree? > > This patch also increases random(6) performance dramatically even > > when working with small-to-medium file sizes, it should be a good > > addition to the random(6) source tree, and > > its also been extensivelly tested against all features of random(6) > > and it scale really well with big files, for example: > > > > -- > > setuid@zion$ yes | head -200000 > test > > setuid@zion$ time ./random -f test > /dev/null > > 0.257u 0.015s 0:00.27 96.2% 11+14460k 0+0io 0pf+0w > > setuid@zion$ time random -f test > /dev/null > > 187.366u 0.007s 3:07.39 99.9% 10+12945k 0+0io 0pf+0w > > -- > > > > And this was on a Intel Core Duo 2 1.8ghz with 1GB of RAM, with one > > process taking > > less than a second to randomize it all, and the other taking 3 > > minutes, I think its a good > > patch to be applied on the source tree. > > I also took the time to change the man page of random(6) to better > > describe the changes, > > basically removed the BUGS sections (since that bug is solved by the > > patch) and included a new line on the HISTORY section describing my > > contribution to the program :). > > > > Attached are the patches for randomize_fd.c and random.6, also a > > little description of the changes made in randomize_fd.c is in the > > readme file. > > Hope you find that this is patch is commitable, I would appreciate to > > have contributed to FreeBSD even if its just this little contribution > > :) > > > > ciao, > > victor loureiro lima > > _______________________________________________ > > freebsd-hackers@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > To unsubscribe, send any mail to "freebsd-hackers- > > unsubscribe@freebsd.org" > > > Lucas Holt > Luke@FoolishGames.com > ________________________________________________________ > FoolishGames.com (Jewel Fan Site) > JustJournal.com (Free blogging) > FoolishGames.net (Enemy Territory site) > > > ------=_Part_6487_3714788.1168360038767-- From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 9 17:02:48 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E4ADB16A403 for ; Tue, 9 Jan 2007 17:02:48 +0000 (UTC) (envelope-from victorloureirolima@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.244]) by mx1.freebsd.org (Postfix) with ESMTP id A6FE113C45B for ; Tue, 9 Jan 2007 17:02:48 +0000 (UTC) (envelope-from victorloureirolima@gmail.com) Received: by an-out-0708.google.com with SMTP id c24so2314073ana for ; Tue, 09 Jan 2007 09:02:48 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=jhjISL7Fr3ff8k7XNlqyAEnjKLI/Rszxae0AxMXZWYtbMq4SfLHT7rVNim2TQTUhcBJwF7Gesl+Tqz2MwBoM07bhXy4CgWcraDDw8q6hOwCZbyhGnqBppzlv4E+EhUUXdrZ4cAO6zj1Z1zQVv8EDb6YhdLx2BaC7XlNYAuR8rJY= Received: by 10.100.166.14 with SMTP id o14mr10848880ane.1168362168175; Tue, 09 Jan 2007 09:02:48 -0800 (PST) Received: by 10.100.109.16 with HTTP; Tue, 9 Jan 2007 09:02:48 -0800 (PST) Message-ID: Date: Tue, 9 Jan 2007 14:02:48 -0300 From: "Victor Loureiro Lima" To: freebsd-hackers@freebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <0CFD7310-5CCE-4346-871A-270F7614919C@foolishgames.com> Subject: Re: [patch] - random(6) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jan 2007 17:02:49 -0000 Bummer... here is the patch: http://setuid.promisc.org/random_faster.tar.gz att, victor loureiro lima 2007/1/9, Victor Loureiro Lima : > Probly got stripped of the email somehow, somewhere ;) > The patch is attached above... > > att, > victor loureiro lima > > 2007/1/9, Lucas Holt : > > Your patch appeared to get stripped from the mailing list. I would > > like to try your patch in MidnightBSD which is based on FreeBSD 6 if > > you'd be willing to email it to me. :) > > > > Luke > > > > > > On Jan 8, 2007, at 2:52 PM, Victor Loureiro Lima wrote: > > > > > I am forwarding this to -hackers, since I havent got any response from > > > the author (seanc@freebsd.org) in months ;/ Maybe someone in here > > > could take a few minutes and check this patch out and maybe commit it > > > to the source tree > > > > > > att, > > > victor loureiro lima > > > > > > ---------- Forwarded message ---------- > > > From: Victor Loureiro Lima > > > Date: 27/11/2006 15:19 > > > Subject: [patch] - random(6) > > > To: seanc@freebsd.org > > > > > > > > > Hello Sean, > > > > > > My name is Victor, I've sent you a patch which solved the "bug" in > > > which random(6) would > > > be way to slow to handle files that are greater than 10MB+, well, I am > > > re-sending you that > > > same patch with little modifications, do you think you could include > > > it in the src tree? > > > This patch also increases random(6) performance dramatically even > > > when working with small-to-medium file sizes, it should be a good > > > addition to the random(6) source tree, and > > > its also been extensivelly tested against all features of random(6) > > > and it scale really well with big files, for example: > > > > > > -- > > > setuid@zion$ yes | head -200000 > test > > > setuid@zion$ time ./random -f test > /dev/null > > > 0.257u 0.015s 0:00.27 96.2% 11+14460k 0+0io 0pf+0w > > > setuid@zion$ time random -f test > /dev/null > > > 187.366u 0.007s 3:07.39 99.9% 10+12945k 0+0io 0pf+0w > > > -- > > > > > > And this was on a Intel Core Duo 2 1.8ghz with 1GB of RAM, with one > > > process taking > > > less than a second to randomize it all, and the other taking 3 > > > minutes, I think its a good > > > patch to be applied on the source tree. > > > I also took the time to change the man page of random(6) to better > > > describe the changes, > > > basically removed the BUGS sections (since that bug is solved by the > > > patch) and included a new line on the HISTORY section describing my > > > contribution to the program :). > > > > > > Attached are the patches for randomize_fd.c and random.6, also a > > > little description of the changes made in randomize_fd.c is in the > > > readme file. > > > Hope you find that this is patch is commitable, I would appreciate to > > > have contributed to FreeBSD even if its just this little contribution > > > :) > > > > > > ciao, > > > victor loureiro lima > > > _______________________________________________ > > > freebsd-hackers@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > > To unsubscribe, send any mail to "freebsd-hackers- > > > unsubscribe@freebsd.org" > > > > > > Lucas Holt > > Luke@FoolishGames.com > > ________________________________________________________ > > FoolishGames.com (Jewel Fan Site) > > JustJournal.com (Free blogging) > > FoolishGames.net (Enemy Territory site) > > > > > > > > > From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 9 17:05:19 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2369516A494; Tue, 9 Jan 2007 17:05:19 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from ns1.jnielsen.net (ns1.jnielsen.net [69.55.238.237]) by mx1.freebsd.org (Postfix) with ESMTP id 04A7B13C4A6; Tue, 9 Jan 2007 17:05:18 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from localhost (jn@ns1 [69.55.238.237]) (authenticated bits=0) by ns1.jnielsen.net (8.12.9p2/8.12.9) with ESMTP id l09H574o019218; Tue, 9 Jan 2007 09:05:07 -0800 (PST) (envelope-from lists@jnielsen.net) From: John Nielsen To: freebsd-hackers@freebsd.org Date: Tue, 9 Jan 2007 12:02:31 -0500 User-Agent: KMail/1.9.5 References: In-Reply-To: X-Face: #X5#Y*q>F:]zT!DegL3z5Xo'^MN[$8k\[4^3rN~wm=s=Uw(sW}R?3b^*f1Wu*.<=?utf-8?q?of=5F4NrS=0A=09P*M/9CpxDo!D6?=)IY1w<9B1jB; tBQf[RU-R<,I)e"$q7N7 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200701091202.32226.lists@jnielsen.net> X-Virus-Scanned: ClamAV version 0.88.4, clamav-milter version 0.88.4 on ns1.jnielsen.net X-Virus-Status: Clean Cc: freebsd-scsi@freebsd.org, Dan Nelson Subject: Re: iSCSI disconnects dilema X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jan 2007 17:05:19 -0000 Forwarding a relevant comment from a parallel discussion on -questions. ---------- Forwarded Message ---------- Subject: Re: iSCSI Date: Tuesday 09 January 2007 11:35 From: Dan Nelson To: DAve Cc: Free BSD Questions list In the last episode (Jan 09), DAve said: > The developers response, for those who are interested. > > hi Dave, > the initiator for iSCSI will hit stable/current real soon now. > that was the good news, now for the down side: > what was missing all along was recovery from network disconnects, so > while I think I have it almost worked out, I've come across a major > flow in the iscsi design: > when the targets crashes, and comes back, there is no way > to tell the client to run an fsck. This is not a problem if the > client is mounting the iscsi partition read only. > > danny Why should the client need to do an fsck? From its point of view it should just look like the target had the iSCSI equivalent of a bus reset. It should resend any queued requests and continue. On Tuesday 09 January 2007 02:06, Danny Braniss wrote: > Hi, > While I think I have almost solved the problem of network disconnects, > It downed on me a major problem: > When a 'local' disk crashes, the kernel will probably hang/panic/crash. > if i don't try to recover, then there is no change in the above scenario. > if i try to recover, then the client does not know that it should > umount/fsck/mount. > While all this seems familiar, removing a floppy/disk-on-key while it's > mounted, we could always say "you shouldn't have done that!", with > a network connection, it can happen very often - rebooting the target, a > network hickup, etc. From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 9 20:04:52 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 19EB316A412 for ; Tue, 9 Jan 2007 20:04:52 +0000 (UTC) (envelope-from freebsd-hackers@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id C600D13C458 for ; Tue, 9 Jan 2007 20:04:51 +0000 (UTC) (envelope-from freebsd-hackers@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1H4NDA-0000Kh-Rz for freebsd-hackers@freebsd.org; Tue, 09 Jan 2007 21:04:44 +0100 Received: from 89-172-49-221.adsl.net.t-com.hr ([89.172.49.221]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 09 Jan 2007 21:04:44 +0100 Received: from ivoras by 89-172-49-221.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 09 Jan 2007 21:04:44 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-hackers@freebsd.org From: Ivan Voras Date: Tue, 09 Jan 2007 21:04:28 +0100 Lines: 28 Message-ID: References: <200701090931.28786.lists@jnielsen.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigB4F4BA0A9F0163D722FD25B5" X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 89-172-49-221.adsl.net.t-com.hr User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) In-Reply-To: <200701090931.28786.lists@jnielsen.net> X-Enigmail-Version: 0.94.1.2 Sender: news Cc: freebsd-scsi@freebsd.org Subject: Re: iSCSI disconnects dilema X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jan 2007 20:04:52 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigB4F4BA0A9F0163D722FD25B5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable John Nielsen wrote: > I don't know how=20 > graceful the failure case is (perhaps not very)... Not at all - removing a mounted USB device panics the kernel. --------------enigB4F4BA0A9F0163D722FD25B5 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFo/VSldnAQVacBcgRAmDJAJ994m1Rk2FiPv/HC3jrJlgd8IkyfACfTqQV Qao+ofnehodBCORsIFDE5qM= =SSFc -----END PGP SIGNATURE----- --------------enigB4F4BA0A9F0163D722FD25B5-- From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 9 21:23:34 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C065116A403 for ; Tue, 9 Jan 2007 21:23:34 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by mx1.freebsd.org (Postfix) with SMTP id 7B6DA13C44B for ; Tue, 9 Jan 2007 21:23:34 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 14835 invoked by uid 399); 9 Jan 2007 21:23:34 -0000 Received: from localhost (HELO ?192.168.0.5?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 9 Jan 2007 21:23:34 -0000 X-Originating-IP: 127.0.0.1 Message-ID: <45A407D1.9030101@FreeBSD.org> Date: Tue, 09 Jan 2007 13:23:29 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Vulpes Velox References: <20070107190616.73dee7b0@vixen42> <45A1DE76.7000201@FreeBSD.org> <20070108185247.2b6e1f69@vixen42> In-Reply-To: <20070108185247.2b6e1f69@vixen42> X-Enigmail-Version: 0.94.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jan 2007 21:23:34 -0000 Vulpes Velox wrote: > On Sun, 07 Jan 2007 22:02:30 -0800 > Doug Barton wrote: > >> Vulpes Velox wrote: >>> I was just wondering. How many people here have given lots of >>> though about integrating FreeBSD configuration with LDAP. I've >>> just begun looking at it a lot more and was curious as to what >>> other people think in this area. >> It would be more useful to have this discussion if you defined what >> you meant by "FreeBSD configuration" in more detail. You might also >> want to search the archives first, there is a lot of discussion >> about various proposals in this area, all of which end up getting >> shot down because they don't offer sufficient added value to >> justify the pain of the change. > > I mean exactly that. Initially I have begun looking at rc.conf as a > logical starting point. Why do you consider rc.d to be a logical starting point? The issue of nss integration is much more useful, especially given that there is critical mass for support to bring ldap into the base to make this happen. > Initially I think seeing a rc.d stuck right in right after NETWORKING > would be very interesting to have. Right after NETWORKING is > finished, a program is kicked off that updates a rc file that is then > included after parsing rc.conf. You've stated what you want to do, but you haven't said why. Please note carefully what I said above. You need to demonstrate SIGNIFICANT added value for this proposal to get any kind of serious consideration. All you've said so far is, "this would be neat!" I was serious about searching the archives, this ground has been pretty well covered. And yes, in case you're wondering, I _am_ being a bit harsh, but it's for a purpose. Unless you really want to do it anyway, I don't want there to be any confusion down the road when you come back to us with a massive patch you expect to be integrated. Doug -- This .signature sanitized for your protection From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 10 00:58:48 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8519F16A40F for ; Wed, 10 Jan 2007 00:58:48 +0000 (UTC) (envelope-from SRS0=e45MbK=GT=vvelox.net=v.velox@yourhostingaccount.com) Received: from mailout17.yourhostingaccount.com (mailout17.yourhostingaccount.com [65.254.253.139]) by mx1.freebsd.org (Postfix) with ESMTP id 49AC313C45E for ; Wed, 10 Jan 2007 00:58:48 +0000 (UTC) (envelope-from SRS0=e45MbK=GT=vvelox.net=v.velox@yourhostingaccount.com) Received: from scan06.yourhostingaccount.com ([10.1.1.236] helo=scan06.yourhostingaccount.com) by mailout17.yourhostingaccount.com with esmtp (Exim) id 1H4RZ8-0007dj-W3 for freebsd-hackers@freebsd.org; Tue, 09 Jan 2007 19:43:43 -0500 Received: from authsmtp09.yourhostingaccount.com ([10.1.18.9] ident=exim) by scan06.yourhostingaccount.com with spamscanlookuphost (Exim) id 1H4RZ8-0005RL-Fc for freebsd-hackers@freebsd.org; Tue, 09 Jan 2007 19:43:42 -0500 Received: from authsmtp09.yourhostingaccount.com ([10.1.18.9] helo=authsmtp09.yourhostingaccount.com) by scan06.yourhostingaccount.com with esmtp (Exim) id 1H4RZ6-0005R7-OQ for freebsd-hackers@freebsd.org; Tue, 09 Jan 2007 19:43:40 -0500 Received: from [69.92.217.33] (helo=vixen42) by authsmtp09.yourhostingaccount.com with esmtpa (Exim) id 1H4RZ5-0005I9-Lj; Tue, 09 Jan 2007 19:43:40 -0500 Date: Tue, 9 Jan 2007 18:43:46 -0600 From: Vulpes Velox To: Doug Barton Message-ID: <20070109184346.135e0bf4@vixen42> In-Reply-To: <45A407D1.9030101@FreeBSD.org> References: <20070107190616.73dee7b0@vixen42> <45A1DE76.7000201@FreeBSD.org> <20070108185247.2b6e1f69@vixen42> <45A407D1.9030101@FreeBSD.org> X-Mailer: Claws Mail 2.7.0 (GTK+ 2.10.7; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-EN-UserInfo: 0d1ca1697cdb7a831d4877828571b7ab:1570f0de6936c69fef9e164fffc541bc X-EN-AuthUser: vvelox2 Sender: Vulpes Velox Cc: freebsd-hackers@freebsd.org Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2007 00:58:48 -0000 On Tue, 09 Jan 2007 13:23:29 -0800 Doug Barton wrote: > Vulpes Velox wrote: > > On Sun, 07 Jan 2007 22:02:30 -0800 > > Doug Barton wrote: > > > >> Vulpes Velox wrote: > >>> I was just wondering. How many people here have given lots of > >>> though about integrating FreeBSD configuration with LDAP. I've > >>> just begun looking at it a lot more and was curious as to what > >>> other people think in this area. > >> It would be more useful to have this discussion if you defined > >> what you meant by "FreeBSD configuration" in more detail. You > >> might also want to search the archives first, there is a lot of > >> discussion about various proposals in this area, all of which > >> end up getting shot down because they don't offer sufficient > >> added value to justify the pain of the change. > > > > I mean exactly that. Initially I have begun looking at rc.conf as > > a logical starting point. > > Why do you consider rc.d to be a logical starting point? The issue > of nss integration is much more useful, especially given that there > is critical mass for support to bring ldap into the base to make > this happen. I do want to see it in the base, but what I want is even less intrusive than this. I want to get the infastructure in place for supporting doing this type of thing. I am largely focusing on the idea of LDAP right now, but I see no reason the base part can't be written in a neutral manner that it can non-instrusively be included in the base in little more than a single rc.d for kicking off a program specified in rc.conf to take care of that. This allows the user to easily choose from a system from the ports that fits their need. What I am thinking is a the rc.d file runs the command specified, the program or script prints a list of files it is going to update, those files are then backed up, and the program then installs the new files. Upon not being able to update, it can be leave the files in place, run a specified command, or pull in a set of default files. What do you think? :) > > Initially I think seeing a rc.d stuck right in right after > > NETWORKING would be very interesting to have. Right after > > NETWORKING is finished, a program is kicked off that updates a rc > > file that is then included after parsing rc.conf. > > You've stated what you want to do, but you haven't said why. Please > note carefully what I said above. You need to demonstrate > SIGNIFICANT added value for this proposal to get any kind of serious > consideration. All you've said so far is, "this would be neat!" I > was serious about searching the archives, this ground has been > pretty well covered. The why is because I like centralized management and it would be really handy for that. For my use, it would be handy in regards to my laptops. I feel better central management is extreme significant. If I had nothing more to say than "this would be neat!" we would not still be talking. Right now I am just poking around for other people I regards to searching the archives, I am not seeing any thing in regards to LDAP outside of NSS recently. I am also not finding any thing in regards to dynamically and automatically building various config files. > And yes, in case you're wondering, I _am_ being a bit harsh, but > it's for a purpose. Unless you really want to do it anyway, I don't > want there to be any confusion down the road when you come back to > us with a massive patch you expect to be integrated. There will be no massive patch for it, given it involves little more than the inclusion of a single rc.d file and a bit of documentation. From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 10 06:32:17 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6573516A403 for ; Wed, 10 Jan 2007 06:32:17 +0000 (UTC) (envelope-from chewy509@lycos.com) Received: from smail1.lycosmail.lycos.com (bos-mail-smail2.bos.lycos.com [209.202.208.42]) by mx1.freebsd.org (Postfix) with ESMTP id 27DCF13C44B for ; Wed, 10 Jan 2007 06:32:16 +0000 (UTC) (envelope-from chewy509@lycos.com) Received: from bos-mail-wwl8.lycosmail.com (bos-mail-wwl8b.bos.lycos.com [10.124.64.88]) by bos-mail-smail2.lycosmail.com (8.13.6/8.9.1) with ESMTP id l0A6HcTT000867; Wed, 10 Jan 2007 01:17:38 -0500 Received: (from hanadmin@localhost) by bos-mail-wwl8.lycosmail.com (8.12.9/8.9.1) id l0A6MoMH004784 for ; Wed, 10 Jan 2007 15:22:50 +0900 Content-Transfer-Encoding: 8bit X-Originating-IP: [210.11.58.16] From: "darran kartaschew" Organization: Lycos. Inc. Priority: Normal To: X-Mailer: Daum Web Mailer 1.1 Date: Wed, 10 Jan 2007 01:22:50 -0500 (EST) Message-Id: <20070110012250.HM.0000000000000G0@chewy509.bos-mail-wwl8.lycos.com> Errors-To: X-Hanmail-Attr: fc=1 X-Mailman-Approved-At: Wed, 10 Jan 2007 12:30:01 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: sbrk vs mmap X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2007 06:32:17 -0000 Hi Guys, I'm having some issues with rewriting a simple malloc() function to be with FreeBSD (AMD64). This is part of porting an application from Linux to FreeBSD. After pulling my hair out for a while, I've found that the sbrk() system call just returns "45 - Operation Not Supported" error, irrespective of the parameters passed to it. (I've found the source for sbrk() and see that it's not implemented). So I decided to try using mmap() instead. All memory allocations don't have to be continuous, so mmap() will suffice. The problem is I'm getting an invalid file handle error? According to the man page, if you use MAP_ANON you're just allocating a block of memory without linking to a file, and a handle of -1 should be supplied... Any way code is as follows: memInit: mov r4, 0 ; don't care where the memory is allocated mov r5, 1048576 ; alloc 1MB mov r3, 3 ; RW access to memory mov r2, 4096 ; MAP_ANON - not a file mov r8d, -1 ; -1 for file handle if using MAP_ANON mov r9, 0 ; ignored for MAP_ANON mov r0, 197 ; mmap(); syscall mov qword [_mmap], r0 ; save address so we can release it on exit; ret It fails with an EBADF (9) ; Bad File Descriptor error... Note: r0 = rax, r1 = rbx, r2 = rcx, r3 = rdx, r4 = rdi, r5 = rsi, r6 = rbp, r7 = rsp. Various parameters for mmap() are found in mman.h>. So does anyone have an example of a working call to mmap() or tell me what's wrong with the above code? I've done up a test C program that simple calls mmap(), after tracing through the compiled C program using gdb I can't see that I'm doing anything different to what gcc/glibc are doing? (except the macro expansion that's in libc which adds an additional 0 to the top of the stack). PS. FASM 1.66 running on FreeBSD 6.1 (AMD64). PPS. This is NOT a homework assignment! (tm) :P _________________________________________________________________ [1]Free Movies 100's of Free Feature Length Films - Meet Friends, Watch Movies & Win! References 1. http://cinema.lycos.com/?if_Event=mail From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 10 14:39:26 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1F0BF16A40F for ; Wed, 10 Jan 2007 14:39:26 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.freebsd.org (Postfix) with ESMTP id 9FC7C13C442 for ; Wed, 10 Jan 2007 14:39:25 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id l0AEdGQ2085036; Wed, 10 Jan 2007 09:39:17 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Wed, 10 Jan 2007 08:55:48 -0500 User-Agent: KMail/1.9.4 References: <20070110012250.HM.0000000000000G0@chewy509.bos-mail-wwl8.lycos.com> In-Reply-To: <20070110012250.HM.0000000000000G0@chewy509.bos-mail-wwl8.lycos.com> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200701100855.49186.jhb@freebsd.org> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [192.168.0.1]); Wed, 10 Jan 2007 09:39:17 -0500 (EST) X-Virus-Scanned: ClamAV 0.88.3/2432/Wed Jan 10 08:12:31 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: darran kartaschew Subject: Re: sbrk vs mmap X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2007 14:39:26 -0000 On Wednesday 10 January 2007 01:22, darran kartaschew wrote: > > Hi Guys, > I'm having some issues with rewriting a simple malloc() function to be > with FreeBSD (AMD64). This is part of porting an application from > Linux > to FreeBSD. > After pulling my hair out for a while, I've found that the sbrk() > system call just returns "45 - Operation Not Supported" error, > irrespective of the parameters passed to it. (I've found the source > for sbrk() and see that it's not implemented). > So I decided to try using mmap() instead. All memory allocations don't > have to be continuous, so mmap() will suffice. The problem is I'm > getting an invalid file handle error? According to the man page, if > you > use MAP_ANON you're just allocating a block of memory without linking > to a file, and a handle of -1 should be supplied... Any way code is as > follows: > memInit: > mov r4, 0 ; don't care where the memory is allocated > mov r5, 1048576 ; alloc 1MB > mov r3, 3 ; RW access to memory > mov r2, 4096 ; MAP_ANON - not a file > mov r8d, -1 ; -1 for file handle if using MAP_ANON > mov r9, 0 ; ignored for MAP_ANON > mov r0, 197 ; mmap(); > syscall > mov qword [_mmap], r0 ; save address so we can release it on exit; > ret > It fails with an EBADF (9) ; Bad File Descriptor error... > Note: r0 = rax, r1 = rbx, r2 = rcx, r3 = rdx, r4 = rdi, r5 = rsi, r6 = > rbp, r7 = rsp. Various parameters for mmap() are found in mman.h>. > So does anyone have an example of a working call to mmap() or tell me > what's wrong with the above code? > I've done up a test C program that simple calls mmap(), after > tracing through the compiled C program using gdb I can't see that > I'm doing anything different to what gcc/glibc are doing? (except > the macro expansion that's in libc which adds an additional > 0 to the top of the stack). > PS. FASM 1.66 running on FreeBSD 6.1 (AMD64). > PPS. This is NOT a homework assignment! (tm) :P Is there a particular reason you have to use assembly and not C? You can call C functions from assembly and vice versa. You also forgot to include one of MAP_SHARED or MAP_PRIVATE in your flags. -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 10 21:46:25 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 22BF416A407; Wed, 10 Jan 2007 21:46:25 +0000 (UTC) (envelope-from lamont@scriptkiddie.org) Received: from sploit.scriptkiddie.org (sploit.scriptkiddie.org [216.231.47.214]) by mx1.freebsd.org (Postfix) with ESMTP id E89BD13C45E; Wed, 10 Jan 2007 21:46:24 +0000 (UTC) (envelope-from lamont@scriptkiddie.org) Received: from sploit (sploit [216.231.47.214]) by sploit.scriptkiddie.org (8.12.11/8.12.11) with ESMTP id l0ALQvxN005407; Wed, 10 Jan 2007 13:27:05 -0800 (PST) Date: Wed, 10 Jan 2007 13:26:57 -0800 (PST) From: Lamont Granquist To: Vulpes Velox In-Reply-To: <20070109184346.135e0bf4@vixen42> Message-ID: References: <20070107190616.73dee7b0@vixen42> <45A1DE76.7000201@FreeBSD.org> <20070108185247.2b6e1f69@vixen42> <45A407D1.9030101@FreeBSD.org> <20070109184346.135e0bf4@vixen42> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org, Doug Barton Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2007 21:46:25 -0000 On Tue, 9 Jan 2007, Vulpes Velox wrote: > The why is because I like centralized management and it would be > really handy for that. For my use, it would be handy in regards to my > laptops. > > I feel better central management is extreme significant. If I had > nothing more to say than "this would be neat!" we would not still be > talking. Right now I am just poking around for other people > > I regards to searching the archives, I am not seeing any thing in > regards to LDAP outside of NSS recently. I am also not finding any > thing in regards to dynamically and automatically building various > config files. Why are you doing this in the FreeBSD rc scripts directly? Why not install cfengine and work on making cfengine play better with database-driven config? And if you're looking specifically at the /etc/rc.conf config file, what would be more useful would be an /etc/rc.conf.d/ directory. That gets away from the need to tweak and edit the /etc/rc.conf config file with multiple inputs tweaking a single file. Instead you can drop whole orthogonal fragments into /etc/rc.conf.d/inetd to manage the inetd config which would make it more friendly to radmind-like approaches. It also makes it easier to use with cfengine since orthogonal cfengine modules aren't doing editfiles touches to the same files. The /etc/cron.d directory that (most?) linux distros have is similarly very useful to drop in files that contain completely orthogonal config (and may be written by entirely different config management tools -- e.g. system config management vs. application deployment/management), and the /etc/periodic functionality is not flexible enough to cover all cases. From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 10 21:56:32 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 91A5816A40F for ; Wed, 10 Jan 2007 21:56:32 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by mx1.freebsd.org (Postfix) with SMTP id 49AFC13C43E for ; Wed, 10 Jan 2007 21:56:32 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 15239 invoked by uid 399); 10 Jan 2007 21:56:27 -0000 Received: from localhost (HELO ?192.168.0.5?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 10 Jan 2007 21:56:27 -0000 X-Originating-IP: 127.0.0.1 Message-ID: <45A56107.5050205@FreeBSD.org> Date: Wed, 10 Jan 2007 13:56:23 -0800 From: Doug Barton Organization: http://www.freebsd.org/ User-Agent: Thunderbird 1.5.0.8 (X11/20061215) MIME-Version: 1.0 To: Lamont Granquist References: <20070107190616.73dee7b0@vixen42> <45A1DE76.7000201@FreeBSD.org> <20070108185247.2b6e1f69@vixen42> <45A407D1.9030101@FreeBSD.org> <20070109184346.135e0bf4@vixen42> In-Reply-To: X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, Vulpes Velox Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2007 21:56:32 -0000 Lamont Granquist wrote: > Why are you doing this in the FreeBSD rc scripts directly? Why not > install cfengine and work on making cfengine play better with > database-driven config? Indeed. For a "many systems" problem, cfengine is a great tool. I think the OP is more interested in the "dynamically configured laptop" problem, which is also an interesting/difficult one, but I don't think it's a good problem for LDAP to solve. It still feels like "I have LDAP that I want to use as a solution, so what problem can I point it at?" to me. > And if you're looking specifically at the /etc/rc.conf config file, what > would be more useful would be an /etc/rc.conf.d/ directory. Good news for you, we already support that. :) I agree that it makes a great tool for the "many systems" problem, and could reasonably be used for part of the "dynamic laptop" problem too. > That gets > away from the need to tweak and edit the /etc/rc.conf config file with > multiple inputs tweaking a single file. Instead you can drop whole > orthogonal fragments into /etc/rc.conf.d/inetd to manage the inetd > config which would make it more friendly to radmind-like approaches. It > also makes it easier to use with cfengine since orthogonal cfengine > modules aren't doing editfiles touches to the same files. Yes yes yes all around. At one time I suggested that we add support for /usr/local/etc/rc.conf.d and encourage port authors to drop files in there, but I didn't get much enthusiasm for it. Perhaps it's time to revisit that? > The > /etc/cron.d directory that (most?) linux distros have is similarly very > useful to drop in files that contain completely orthogonal config (and > may be written by entirely different config management tools -- e.g. > system config management vs. application deployment/management), and the > /etc/periodic functionality is not flexible enough to cover all cases. That's not a bad idea, but you'll have to find some other huckleberry to address it, I've got my hands full at the moment. Doug -- This .signature sanitized for your protection From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 10 22:07:00 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8672116A403 for ; Wed, 10 Jan 2007 22:07:00 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: from mired.org (vpn.mired.org [66.92.153.74]) by mx1.freebsd.org (Postfix) with SMTP id 2BBC613C461 for ; Wed, 10 Jan 2007 22:07:00 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: (qmail 37425 invoked by uid 1001); 10 Jan 2007 22:06:34 -0000 Received: by bhuda.mired.org (tmda-sendmail, from uid 1001); Wed, 10 Jan 2007 17:06:33 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17829.25449.731134.744939@bhuda.mired.org> Date: Wed, 10 Jan 2007 17:06:33 -0500 To: Doug Barton In-Reply-To: <45A56107.5050205@FreeBSD.org> References: <20070107190616.73dee7b0@vixen42> <45A1DE76.7000201@FreeBSD.org> <20070108185247.2b6e1f69@vixen42> <45A407D1.9030101@FreeBSD.org> <20070109184346.135e0bf4@vixen42> <45A56107.5050205@FreeBSD.org> X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.1.5 (Fettercairn) From: Mike Meyer Cc: freebsd-hackers@freebsd.org Subject: /etc/rc.conf.d (was: LDAP integration) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2007 22:07:00 -0000 In <45A56107.5050205@FreeBSD.org>, Doug Barton typed: > Lamont Granquist wrote: > > And if you're looking specifically at the /etc/rc.conf config file, what > > would be more useful would be an /etc/rc.conf.d/ directory. > Good news for you, we already support that. :) I agree that it makes a > great tool for the "many systems" problem, and could reasonably be > used for part of the "dynamic laptop" problem too. I've got questions. Do you have a documentation pointer? > Yes yes yes all around. At one time I suggested that we add support > for /usr/local/etc/rc.conf.d and encourage port authors to drop files > in there, but I didn't get much enthusiasm for it. Perhaps it's time > to revisit that? While I generally feel that what's good for the base system is good for ports (and vice versa), is there any real benefit to be had from having multiple directories for this purpose? In particular, I treat /etc as precious, becuase it tends to be full of things I edited myself. /usr/opt/etc, not so much. If we do have multiple directories, I'd ask that it be a user-configurable list, defaulting to /etc/rc.conf.d and $LOCALBASE/etc/rc.conf.d, ala local_startup and a number of others. Thanks, http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 10 22:12:57 2007 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1206616A523; Wed, 10 Jan 2007 22:12:57 +0000 (UTC) (envelope-from lamont@scriptkiddie.org) Received: from sploit.scriptkiddie.org (sploit.scriptkiddie.org [216.231.47.214]) by mx1.freebsd.org (Postfix) with ESMTP id B45C313C441; Wed, 10 Jan 2007 22:12:54 +0000 (UTC) (envelope-from lamont@scriptkiddie.org) Received: from sploit (sploit [216.231.47.214]) by sploit.scriptkiddie.org (8.12.11/8.12.11) with ESMTP id l0AMCsL3005633; Wed, 10 Jan 2007 14:12:54 -0800 (PST) Date: Wed, 10 Jan 2007 14:12:54 -0800 (PST) From: Lamont Granquist To: Doug Barton In-Reply-To: <45A56107.5050205@FreeBSD.org> Message-ID: References: <20070107190616.73dee7b0@vixen42> <45A1DE76.7000201@FreeBSD.org> <20070108185247.2b6e1f69@vixen42> <45A407D1.9030101@FreeBSD.org> <20070109184346.135e0bf4@vixen42> <45A56107.5050205@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@FreeBSD.org, Vulpes Velox Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2007 22:12:57 -0000 On Wed, 10 Jan 2007, Doug Barton wrote: > Lamont Granquist wrote: > >> Why are you doing this in the FreeBSD rc scripts directly? Why not >> install cfengine and work on making cfengine play better with >> database-driven config? > > Indeed. For a "many systems" problem, cfengine is a great tool. I > think the OP is more interested in the "dynamically configured laptop" > problem, which is also an interesting/difficult one, but I don't think > it's a good problem for LDAP to solve. It still feels like "I have > LDAP that I want to use as a solution, so what problem can I point it > at?" to me. Yeah, I've also found LDAP to be more of a problem than a solution itself. Once the data starts to be dynamically updated and acquires a higher rate of change you no longer have a 'directory service' that you're working with and MySQL becomes a better tool than LDAP. System config has a way of creeeping into becoming more dynamic over time, particularly when you start logging audit trails in the database, success codes, error conditions, state machines, etc. >> And if you're looking specifically at the /etc/rc.conf config file, what >> would be more useful would be an /etc/rc.conf.d/ directory. > > Good news for you, we already support that. :) I agree that it makes a > great tool for the "many systems" problem, and could reasonably be > used for part of the "dynamic laptop" problem too. 7-current feature? I'm not seeing it in rc.conf(5) on my RELENG_6-ish system... >> That gets >> away from the need to tweak and edit the /etc/rc.conf config file with >> multiple inputs tweaking a single file. Instead you can drop whole >> orthogonal fragments into /etc/rc.conf.d/inetd to manage the inetd >> config which would make it more friendly to radmind-like approaches. It >> also makes it easier to use with cfengine since orthogonal cfengine >> modules aren't doing editfiles touches to the same files. > > Yes yes yes all around. At one time I suggested that we add support > for /usr/local/etc/rc.conf.d and encourage port authors to drop files > in there, but I didn't get much enthusiasm for it. Perhaps it's time > to revisit that? sounds great to me, but i don't have the CFT >> The >> /etc/cron.d directory that (most?) linux distros have is similarly very >> useful to drop in files that contain completely orthogonal config (and >> may be written by entirely different config management tools -- e.g. >> system config management vs. application deployment/management), and the >> /etc/periodic functionality is not flexible enough to cover all cases. > > That's not a bad idea, but you'll have to find some other huckleberry > to address it, I've got my hands full at the moment. yup, hear ya. From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 10 22:14:22 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8461916A415 for ; Wed, 10 Jan 2007 22:14:22 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by mx1.freebsd.org (Postfix) with SMTP id 2238C13C441 for ; Wed, 10 Jan 2007 22:14:19 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 3933 invoked by uid 399); 10 Jan 2007 22:14:19 -0000 Received: from localhost (HELO ?192.168.0.5?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 10 Jan 2007 22:14:19 -0000 X-Originating-IP: 127.0.0.1 Message-ID: <45A56539.9070204@FreeBSD.org> Date: Wed, 10 Jan 2007 14:14:17 -0800 From: Doug Barton Organization: http://www.freebsd.org/ User-Agent: Thunderbird 1.5.0.8 (X11/20061215) MIME-Version: 1.0 To: Vulpes Velox References: <20070107190616.73dee7b0@vixen42> <45A1DE76.7000201@FreeBSD.org> <20070108185247.2b6e1f69@vixen42> <45A407D1.9030101@FreeBSD.org> <20070109184346.135e0bf4@vixen42> In-Reply-To: <20070109184346.135e0bf4@vixen42> X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2007 22:14:22 -0000 Vulpes Velox wrote: > There will be no massive patch for it, given it involves little more > than the inclusion of a single rc.d file and a bit of documentation. In that case, you'll be glad to know that the base in 6.x and newer already supports running a local rc.d script in the overall rcorder at boot time, so all you have to do is make a port of your project and you're good to go. Doug -- This .signature sanitized for your protection From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 10 22:21:14 2007 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0CE8116A412 for ; Wed, 10 Jan 2007 22:21:14 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by mx1.freebsd.org (Postfix) with SMTP id 9BBF713C45B for ; Wed, 10 Jan 2007 22:21:13 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 12197 invoked by uid 399); 10 Jan 2007 22:21:13 -0000 Received: from localhost (HELO ?192.168.0.5?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 10 Jan 2007 22:21:13 -0000 X-Originating-IP: 127.0.0.1 Message-ID: <45A566D7.4040907@FreeBSD.org> Date: Wed, 10 Jan 2007 14:21:11 -0800 From: Doug Barton Organization: http://www.freebsd.org/ User-Agent: Thunderbird 1.5.0.8 (X11/20061215) MIME-Version: 1.0 To: Lamont Granquist References: <20070107190616.73dee7b0@vixen42> <45A1DE76.7000201@FreeBSD.org> <20070108185247.2b6e1f69@vixen42> <45A407D1.9030101@FreeBSD.org> <20070109184346.135e0bf4@vixen42> <45A56107.5050205@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@FreeBSD.org, Vulpes Velox Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2007 22:21:14 -0000 Lamont Granquist wrote: > > > On Wed, 10 Jan 2007, Doug Barton wrote: >>> And if you're looking specifically at the /etc/rc.conf config file, what >>> would be more useful would be an /etc/rc.conf.d/ directory. >> >> Good news for you, we already support that. :) I agree that it makes a >> great tool for the "many systems" problem, and could reasonably be >> used for part of the "dynamic laptop" problem too. > > 7-current feature? I'm not seeing it in rc.conf(5) on my RELENG_6-ish > system... It's not documented, but the code is there in /etc/rc.subr: grep 'rc.conf\.d' /etc/rc.subr if [ -f /etc/rc.conf.d/"$_name" ]; then debug "Sourcing /etc/rc.conf.d/${_name}" . /etc/rc.conf.d/"$_name" ... -- This .signature sanitized for your protection From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 10 22:43:56 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6B74C16A407; Wed, 10 Jan 2007 22:43:56 +0000 (UTC) (envelope-from lamont@scriptkiddie.org) Received: from sploit.scriptkiddie.org (sploit.scriptkiddie.org [216.231.47.214]) by mx1.freebsd.org (Postfix) with ESMTP id 385FD13C455; Wed, 10 Jan 2007 22:43:56 +0000 (UTC) (envelope-from lamont@scriptkiddie.org) Received: from sploit (sploit [216.231.47.214]) by sploit.scriptkiddie.org (8.12.11/8.12.11) with ESMTP id l0AMhte9005823; Wed, 10 Jan 2007 14:43:55 -0800 (PST) Date: Wed, 10 Jan 2007 14:43:55 -0800 (PST) From: Lamont Granquist To: Doug Barton In-Reply-To: <45A566D7.4040907@FreeBSD.org> Message-ID: References: <20070107190616.73dee7b0@vixen42> <45A1DE76.7000201@FreeBSD.org> <20070108185247.2b6e1f69@vixen42> <45A407D1.9030101@FreeBSD.org> <20070109184346.135e0bf4@vixen42> <45A56107.5050205@FreeBSD.org> <45A566D7.4040907@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org, Vulpes Velox Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2007 22:43:56 -0000 On Wed, 10 Jan 2007, Doug Barton wrote: > Lamont Granquist wrote: >> On Wed, 10 Jan 2007, Doug Barton wrote: >>>> And if you're looking specifically at the /etc/rc.conf config file, what >>>> would be more useful would be an /etc/rc.conf.d/ directory. >>> >>> Good news for you, we already support that. :) I agree that it makes a >>> great tool for the "many systems" problem, and could reasonably be >>> used for part of the "dynamic laptop" problem too. >> >> 7-current feature? I'm not seeing it in rc.conf(5) on my RELENG_6-ish >> system... > > It's not documented, but the code is there in /etc/rc.subr: > > grep 'rc.conf\.d' /etc/rc.subr > if [ -f /etc/rc.conf.d/"$_name" ]; then > debug "Sourcing /etc/rc.conf.d/${_name}" > . /etc/rc.conf.d/"$_name" > ... If i understand that correctly its not *exactly* what i was looking for, but its better than a monolithic /etc/rc.conf It looks like you must put /etc/rc.d/inetd config into either /etc/rc.conf or /etc/rc.config.d/inetd. That means that if you've got two different orthogonal applications runing on the same server which both need to run something orthogonal out of inetd then they still wind up needing to do edits to the same config file to get inetd configured correctly. I'd rather see /etc/rc.config.d/app01 and /etc/rc.config.d/app02 both able to tweak inetd settings. Of course there is the possibility that app01 and app02 could drop mutually conflicting inetd setttings, but you've got that problem anyway in the existing scheme... Basically I like self-containment around a top-down role that the server plays ('i am an ftp server') not necessarily around a bottom-up subsystem like inetd... YMMV. From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 10 22:55:00 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1A62216A412 for ; Wed, 10 Jan 2007 22:55:00 +0000 (UTC) (envelope-from SRS0=e45MbK=GT=vvelox.net=v.velox@yourhostingaccount.com) Received: from mailout20.yourhostingaccount.com (mailout20.yourhostingaccount.com [65.254.253.166]) by mx1.freebsd.org (Postfix) with ESMTP id E292813C44B for ; Wed, 10 Jan 2007 22:54:59 +0000 (UTC) (envelope-from SRS0=e45MbK=GT=vvelox.net=v.velox@yourhostingaccount.com) Received: from scan08.yourhostingaccount.com ([10.1.1.238] helo=scan08.yourhostingaccount.com) by mailout20.yourhostingaccount.com with esmtp (Exim) id 1H4mLT-0000qg-4O for freebsd-hackers@freebsd.org; Wed, 10 Jan 2007 17:54:59 -0500 Received: from authsmtp08.yourhostingaccount.com ([10.1.18.8] ident=exim) by scan08.yourhostingaccount.com with spamscanlookuphost (Exim) id 1H4mLS-0001qy-TG for freebsd-hackers@freebsd.org; Wed, 10 Jan 2007 17:54:58 -0500 Received: from authsmtp08.yourhostingaccount.com ([10.1.18.8] helo=authsmtp08.yourhostingaccount.com) by scan08.yourhostingaccount.com with esmtp (Exim) id 1H4mLS-0001qu-HU for freebsd-hackers@freebsd.org; Wed, 10 Jan 2007 17:54:58 -0500 Received: from [69.92.217.33] (helo=vixen42) by authsmtp08.yourhostingaccount.com with esmtpa (Exim) id 1H4mLS-0001DV-5V; Wed, 10 Jan 2007 17:54:58 -0500 Date: Wed, 10 Jan 2007 16:54:59 -0600 From: Vulpes Velox To: Doug Barton Message-ID: <20070110165459.218f4a9e@vixen42> In-Reply-To: <45A56539.9070204@FreeBSD.org> References: <20070107190616.73dee7b0@vixen42> <45A1DE76.7000201@FreeBSD.org> <20070108185247.2b6e1f69@vixen42> <45A407D1.9030101@FreeBSD.org> <20070109184346.135e0bf4@vixen42> <45A56539.9070204@FreeBSD.org> X-Mailer: Claws Mail 2.7.0 (GTK+ 2.10.7; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-EN-UserInfo: 0d1ca1697cdb7a831d4877828571b7ab:1570f0de6936c69fef9e164fffc541bc X-EN-AuthUser: vvelox2 Sender: Vulpes Velox Cc: freebsd-hackers@freebsd.org Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2007 22:55:00 -0000 On Wed, 10 Jan 2007 14:14:17 -0800 Doug Barton wrote: > Vulpes Velox wrote: > > > There will be no massive patch for it, given it involves little > > more than the inclusion of a single rc.d file and a bit of > > documentation. > > In that case, you'll be glad to know that the base in 6.x and newer > already supports running a local rc.d script in the overall rcorder > at boot time, so all you have to do is make a port of your project > and you're good to go. I though ports sticking stuff in /etc was considered very improper and thus non-commitable? From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 10 23:06:24 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CD53416A416 for ; Wed, 10 Jan 2007 23:06:24 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.freebsd.org (Postfix) with ESMTP id 7BB9513C441 for ; Wed, 10 Jan 2007 23:06:17 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id l0AN5oZe088666; Wed, 10 Jan 2007 18:05:50 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: "Brad L. Chisholm" Date: Wed, 10 Jan 2007 17:53:24 -0500 User-Agent: KMail/1.9.4 References: <20070110215207.GA85834@bsdone.bsdwins.com> In-Reply-To: <20070110215207.GA85834@bsdone.bsdwins.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200701101753.24716.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [192.168.0.1]); Wed, 10 Jan 2007 18:05:50 -0500 (EST) X-Virus-Scanned: ClamAV 0.88.3/2433/Wed Jan 10 13:28:34 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-hackers@freebsd.org Subject: Re: Kernel hang on 6.x X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2007 23:06:24 -0000 On Wednesday 10 January 2007 16:52, Brad L. Chisholm wrote: > On Thu, 4 Jan 2007 12:53:47 -0500, John Baldwin wrote: > > On Thursday 04 January 2007 10:27, Brian Dean wrote: > > > > > > I believe that I can generate a kernel dump. We tried this yesterday > > > but didn't have a dump device configured. > > > > If this is 6.x, turn on minidumps via the sysctl. The dump size normally is > > the size of RAM. With minidumps it can be a lot smaller. If you get a dump, > > let me know and I'll point you at some gdb scripts to generate 'ps' type > > output, etc. > > > > I work with Brian, and have been helping him analyze this problem. We have > been able to generate kernel dumps, and have also done some additional > analysis under ddb. Here is a summary of our analysis so far. Suggestions > as to how to proceed from here are most welcome. How much swap do you have? You might have run out of buckets in the swap_zone before you ran out of swap space, in which case the kernel deadlocks rather than killing the hog like it does when it runs out of swap space. I added a printf to catch this on HEAD recently that will be MFC'd soonish. You can try bumping up kern.maxswzone (loader tunable). -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 10 23:37:31 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B6A0916A55A for ; Wed, 10 Jan 2007 23:37:30 +0000 (UTC) (envelope-from SRS0=e45MbK=GT=vvelox.net=v.velox@yourhostingaccount.com) Received: from mailout16.yourhostingaccount.com (mailout16.yourhostingaccount.com [65.254.253.133]) by mx1.freebsd.org (Postfix) with ESMTP id 06B2D13C467 for ; Wed, 10 Jan 2007 23:37:29 +0000 (UTC) (envelope-from SRS0=e45MbK=GT=vvelox.net=v.velox@yourhostingaccount.com) Received: from scan08.yourhostingaccount.com ([10.1.1.238] helo=scan08.yourhostingaccount.com) by mailout16.yourhostingaccount.com with esmtp (Exim) id 1H4n0b-00040K-CQ for freebsd-hackers@freebsd.org; Wed, 10 Jan 2007 18:37:29 -0500 Received: from authsmtp09.yourhostingaccount.com ([10.1.18.9] ident=exim) by scan08.yourhostingaccount.com with spamscanlookuphost (Exim) id 1H4n0a-0000U4-4G for freebsd-hackers@freebsd.org; Wed, 10 Jan 2007 18:37:28 -0500 Received: from authsmtp09.yourhostingaccount.com ([10.1.18.9] helo=authsmtp09.yourhostingaccount.com) by scan08.yourhostingaccount.com with esmtp (Exim) id 1H4n0Y-0000U0-Lp for freebsd-hackers@freebsd.org; Wed, 10 Jan 2007 18:37:26 -0500 Received: from [69.92.217.33] (helo=vixen42) by authsmtp09.yourhostingaccount.com with esmtpa (Exim) id 1H4n0X-0001oY-Nd; Wed, 10 Jan 2007 18:37:26 -0500 Date: Wed, 10 Jan 2007 17:37:26 -0600 From: Vulpes Velox To: Lamont Granquist Message-ID: <20070110173726.466bdc48@vixen42> In-Reply-To: References: <20070107190616.73dee7b0@vixen42> <45A1DE76.7000201@FreeBSD.org> <20070108185247.2b6e1f69@vixen42> <45A407D1.9030101@FreeBSD.org> <20070109184346.135e0bf4@vixen42> X-Mailer: Claws Mail 2.7.0 (GTK+ 2.10.7; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-EN-UserInfo: 0d1ca1697cdb7a831d4877828571b7ab:1570f0de6936c69fef9e164fffc541bc X-EN-AuthUser: vvelox2 Sender: Vulpes Velox Cc: freebsd-hackers@freebsd.org, Doug Barton Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2007 23:37:31 -0000 On Wed, 10 Jan 2007 13:26:57 -0800 (PST) Lamont Granquist wrote: > > > > On Tue, 9 Jan 2007, Vulpes Velox wrote: > > The why is because I like centralized management and it would be > > really handy for that. For my use, it would be handy in regards > > to my laptops. > > > > I feel better central management is extreme significant. If I had > > nothing more to say than "this would be neat!" we would not still > > be talking. Right now I am just poking around for other people > > > > I regards to searching the archives, I am not seeing any thing in > > regards to LDAP outside of NSS recently. I am also not finding any > > thing in regards to dynamically and automatically building various > > config files. > > Why are you doing this in the FreeBSD rc scripts directly? Why not > install cfengine and work on making cfengine play better with > database-driven config? I've looked at it once a long time ago and have looked at it again today. It has never held my interest for too long. I find perl and LDAP much more interesting. More user friendly as well. > And if you're looking specifically at the /etc/rc.conf config file, > what would be more useful would be an /etc/rc.conf.d/ directory. > That gets away from the need to tweak and edit the /etc/rc.conf > config file with multiple inputs tweaking a single file. Instead > you can drop whole orthogonal fragments into /etc/rc.conf.d/inetd > to manage the inetd config which would make it more friendly to > radmind-like approaches. It also makes it easier to use with > cfengine since orthogonal cfengine modules aren't doing editfiles > touches to the same files. The /etc/cron.d directory that (most?) > linux distros have is similarly very useful to drop in files that > contain completely orthogonal config (and may be written by > entirely different config management tools -- e.g. system config > management vs. application deployment/management), and > the /etc/periodic functionality is not flexible enough to cover all > cases. This honestly sounds like a massive and complete pain in the ass. I don't even see how this is remote admin friendly. It just means way more to muck around with. If cfengine can not generate rc.conf in a nice manner, it seems more like a problem with cfengine. On a similar note, rc.conf.local supported? I saw it referenced in the man file for rc.conf, but never hear any thing about it and I've not finished picking rc.subr apart yet. From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 10 23:47:10 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A57D616A407 for ; Wed, 10 Jan 2007 23:47:10 +0000 (UTC) (envelope-from SRS0=e45MbK=GT=vvelox.net=v.velox@yourhostingaccount.com) Received: from mailout09.yourhostingaccount.com (mailout09.yourhostingaccount.com [65.254.253.72]) by mx1.freebsd.org (Postfix) with ESMTP id 62A2A13C45A for ; Wed, 10 Jan 2007 23:47:10 +0000 (UTC) (envelope-from SRS0=e45MbK=GT=vvelox.net=v.velox@yourhostingaccount.com) Received: from scan07.yourhostingaccount.com ([10.1.1.237] helo=scan07.yourhostingaccount.com) by mailout09.yourhostingaccount.com with esmtp (Exim) id 1H4n9x-0002iA-Mn for freebsd-hackers@freebsd.org; Wed, 10 Jan 2007 18:47:09 -0500 Received: from authsmtp10.yourhostingaccount.com ([10.1.18.10] ident=exim) by scan07.yourhostingaccount.com with spamscanlookuphost (Exim) id 1H4n9x-0002XT-Ir for freebsd-hackers@freebsd.org; Wed, 10 Jan 2007 18:47:09 -0500 Received: from authsmtp10.yourhostingaccount.com ([10.1.18.10] helo=authsmtp10.yourhostingaccount.com) by scan07.yourhostingaccount.com with esmtp (Exim) id 1H4n9x-0002XP-2s for freebsd-hackers@freebsd.org; Wed, 10 Jan 2007 18:47:09 -0500 Received: from [69.92.217.33] (helo=vixen42) by authsmtp10.yourhostingaccount.com with esmtpa (Exim) id 1H4n9w-0006rt-2c; Wed, 10 Jan 2007 18:47:08 -0500 Date: Wed, 10 Jan 2007 17:47:09 -0600 From: Vulpes Velox To: Doug Barton Message-ID: <20070110174709.534b1f16@vixen42> In-Reply-To: <45A56107.5050205@FreeBSD.org> References: <20070107190616.73dee7b0@vixen42> <45A1DE76.7000201@FreeBSD.org> <20070108185247.2b6e1f69@vixen42> <45A407D1.9030101@FreeBSD.org> <20070109184346.135e0bf4@vixen42> <45A56107.5050205@FreeBSD.org> X-Mailer: Claws Mail 2.7.0 (GTK+ 2.10.7; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-EN-UserInfo: 0d1ca1697cdb7a831d4877828571b7ab:1570f0de6936c69fef9e164fffc541bc X-EN-AuthUser: vvelox2 Sender: Vulpes Velox Cc: freebsd-hackers@freebsd.org, Lamont Granquist Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2007 23:47:10 -0000 On Wed, 10 Jan 2007 13:56:23 -0800 Doug Barton wrote: > Lamont Granquist wrote: > > > Why are you doing this in the FreeBSD rc scripts directly? Why > > not install cfengine and work on making cfengine play better with > > database-driven config? > > Indeed. For a "many systems" problem, cfengine is a great tool. I > think the OP is more interested in the "dynamically configured > laptop" problem, which is also an interesting/difficult one, but I > don't think it's a good problem for LDAP to solve. It still feels > like "I have LDAP that I want to use as a solution, so what problem > can I point it at?" to me. Stuff like this is what LDAP truely shines for. It keeps everything in a nicely organized manner that is easily accessible and searchable. It is also nicely syncable. > > And if you're looking specifically at the /etc/rc.conf config > > file, what would be more useful would be an /etc/rc.conf.d/ > > directory. > > Good news for you, we already support that. :) I agree that it > makes a great tool for the "many systems" problem, and could > reasonably be used for part of the "dynamic laptop" problem too. Simply put... oh hell no. The rc.conf.d just makes a bloody mess. > > That gets > > away from the need to tweak and edit the /etc/rc.conf config file > > with multiple inputs tweaking a single file. Instead you can > > drop whole orthogonal fragments into /etc/rc.conf.d/inetd to > > manage the inetd config which would make it more friendly to > > radmind-like approaches. It also makes it easier to use with > > cfengine since orthogonal cfengine modules aren't doing editfiles > > touches to the same files. > > Yes yes yes all around. At one time I suggested that we add support > for /usr/local/etc/rc.conf.d and encourage port authors to drop > files in there, but I didn't get much enthusiasm for it. Perhaps > it's time to revisit that? Configuration of for the rc.d scripts should be left to rc.conf. > > The > > /etc/cron.d directory that (most?) linux distros have is > > similarly very useful to drop in files that contain completely > > orthogonal config (and may be written by entirely different > > config management tools -- e.g. system config management vs. > > application deployment/management), and the /etc/periodic > > functionality is not flexible enough to cover all cases. > > That's not a bad idea, but you'll have to find some other > huckleberry to address it, I've got my hands full at the moment. I don't have much to say in this area currently, but I have been kicking around the idea of writing one that pulls from a LDAP database and then logs to SQL for awhile. Not really something to be included in the base system, but would be really interesting. From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 00:11:02 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 33B2816A403 for ; Thu, 11 Jan 2007 00:11:02 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (grnl-static-02-0046.dsl.iowatelecom.net [69.66.56.110]) by mx1.freebsd.org (Postfix) with ESMTP id E807E13C441 for ; Thu, 11 Jan 2007 00:11:01 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.13.8/8.13.8) with ESMTP id l0ANt8e2011382; Wed, 10 Jan 2007 17:55:08 -0600 (CST) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.13.8/8.13.8/Submit) id l0ANt8tj011381; Wed, 10 Jan 2007 17:55:08 -0600 (CST) (envelope-from brooks) Date: Wed, 10 Jan 2007 17:55:08 -0600 From: Brooks Davis To: Vulpes Velox Message-ID: <20070110235508.GB10250@lor.one-eyed-alien.net> References: <20070107190616.73dee7b0@vixen42> <45A1DE76.7000201@FreeBSD.org> <20070108185247.2b6e1f69@vixen42> <45A407D1.9030101@FreeBSD.org> <20070109184346.135e0bf4@vixen42> <45A56539.9070204@FreeBSD.org> <20070110165459.218f4a9e@vixen42> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="qlTNgmc+xy1dBmNv" Content-Disposition: inline In-Reply-To: <20070110165459.218f4a9e@vixen42> User-Agent: Mutt/1.5.11 Cc: freebsd-hackers@freebsd.org, Doug Barton Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 00:11:02 -0000 --qlTNgmc+xy1dBmNv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 10, 2007 at 04:54:59PM -0600, Vulpes Velox wrote: > On Wed, 10 Jan 2007 14:14:17 -0800 > Doug Barton wrote: >=20 > > Vulpes Velox wrote: > >=20 > > > There will be no massive patch for it, given it involves little > > > more than the inclusion of a single rc.d file and a bit of > > > documentation. > >=20 > > In that case, you'll be glad to know that the base in 6.x and newer > > already supports running a local rc.d script in the overall rcorder > > at boot time, so all you have to do is make a port of your project > > and you're good to go. >=20 > I though ports sticking stuff in /etc was considered very improper > and thus non-commitable? It is (mostly). The scripts are in /usr/local/etc/rc.d (or other configurable locations), but are run sorted by rcorder. See a recent copy of /etc/rc for the details. -- Brooks --qlTNgmc+xy1dBmNv Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFpXzbXY6L6fI4GtQRAo7WAJ9eLubVH9Txy0tTYG15XStJSv1o9QCghfak TOc7U/IlpibjWginJdEaqLU= =EgGQ -----END PGP SIGNATURE----- --qlTNgmc+xy1dBmNv-- From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 10 22:21:41 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3A38C16A492; Wed, 10 Jan 2007 22:21:41 +0000 (UTC) (envelope-from blc@bsdwins.com) Received: from bsdone.bsdwins.com (www.bsdwins.com [192.58.184.33]) by mx1.freebsd.org (Postfix) with ESMTP id CD92F13C448; Wed, 10 Jan 2007 22:21:40 +0000 (UTC) (envelope-from blc@bsdwins.com) Received: from bsdone.bsdwins.com (localhost [127.0.0.1]) by bsdone.bsdwins.com (8.13.6/8.13.6) with ESMTP id l0ALq8Ba086131; Wed, 10 Jan 2007 21:52:08 GMT (envelope-from blc@www.bsdwins.com) Received: (from blc@localhost) by bsdone.bsdwins.com (8.13.6/8.13.6/Submit) id l0ALq7uk086130; Wed, 10 Jan 2007 16:52:07 -0500 (EST) (envelope-from blc) Date: Wed, 10 Jan 2007 16:52:07 -0500 From: "Brad L. Chisholm" To: John Baldwin Message-ID: <20070110215207.GA85834@bsdone.bsdwins.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Mailman-Approved-At: Thu, 11 Jan 2007 00:52:40 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: Kernel hang on 6.x X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2007 22:21:41 -0000 On Thu, 4 Jan 2007 12:53:47 -0500, John Baldwin wrote: > On Thursday 04 January 2007 10:27, Brian Dean wrote: > > > > I believe that I can generate a kernel dump. We tried this yesterday > > but didn't have a dump device configured. > > If this is 6.x, turn on minidumps via the sysctl. The dump size normally is > the size of RAM. With minidumps it can be a lot smaller. If you get a dump, > let me know and I'll point you at some gdb scripts to generate 'ps' type > output, etc. > I work with Brian, and have been helping him analyze this problem. We have been able to generate kernel dumps, and have also done some additional analysis under ddb. Here is a summary of our analysis so far. Suggestions as to how to proceed from here are most welcome. Summary ------- There appears to be a VM deadlock, not due to any actual locks or mutexes being held, but due to an inability to satisfy page faults. In our scenario, one huge process is essentially consuming most of the memory on the machine. Depending upon the physical memory configured, that process will consume 1.5-3 times physical memory. When the machine hangs, however, there is still plenty of swap space available. One possibly interesting observation is that the hang always seems to occur when ~14G of swap has been consumed, regardless of the size of physmem (6G, 8G, 16G) or amount of swap (32G, 64G) configured. Dropping to DDB on the serial console, and running "show locks", "show alllocks", and "show lockedvnods" usually indicate that only an sio lock is being held (probably for the serial console). A "ps" indicates that the pagedaemon is in VMWait state, while a number of other processes (including the huge memory process) are in pfault state. We have been able to generate a full core dump, as well as a couple of minidumps with differing hw.physmem settings. We can make these dumps available, if that would help, or we can provide information from gdb on request. We can usually reproduce the hang within 1.5-2 hours, and can provide additional information from ddb, as well. Details ------- Here is an example of a 'top' session that was running when the machine became unresponsive. Note the one huge 'sdsbuild' process. last pid: 3331; load averages: 0.00, 0.27, 0.44 up 0+03:22:40 17:06:05 42 processes: 1 running, 41 sleeping CPU states: 0.0% user, 0.0% nice, 0.8% system, 0.0% interrupt, 99.2% idle Mem: 14G Active, 1115M Inact, 535M Wired, 39M Cache, 214M Buf, 21M Free Swap: 64G Total, 14G Used, 50G Free, 21% Inuse PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND 2698 blc 1 114 0 29579M 14635M pfault 30:40 0.00% sdsbuild 3159 blc 1 5 0 7492K 856K ttyin 0:23 0.00% systat 3158 root 1 96 0 6984K 744K RUN 0:04 0.00% top 2096 root 1 96 0 3656K 104K select 0:02 0.00% rlogind 2699 blc 1 -8 0 2492K 212K piperd 0:01 0.00% tee 1092 root 1 96 0 2692K 168K select 0:01 0.00% cvd 773 root 1 96 0 7712K 600K select 0:01 0.00% ntpd 736 root 1 97 0 3984K 0K select 0:00 0.00% 2525 root 1 96 0 3656K 104K select 0:00 0.00% rlogind 1986 root 1 96 0 3656K 104K select 0:00 0.00% rlogind 707 root 1 96 0 9760K 352K select 0:00 0.00% amd 817 root 1 96 0 9340K 564K select 0:00 0.00% sendmail 657 root 1 96 0 3644K 304K select 0:00 0.00% syslogd 2000 root 1 20 0 9796K 0K pause 0:00 0.00% 825 root 1 -16 0 3664K 336K vmwait 0:00 0.00% cron 2527 blc 1 20 0 960K 0K pause 0:00 0.00% 676 root 1 96 0 4940K 352K select 0:00 0.00% rpcbind 1956 root 1 96 0 6108K 0K select 0:00 0.00% 738 root 1 109 0 2724K 0K select 0:00 0.00% 1987 root 1 8 0 18408K 0K wait 0:00 0.00% 2097 root 1 8 0 18408K 0K wait 0:00 0.00% 2526 root 1 8 0 18408K 0K wait 0:00 0.00% 2098 blc 1 20 0 960K 0K pause 0:00 0.00% 793 root 1 96 0 2516K 152K select 0:00 0.00% usbd 1999 blc 1 8 0 18400K 0K wait 0:00 0.00% 1988 blc 1 20 0 960K 0K pause 0:00 0.00% 2682 blc 1 20 0 964K 0K pause 0:00 0.00% 1982 root 1 5 0 3600K 0K ttyin 0:00 0.00% 1974 root 1 5 0 3600K 0K ttyin 0:00 0.00% 1981 root 1 5 0 3600K 0K ttyin 0:00 0.00% 1978 root 1 5 0 3600K 0K ttyin 0:00 0.00% 1977 root 1 5 0 3600K 0K ttyin 0:00 0.00% 1976 root 1 5 0 3600K 0K ttyin 0:00 0.00% Here is a 'ps' from ddb corresponding to the 'top' session above: db> ps pid ppid pgrp uid state wmesg wchan cmd 3332 817 817 0 N sendmail 3331 825 825 0 N cron 3159 2527 3159 207 S+ ttyin 0xffffff02574d4c10 systat 3158 2000 3158 0 SL+ pfault 0xffffffff809326f8 top 3155 0 0 0 SL mdwait 0xffffff030c9e7800 [md0] 2699 2682 2682 207 S+ piperd 0xffffff004e432000 tee 2698 2682 2682 207 SL+ pfault 0xffffffff809326f8 sdsbuild 2682 2098 2682 207 SW+ pause 0xffffff03253933c0 ksh 2527 2526 2527 207 SW+ pause 0xffffff030b906068 ksh 2526 2525 2526 0 SWs+ wait 0xffffff031af246b0 login 2525 1956 2525 0 Ss select 0xffffffff8091fe50 rlogind 2098 2097 2098 207 SW+ pause 0xffffff030bbc7a70 ksh 2097 2096 2097 0 SWs+ wait 0xffffff030bbc7358 login 2096 1956 2096 0 Ss select 0xffffffff8091fe50 rlogind 2000 1999 2000 0 SW+ pause 0xffffff030663b718 csh 1999 1988 1999 207 SW+ wait 0xffffff030663ba08 su 1988 1987 1988 207 SW+ pause 0xffffff031b2e4718 ksh 1987 1986 1987 0 SWs+ wait 0xffffff031b2e4a08 login 1986 1956 1986 0 Ss select 0xffffffff8091fe50 rlogind 1982 1 1982 0 ?s+ getty 1981 1 1981 0 SWs+ ttyin 0xffffff03e0c42410 getty 1980 1 1980 0 SWs+ ttyin 0xffffff03e0c42010 getty 1979 1 1979 0 SWs+ ttyin 0xffffff03dd03c010 getty 1978 1 1978 0 SWs+ ttyin 0xffffff03e14b6410 getty 1977 1 1977 0 SWs+ ttyin 0xffffff03e0921810 getty 1976 1 1976 0 SWs+ ttyin 0xffffff03e0921410 getty 1975 1 1975 0 SWs+ ttyin 0xffffff03e0200410 getty 1974 1 1974 0 SWs+ ttyin 0xffffff03e0200010 getty 1956 1 1956 0 SWs select 0xffffffff8091fe50 inetd 1092 1 1092 0 Ss select 0xffffffff8091fe50 cvd 825 1 825 0 SLs vmwait 0xffffffff809326f8 cron 817 1 817 0 SLs vmwait 0xffffffff809326f8 sendmail 811 1 811 0 SWs select 0xffffffff8091fe50 sshd 793 1 793 0 Ss select 0xffffffff8091fe50 usbd 773 1 773 0 SLs pfault 0xffffffff809326f8 ntpd 745 738 738 0 SW - 0xffffff03e068bc00 nfsd 742 738 738 0 SW - 0xffffff0000f47600 nfsd 741 738 738 0 SW - 0xffffff03e068b400 nfsd 740 738 738 0 SW - 0xffffff03e068b600 nfsd 738 1 738 0 SWs select 0xffffffff8091fe50 nfsd 736 1 736 0 SWs select 0xffffffff8091fe50 mountd 707 1 707 0 SLs pfault 0xffffffff809326f8 amd 676 1 676 0 Ss select 0xffffffff8091fe50 rpcbind 657 1 657 0 Ss select 0xffffffff8091fe50 syslogd 547 1 547 0 SWs select 0xffffffff8091fe50 devd 41 0 0 0 SL - 0xffffffffbf5ddbe4 [schedcpu] 40 0 0 0 SL sdflush 0xffffffff80931ae0 [softdepflush] 39 0 0 0 SL syncer 0xffffffff8089aa20 [syncer] 38 0 0 0 SL vlruwt 0xffffff03dccfc6b0 [vnlru] 37 0 0 0 SL psleep 0xffffffff80920718 [bufdaemon] 36 0 0 0 SL pgzero 0xffffffff80933460 [pagezero] 35 0 0 0 SL psleep 0xffffffff80932b2c [vmdaemon] 34 0 0 0 SL VMWait 0xffffffff80932ae0 [pagedaemon] 33 0 0 0 WL [swi0: sio] 32 0 0 0 WL [irq15: ata1] 31 0 0 0 WL [irq14: ata0] 30 0 0 0 SL usbevt 0xffffffff94066420 [usb1] 29 0 0 0 SL usbtsk 0xffffffff80895750 [usbtask] 28 0 0 0 SL usbevt 0xffffffff94064420 [usb0] 27 0 0 0 WL [irq19: ohci0 ohci1 ] 26 0 0 0 SL idle 0xffffffff940562e0 [mpt_raid0] 25 0 0 0 SL idle 0xffffffff94056000 [mpt_recovery0] 24 0 0 0 WL [irq28: mpt0] 23 0 0 0 SL - 0xffffff0000e2d700 [em3 taskq] 22 0 0 0 SL - 0xffffff0000e2dd00 [em2 taskq] 21 0 0 0 SL - 0xffffff0000e2a200 [em1 taskq] 20 0 0 0 SL - 0xffffff0000e36300 [em0 taskq] 19 0 0 0 WL [irq9: acpi0] 18 0 0 0 WL [swi6: Giant taskq] 9 0 0 0 SL - 0xffffff0000db5000 [thread taskq] 17 0 0 0 WL [swi5: +] 8 0 0 0 SL - 0xffffff0000db5300 [acpi_task_2] 7 0 0 0 SL - 0xffffff0000db5300 [acpi_task_1] 6 0 0 0 SL - 0xffffff0000db5300 [acpi_task_0] 5 0 0 0 SL - 0xffffff0000db5400 [kqueue taskq] 16 0 0 0 WL [swi2: cambio] 15 0 0 0 WL [swi6: task queue] 14 0 0 0 SL - 0xffffffff80893300 [yarrow] 4 0 0 0 SL - 0xffffffff80896468 [g_down] 3 0 0 0 SL - 0xffffffff80896460 [g_up] 2 0 0 0 SL - 0xffffffff80896450 [g_event] 13 0 0 0 WL [swi1: net] 12 0 0 0 WL [swi3: vm] 11 0 0 0 WL [swi4: clock sio] 10 0 0 0 RL CPU 0 [idle] 1 0 1 0 SLs wait 0xffffff03e1566000 [init] 0 0 0 0 SLs vmwait 0xffffffff809326f8 [swapper] Here is where the pagedaemon process appears to be whenever the hang occurs: db> tr 34 Tracing pid 34 tid 100027 td 0xffffff03e1557000 sched_switch() at sched_switch+0x11f mi_switch() at mi_switch+0x14c sleepq_wait() at sleepq_wait+0x2e msleep() at msleep+0x191 swp_pager_meta_build() at swp_pager_meta_build+0x13b swap_pager_putpages() at swap_pager_putpages+0x261 vm_pageout_flush() at vm_pageout_flush+0xde vm_pageout() at vm_pageout+0x1668 fork_exit() at fork_exit+0x87 fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffffffbf56ed00, rbp = 0 --- Here is the lock info from ddb: db> show locks exclusive spin mutex sio r = 0 (0xffffffff8097a100) locked @ /usr/src/sys/dev/sio/sio.c:1390 db> show alllocks db> show lockedvnods Locked vnodes db> show pcpu cpuid = 0 curthread = 0xffffff017f421720: pid 10 "idle" curpcb = 0xffffffffb6ce2d10 fpcurthread = none idlethread = 0xffffff017f421720: pid 10 "idle" spin locks held: exclusive spin mutex sio r = 0 (0xffffffff8097a100) locked @ /usr/src/sys/dev/sio/sio.c:1390 db> show allpcpu Current CPU: 0 cpuid = 0 curthread = 0xffffff017f421720: pid 10 "idle" curpcb = 0xffffffffb6ce2d10 fpcurthread = none idlethread = 0xffffff017f421720: pid 10 "idle" spin locks held: exclusive spin mutex sio r = 0 (0xffffffff8097a100) locked @ /usr/src/sys/dev/sio/sio.c:1390 Here is a 'vmstat -s' snapshot taken as the machine hung: 45794937 cpu context switches 20220635 device interrupts 810196 software interrupts 66195618 traps 6615004 system calls 61 kernel threads created 5940 fork() calls 560 vfork() calls 0 rfork() calls 1851 swap pager pageins 13980 swap pager pages paged in 234711 swap pager pageouts 3670484 swap pager pages paged out 1088 vnode pager pageins 5591 vnode pager pages paged in 0 vnode pager pageouts 0 vnode pager pages paged out 744 page daemon wakeups 301408821 pages examined by the page daemon 3228902 pages reactivated 233903 copy-on-write faults 425 copy-on-write optimized faults 55595560 zero fill pages zeroed 10623188 zero fill pages prezeroed 1878 intransit blocking page faults 66078208 total VM faults taken 0 pages affected by kernel thread creation 377526 pages affected by fork() 1282533 pages affected by vfork() 0 pages affected by rfork() 71450207 pages freed 3805 pages freed by daemon 7974727 pages freed by exiting processes 3577239 pages active 294202 pages inactive 13662 pages in VM cache 106557 pages wired down 10548 pages free 4096 bytes per page 3665219 total name lookups cache hits (75% pos + 0% neg) system 1% per-directory deletions 0%, falsehits 0%, toolong 0% Here is a snapshot of 'sysctl vm' as the machine hung: vm.vmtotal: System wide totals computed every five seconds: (values in kilobytes) =============================================== Processes: (RUNQ: 2 Disk Wait: 1 Page Wait: 1 Sleep: 43) Virtual Memory: (Total: 35242K, Active 30153728K) Real Memory: (Total: 15917288K Active 15540600K) Shared Virtual Memory: (Total: 7128K Active: 6576K) Shared Real Memory: (Total: 2368K Active: 2368K) Free Memory Pages: 96860K vm.loadavg: { 2.67 1.84 1.53 } vm.v_free_min: 25512 vm.v_free_target: 107384 vm.v_free_reserved: 5336 vm.v_inactive_target: 161076 vm.v_cache_min: 107384 vm.v_cache_max: 214768 vm.v_pageout_free_min: 34 vm.pageout_algorithm: 0 vm.swap_enabled: 1 vm.kmem_size_scale: 3 vm.kmem_size_max: 419430400 vm.kmem_size: 419430400 vm.nswapdev: 1 vm.dmmax: 32 vm.swap_async_max: 4 vm.zone_count: 69 vm.zone: ITEM SIZE LIMIT USED FREE REQUESTS FFS2 dinode: 256, 0, 38765, 25060, 633124 FFS1 dinode: 128, 0, 0, 0, 0 FFS inode: 192, 0, 38765, 26355, 633124 Mountpoints: 936, 0, 181, 11, 181 SWAPMETA: 288, 116519, 116519, 0, 116551 rtentry: 264, 0, 40, 30, 72 ripcb: 304, 33792, 0, 24, 18 sackhole: 32, 0, 0, 0, 0 tcpreass: 40, 2184, 0, 0, 0 hostcache: 136, 15372, 17, 39, 20 syncache: 128, 15370, 0, 58, 12 tcptw: 80, 6795, 0, 810, 1595 tcpcb: 752, 33795, 34, 21, 1655 inpcb: 304, 33792, 34, 794, 1655 udpcb: 304, 33792, 204, 24, 3543 ipq: 56, 1071, 0, 126, 2604 unpcb: 192, 33800, 12, 28, 577 socket: 616, 33792, 250, 26, 5794 KNOTE: 120, 0, 0, 62, 6251 PIPE: 768, 0, 2, 23, 2416 NFSNODE: 816, 0, 9012, 7898, 65144 NFSMOUNT: 584, 0, 174, 15, 174 DIRHASH: 1024, 0, 1219, 293, 2098 L VFS Cache: 327, 0, 729, 687, 10160 S VFS Cache: 104, 0, 52929, 30231, 714353 NAMEI: 1024, 0, 4, 8, 1395238 VNODEPOLL: 152, 0, 0, 0, 0 VNODE: 648, 0, 47992, 34748, 698512 ata_composit: 376, 0, 0, 0, 0 ata_request: 336, 0, 0, 22, 24 g_bio: 216, 0, 0, 1818, 1418264 ACL UMA zone: 388, 0, 0, 0, 0 mbuf_jumbo_1: 16384, 0, 0, 0, 0 mbuf_jumbo_9: 9216, 0, 0, 0, 0 mbuf_jumbo_p: 4096, 0, 0, 0, 0 mbuf_cluster: 2048, 33792, 1152, 72, 7441 mbuf: 256, 0, 1169, 121, 2197657 mbuf_packet: 256, 0, 1152, 138, 1780924 VMSPACE: 544, 0, 47, 16, 6504 UPCALL: 88, 0, 0, 0, 0 KSEGRP: 136, 0, 112, 18, 112 THREAD: 608, 0, 112, 8, 112 PROC: 856, 0, 88, 24, 6562 Files: 120, 0, 149, 68, 223724 4096: 4096, 0, 351, 8, 9244 2048: 2048, 0, 29, 137, 3815 1024: 1024, 0, 727, 17, 1059555 512: 512, 0, 593, 149, 16584 256: 256, 0, 753, 117, 57787 128: 128, 0, 5084, 1325, 291338 64: 64, 0, 3596, 436, 53093 32: 32, 0, 1895, 226, 27977 16: 16, 0, 3166, 194, 389649 mt_zone: 64, 0, 203, 77, 203 DP fakepg: 120, 0, 0, 0, 0 PV ENTRY: 48, 5678064, 3753306, 116118, 106702024 MAP ENTRY: 112, 0, 1707, 207, 273770 KMAP ENTRY: 112, 98406, 16, 116, 11646 MAP: 352, 0, 7, 15, 7 VM OBJECT: 224, 0, 41676, 8678, 178636 128 Bucket: 1048, 0, 240, 306, 1081 64 Bucket: 536, 0, 38, 32, 73 32 Bucket: 280, 0, 16, 26, 39 16 Bucket: 152, 0, 30, 20, 43 UMA Hash: 256, 0, 5, 10, 8 UMA RCntSlab: 128, 0, 612, 26, 619 UMA Slabs: 128, 0, 4452, 3668, 14083 UMA Zones: 184, 0, 67, 13, 67 UMA Kegs: 240, 0, 67, 8, 67 vm.old_contigmalloc: 0 vm.swap_idle_threshold2: 10 vm.swap_idle_threshold1: 2 vm.exec_map_entries: 16 vm.stats.misc.zero_page_count: 1415 vm.stats.misc.cnt_prezero: 6936472 vm.stats.vm.v_kthreadpages: 0 vm.stats.vm.v_rforkpages: 0 vm.stats.vm.v_vforkpages: 1282533 vm.stats.vm.v_forkpages: 377616 vm.stats.vm.v_kthreads: 61 vm.stats.vm.v_rforks: 0 vm.stats.vm.v_vforks: 560 vm.stats.vm.v_forks: 5941 vm.stats.vm.v_interrupt_free_min: 2 vm.stats.vm.v_pageout_free_min: 34 vm.stats.vm.v_cache_max: 214768 vm.stats.vm.v_cache_min: 107384 vm.stats.vm.v_cache_count: 13662 vm.stats.vm.v_inactive_count: 294202 vm.stats.vm.v_inactive_target: 161076 vm.stats.vm.v_active_count: 3577241 vm.stats.vm.v_wire_count: 106556 vm.stats.vm.v_free_count: 10547 vm.stats.vm.v_free_min: 25512 vm.stats.vm.v_free_target: 107384 vm.stats.vm.v_free_reserved: 5336 vm.stats.vm.v_page_count: 4035617 vm.stats.vm.v_page_size: 4096 vm.stats.vm.v_tfree: 71450323 vm.stats.vm.v_pfree: 7974792 vm.stats.vm.v_dfree: 3805 vm.stats.vm.v_pdpages: 301408821 vm.stats.vm.v_pdwakeups: 744 vm.stats.vm.v_reactivated: 3228902 vm.stats.vm.v_intrans: 1878 vm.stats.vm.v_vnodepgsout: 0 vm.stats.vm.v_vnodepgsin: 5591 vm.stats.vm.v_vnodeout: 0 vm.stats.vm.v_vnodein: 1088 vm.stats.vm.v_swappgsout: 3670484 vm.stats.vm.v_swappgsin: 13980 vm.stats.vm.v_swapout: 234711 vm.stats.vm.v_swapin: 1851 vm.stats.vm.v_ozfod: 10623195 vm.stats.vm.v_zfod: 55595610 vm.stats.vm.v_cow_optim: 425 vm.stats.vm.v_cow_faults: 233938 vm.stats.vm.v_vm_faults: 66078331 vm.stats.sys.v_soft: 810461 vm.stats.sys.v_intr: 20220649 vm.stats.sys.v_syscall: 6616609 vm.stats.sys.v_trap: 66195742 vm.stats.sys.v_swtch: 45795521 vm.v_free_severe: 15424 vm.max_proc_mmap: 37449 vm.old_msync: 0 vm.msync_flush_flags: 3 vm.boot_pages: 48 vm.pageout_lock_miss: 0 vm.disable_swapspace_pageouts: 0 vm.defer_swapspace_pageouts: 0 vm.swap_idle_enabled: 0 vm.pageout_stats_interval: 5 vm.pageout_full_stats_interval: 20 vm.pageout_stats_max: 107384 vm.max_launder: 32 vm.idlezero_maxrun: 16 vm.idlezero_enable: 1 vm.kvm_free: 1042280448 vm.kvm_size: 2147479552 --- Brad Chisholm blc@bsdwins.com From owner-freebsd-hackers@FreeBSD.ORG Wed Jan 10 22:57:40 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7F0AB16A492 for ; Wed, 10 Jan 2007 22:57:40 +0000 (UTC) (envelope-from chewy509@lycos.com) Received: from smail1.lycosmail.lycos.com (bos-mail-smail2.bos.lycos.com [209.202.208.42]) by mx1.freebsd.org (Postfix) with ESMTP id 2ADB613C44C for ; Wed, 10 Jan 2007 22:57:39 +0000 (UTC) (envelope-from chewy509@lycos.com) Received: from bos-mail-wwl8.lycosmail.com (bos-mail-wwl8b.bos.lycos.com [10.124.64.88]) by bos-mail-smail2.lycosmail.com (8.13.6/8.9.1) with ESMTP id l0AMqmcF014662; Wed, 10 Jan 2007 17:52:48 -0500 Received: (from hanadmin@localhost) by bos-mail-wwl8.lycosmail.com (8.12.9/8.9.1) id l0AMw5es004625 for ; Thu, 11 Jan 2007 07:58:05 +0900 Content-Transfer-Encoding: 8bit X-Originating-IP: [210.11.58.16] From: "darran kartaschew" Organization: Lycos. Inc. Priority: Normal To: X-Mailer: Daum Web Mailer 1.1 Date: Wed, 10 Jan 2007 17:58:05 -0500 (EST) Message-Id: <20070110175805.HM.0000000000000GI@chewy509.bos-mail-wwl8.lycos.com> Errors-To: X-Hanmail-Attr: fc=1 X-Mailman-Approved-At: Thu, 11 Jan 2007 00:52:51 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: sbrk vs mmap X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jan 2007 22:57:40 -0000 > Is there a particular reason you have to use assembly and not C? The whole application is in assembly (some of us still enjoy coding in assembly), and rather not link to libc if I don't have to. (There are about 5 syscalls for the entire application, porting between each OS's hasn't been that hard). The app in question, also has been ported to Linux, Windows x64, Solaris and now FreeBSD, and the mmap() call is the last one to get working... > You can call C functions from assembly and vice versa. > You also forgot to include > one of MAP_SHARED or MAP_PRIVATE in your flags. Thanks, I'll try including one of the those flags. Darran _________________________________________________________________ [1]Free Movies 100's of Free Feature Length Films - Meet Friends, Watch Movies & Win! References 1. http://cinema.lycos.com/?if_Event=mail From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 00:19:50 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0AD1416A40F; Thu, 11 Jan 2007 00:19:50 +0000 (UTC) (envelope-from blc@bsdwins.com) Received: from bsdone.bsdwins.com (www.bsdwins.com [192.58.184.33]) by mx1.freebsd.org (Postfix) with ESMTP id C81F613C44B; Thu, 11 Jan 2007 00:19:49 +0000 (UTC) (envelope-from blc@bsdwins.com) Received: from bsdone.bsdwins.com (localhost [127.0.0.1]) by bsdone.bsdwins.com (8.13.6/8.13.6) with ESMTP id l0B0FYcP004572; Thu, 11 Jan 2007 00:15:34 GMT (envelope-from blc@www.bsdwins.com) Received: (from blc@localhost) by bsdone.bsdwins.com (8.13.6/8.13.6/Submit) id l0B0FYG7004571; Wed, 10 Jan 2007 19:15:34 -0500 (EST) (envelope-from blc) Date: Wed, 10 Jan 2007 19:15:34 -0500 From: "Brad L. Chisholm" To: John Baldwin Message-ID: <20070111001534.GA319@bsdone.bsdwins.com> References: <20070110215207.GA85834@bsdone.bsdwins.com> <200701101753.24716.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200701101753.24716.jhb@freebsd.org> User-Agent: Mutt/1.4.2.1i X-Mailman-Approved-At: Thu, 11 Jan 2007 00:54:48 +0000 Cc: "Brad L. Chisholm" , freebsd-hackers@freebsd.org Subject: Re: Kernel hang on 6.x X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 00:19:50 -0000 On Wed, Jan 10, 2007 at 05:53:24PM -0500, John Baldwin wrote: > On Wednesday 10 January 2007 16:52, Brad L. Chisholm wrote: > > > > I work with Brian, and have been helping him analyze this problem. We have > > been able to generate kernel dumps, and have also done some additional > > analysis under ddb. Here is a summary of our analysis so far. Suggestions > > as to how to proceed from here are most welcome. > > How much swap do you have? You might have run out of buckets in the > swap_zone before you ran out of swap space, in which case the kernel > deadlocks rather than killing the hog like it does when it runs out of > swap space. I added a printf to catch this on HEAD recently that will > be MFC'd soonish. You can try bumping up kern.maxswzone (loader tunable). > It has a 32GB swap partition. We have also run it configured with an additional 32GB swap file, for a total of 64GB. Changing the amount of swap did not seem to affect the hang. However, as I mentioned in my previous post, the hang appears to always occur when ~14GB of swap have been consumed, regardless of the amount of swap or physmen configured. This does make it sound like a limit (such as swap_zone buckets) has been reached. I notice the following in the vm.zone output captured just prior to a hang. Does this value correspond to the swap_zone you were referring to? This looks like a limit may have been reached. SWAPMETA: 288, 116519, 116519, 0, 116543 I don't seem to be able to query kern.maxswzone on our 6.2-BETA2 image: # sysctl kern.maxswzone sysctl: unknown oid 'kern.maxswzone' Is it available in 6.x, or is it something newer? Thanks! --- Brad Chisholm blc@bsdwins.com From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 01:00:06 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A087316A412; Thu, 11 Jan 2007 01:00:06 +0000 (UTC) (envelope-from lamont@scriptkiddie.org) Received: from sploit.scriptkiddie.org (sploit.scriptkiddie.org [216.231.47.214]) by mx1.freebsd.org (Postfix) with ESMTP id 1A1DC13C458; Thu, 11 Jan 2007 01:00:06 +0000 (UTC) (envelope-from lamont@scriptkiddie.org) Received: from sploit (sploit [216.231.47.214]) by sploit.scriptkiddie.org (8.12.11/8.12.11) with ESMTP id l0B104Zu006423; Wed, 10 Jan 2007 17:00:04 -0800 (PST) Date: Wed, 10 Jan 2007 17:00:04 -0800 (PST) From: Lamont Granquist To: Vulpes Velox In-Reply-To: <20070110173726.466bdc48@vixen42> Message-ID: References: <20070107190616.73dee7b0@vixen42> <45A1DE76.7000201@FreeBSD.org> <20070108185247.2b6e1f69@vixen42> <45A407D1.9030101@FreeBSD.org> <20070109184346.135e0bf4@vixen42> <20070110173726.466bdc48@vixen42> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org, Doug Barton Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 01:00:06 -0000 On Wed, 10 Jan 2007, Vulpes Velox wrote: >> And if you're looking specifically at the /etc/rc.conf config file, >> what would be more useful would be an /etc/rc.conf.d/ directory. >> That gets away from the need to tweak and edit the /etc/rc.conf >> config file with multiple inputs tweaking a single file. Instead >> you can drop whole orthogonal fragments into /etc/rc.conf.d/inetd >> to manage the inetd config which would make it more friendly to >> radmind-like approaches. It also makes it easier to use with >> cfengine since orthogonal cfengine modules aren't doing editfiles >> touches to the same files. The /etc/cron.d directory that (most?) >> linux distros have is similarly very useful to drop in files that >> contain completely orthogonal config (and may be written by >> entirely different config management tools -- e.g. system config >> management vs. application deployment/management), and >> the /etc/periodic functionality is not flexible enough to cover all >> cases. > > This honestly sounds like a massive and complete pain in the ass. I > don't even see how this is remote admin friendly. It just means way > more to muck around with. > > If cfengine can not generate rc.conf in a nice manner, it seems more > like a problem with cfengine. Actually, cfengine is perfectly capable of doing that, it has an obscenely flexible ability to edit files 'in place' to do this kind of tweaking and tuning to manage monolithic config files like rc.conf or inetd.conf which may have orthogonal configuration inputs from different apps running on the machine. The problem is that with orthogonal inputs to the same config file it becomes more likely that entirely seperate pieces of config will be twiddling the same file, and those pieces of code will be built and maintained by entirely different people and that increases the chances of simple file editing errors. Once you start hitting the problem of dozens of system admins trying to collaboratively manage 1000s of systems these kinds of issues come up. They're not apparent when you've got single administrative owners for all the machines. The radmind model of system configuration alone, however, doesn't let you do this since it is built around pushing only whole files. You can construct all the different flavors of the monolithic files that you're managing and try to make sure that the correct image gets on the correct system but that requires higher-level wrapping -- or you can just have radmind call out to cfengine to construct files like this. Still, avoiding monolithic files makes system configuration friendlier to those who use the radmind-approach. From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 01:01:50 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B56FC16A403 for ; Thu, 11 Jan 2007 01:01:50 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id A038E13C46B for ; Thu, 11 Jan 2007 01:01:50 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 7B33E1A4D8D; Wed, 10 Jan 2007 17:01:50 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id E185F513F8; Wed, 10 Jan 2007 20:01:49 -0500 (EST) Date: Wed, 10 Jan 2007 20:01:49 -0500 From: Kris Kennaway To: Attila Nagy Message-ID: <20070111010149.GA2704@xor.obsecurity.org> References: <45A0229F.7070701@fsn.hu> <45a03a95.08FguubdCa9DFcxj%perryh@pluto.rain.com> <45A0DD27.4020704@fsn.hu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Q68bSM7Ycu6FN28Q" Content-Disposition: inline In-Reply-To: <45A0DD27.4020704@fsn.hu> User-Agent: Mutt/1.4.2.2i Cc: freebsd-hackers@freebsd.org, perryh@pluto.rain.com Subject: Re: ufs_rename: fvp == tvp (can't happen), but it did X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 01:01:50 -0000 --Q68bSM7Ycu6FN28Q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 07, 2007 at 12:44:39PM +0100, Attila Nagy wrote: > On 2007.01.07. 1:11, perryh@pluto.rain.com wrote: > >It sounds as if the caller of ufs_rename() is confused. You could > >try setting a breakpoint on the printf(), or change it to a panic() > >to get a dump, and try to figure out who the caller is and what is > >going on. > > =20 > Yes this would be very good, especially if this wouldn't be a production= =20 > machine or if I could reproduce this on a test system. But neither of=20 > this are true. :( >=20 > Maybe I will try it on a sleepless night, in the maintenance window,=20 > thanks for the idea. Try forcing a fsck, sometimes bizarre FS panics are due to filesystem corruption. Kris --Q68bSM7Ycu6FN28Q Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.1 (FreeBSD) iD8DBQFFpYx9Wry0BWjoQKURAh/tAJ0SOZOSS6zLBes+XllaLe+lyzf9bgCfdJxX Q0u5cg8FLKFFdCZr51ReOMU= =1qLH -----END PGP SIGNATURE----- --Q68bSM7Ycu6FN28Q-- From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 01:10:37 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E9C6C16A523; Thu, 11 Jan 2007 01:10:36 +0000 (UTC) (envelope-from lamont@scriptkiddie.org) Received: from sploit.scriptkiddie.org (sploit.scriptkiddie.org [216.231.47.214]) by mx1.freebsd.org (Postfix) with ESMTP id B6AE213C474; Thu, 11 Jan 2007 01:10:36 +0000 (UTC) (envelope-from lamont@scriptkiddie.org) Received: from sploit (sploit [216.231.47.214]) by sploit.scriptkiddie.org (8.12.11/8.12.11) with ESMTP id l0B1Aa79006476; Wed, 10 Jan 2007 17:10:36 -0800 (PST) Date: Wed, 10 Jan 2007 17:10:36 -0800 (PST) From: Lamont Granquist To: Vulpes Velox In-Reply-To: <20070110174709.534b1f16@vixen42> Message-ID: References: <20070107190616.73dee7b0@vixen42> <45A1DE76.7000201@FreeBSD.org> <20070108185247.2b6e1f69@vixen42> <45A407D1.9030101@FreeBSD.org> <20070109184346.135e0bf4@vixen42> <45A56107.5050205@FreeBSD.org> <20070110174709.534b1f16@vixen42> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org, Doug Barton Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 01:10:37 -0000 On Wed, 10 Jan 2007, Vulpes Velox wrote: > On Wed, 10 Jan 2007 13:56:23 -0800 > Doug Barton wrote: >> Lamont Granquist wrote: >>> Why are you doing this in the FreeBSD rc scripts directly? Why >>> not install cfengine and work on making cfengine play better with >>> database-driven config? >> >> Indeed. For a "many systems" problem, cfengine is a great tool. I >> think the OP is more interested in the "dynamically configured >> laptop" problem, which is also an interesting/difficult one, but I >> don't think it's a good problem for LDAP to solve. It still feels >> like "I have LDAP that I want to use as a solution, so what problem >> can I point it at?" to me. > > Stuff like this is what LDAP truely shines for. It keeps everything > in a nicely organized manner that is easily accessible and searchable. I agree that database-driven config management is good. I do not agree that LDAP is the best way to go about doing it since LDAP works best as a read-mostly directory service and not as an mixed-read/write database which is what I've seen these kinds of configuration management databases scale and turn into. LDAP is great for stuff that barely ever changes. When you add SOX audit trails and error reporting and other junk into the database LDAP stops being appropriate. I also don't understand the focus on dynamically generating /etc/rc.conf since that is actually not what I want in my database. Inside my database I want to configure a machine as an ftp server or a web server and deal with the high-level roles that the machine plays. In order to generate an rc.conf file I want to take the roles as inputs and construct the rc.conf file specific to the machine. From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 02:10:48 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 43A1516A580 for ; Thu, 11 Jan 2007 02:10:48 +0000 (UTC) (envelope-from SRS0=LVA8ua=GU=vvelox.net=v.velox@yourhostingaccount.com) Received: from mailout06.yourhostingaccount.com (mailout06.yourhostingaccount.com [65.254.253.51]) by mx1.freebsd.org (Postfix) with ESMTP id 0149813C457 for ; Thu, 11 Jan 2007 02:10:47 +0000 (UTC) (envelope-from SRS0=LVA8ua=GU=vvelox.net=v.velox@yourhostingaccount.com) Received: from scan03.yourhostingaccount.com ([10.1.1.233] helo=scan03.yourhostingaccount.com) by mailout06.yourhostingaccount.com with esmtp (Exim) id 1H4pAK-0004Mg-Q3 for freebsd-hackers@freebsd.org; Wed, 10 Jan 2007 20:55:40 -0500 Received: from authsmtp09.yourhostingaccount.com ([10.1.18.9] ident=exim) by scan03.yourhostingaccount.com with spamscanlookuphost (Exim) id 1H4pAK-0003VY-KM for freebsd-hackers@freebsd.org; Wed, 10 Jan 2007 20:55:40 -0500 Received: from authsmtp09.yourhostingaccount.com ([10.1.18.9] helo=authsmtp09.yourhostingaccount.com) by scan03.yourhostingaccount.com with esmtp (Exim) id 1H4pAJ-0003VR-Eo for freebsd-hackers@freebsd.org; Wed, 10 Jan 2007 20:55:39 -0500 Received: from [69.92.217.33] (helo=vixen42) by authsmtp09.yourhostingaccount.com with esmtpa (Exim) id 1H4pAI-00036r-4e; Wed, 10 Jan 2007 20:55:39 -0500 Date: Wed, 10 Jan 2007 19:55:39 -0600 From: Vulpes Velox To: Lamont Granquist Message-ID: <20070110195539.68e60812@vixen42> In-Reply-To: References: <20070107190616.73dee7b0@vixen42> <45A1DE76.7000201@FreeBSD.org> <20070108185247.2b6e1f69@vixen42> <45A407D1.9030101@FreeBSD.org> <20070109184346.135e0bf4@vixen42> <45A56107.5050205@FreeBSD.org> <20070110174709.534b1f16@vixen42> X-Mailer: Claws Mail 2.7.0 (GTK+ 2.10.7; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-EN-UserInfo: 0d1ca1697cdb7a831d4877828571b7ab:1570f0de6936c69fef9e164fffc541bc X-EN-AuthUser: vvelox2 Sender: Vulpes Velox Cc: freebsd-hackers@freebsd.org, Doug Barton Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 02:10:48 -0000 On Wed, 10 Jan 2007 17:10:36 -0800 (PST) Lamont Granquist wrote: > > > On Wed, 10 Jan 2007, Vulpes Velox wrote: > > On Wed, 10 Jan 2007 13:56:23 -0800 > > Doug Barton wrote: > >> Lamont Granquist wrote: > >>> Why are you doing this in the FreeBSD rc scripts directly? Why > >>> not install cfengine and work on making cfengine play better > >>> with database-driven config? > >> > >> Indeed. For a "many systems" problem, cfengine is a great tool. I > >> think the OP is more interested in the "dynamically configured > >> laptop" problem, which is also an interesting/difficult one, but > >> I don't think it's a good problem for LDAP to solve. It still > >> feels like "I have LDAP that I want to use as a solution, so > >> what problem can I point it at?" to me. > > > > Stuff like this is what LDAP truely shines for. It keeps > > everything in a nicely organized manner that is easily accessible > > and searchable. > > I agree that database-driven config management is good. I do not > agree that LDAP is the best way to go about doing it since LDAP > works best as a read-mostly directory service and not as an > mixed-read/write database which is what I've seen these kinds of > configuration management databases scale and turn into. LDAP is > great for stuff that barely ever changes. When you add SOX audit > trails and error reporting and other junk into the database LDAP > stops being appropriate. Right. LDAP should not be used for logging at all. That is what SQL is awesome for. :) > I also don't understand the focus on dynamically > generating /etc/rc.conf since that is actually not what I want in > my database. Inside my database I want to configure a machine as > an ftp server or a web server and deal with the high-level roles > that the machine plays. In order to generate an rc.conf file I > want to take the roles as inputs and construct the rc.conf file > specific to the machine. I am starting with rc.conf because it is a logical place to start for what I want. I am not interested in the autoconfiguration stuff in this project. Just reeling in the configuration, I am largely focusing LDAP because it is what would be most handy in my situation, but I am aiming at the idea of making that part is interchangable. I plan to start work the actual parts, once I am happy with the schema. That is going to take a bit of time to get worked out because there are a few things to iron out. There is also a lot of attributes that need to be defined. From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 03:12:52 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 10F4316A412 for ; Thu, 11 Jan 2007 03:12:52 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.freebsd.org (Postfix) with ESMTP id 9C3BC13C455 for ; Thu, 11 Jan 2007 03:12:51 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id l0B3CiAm090120; Wed, 10 Jan 2007 22:12:45 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: "Brad L. Chisholm" Date: Wed, 10 Jan 2007 22:11:38 -0500 User-Agent: KMail/1.9.4 References: <20070110215207.GA85834@bsdone.bsdwins.com> <200701101753.24716.jhb@freebsd.org> <20070111001534.GA319@bsdone.bsdwins.com> In-Reply-To: <20070111001534.GA319@bsdone.bsdwins.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200701102211.39412.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [192.168.0.1]); Wed, 10 Jan 2007 22:12:45 -0500 (EST) X-Virus-Scanned: ClamAV 0.88.3/2434/Wed Jan 10 19:47:38 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-hackers@freebsd.org Subject: Re: Kernel hang on 6.x X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 03:12:52 -0000 On Wednesday 10 January 2007 19:15, Brad L. Chisholm wrote: > On Wed, Jan 10, 2007 at 05:53:24PM -0500, John Baldwin wrote: > > On Wednesday 10 January 2007 16:52, Brad L. Chisholm wrote: > > > > > > I work with Brian, and have been helping him analyze this problem. We have > > > been able to generate kernel dumps, and have also done some additional > > > analysis under ddb. Here is a summary of our analysis so far. Suggestions > > > as to how to proceed from here are most welcome. > > > > How much swap do you have? You might have run out of buckets in the > > swap_zone before you ran out of swap space, in which case the kernel > > deadlocks rather than killing the hog like it does when it runs out of > > swap space. I added a printf to catch this on HEAD recently that will > > be MFC'd soonish. You can try bumping up kern.maxswzone (loader tunable). > > > > It has a 32GB swap partition. We have also run it configured with an > additional 32GB swap file, for a total of 64GB. Changing the amount of > swap did not seem to affect the hang. However, as I mentioned in my > previous post, the hang appears to always occur when ~14GB of swap have > been consumed, regardless of the amount of swap or physmen configured. > This does make it sound like a limit (such as swap_zone buckets) has > been reached. > > I notice the following in the vm.zone output captured just prior to > a hang. Does this value correspond to the swap_zone you were referring > to? This looks like a limit may have been reached. > > SWAPMETA: 288, 116519, 116519, 0, 116543 yep, that's exactly the issue you are hitting. > I don't seem to be able to query kern.maxswzone on our 6.2-BETA2 image: > > # sysctl kern.maxswzone > sysctl: unknown oid 'kern.maxswzone' > > Is it available in 6.x, or is it something newer? It's only a tunable, not available as a sysctl. You can figure out the current size from the vmstat output above, then do some math to figure out a good guess to use based on how much swap it had in use when it locked up. For example, right now you have 116519 objects of size 288, so 33557472 bytes allocated. You said you die when 14 GB out of 64 total is used, so you should probably try taking that value and multiplying it by 64 / 14. That gives a result of 153405586. However, you really want to round this up to a multiple of 288 (because the kernel rounds it down to a multiple of 288), so I'd use a value of at least 153405792. And yes, that means you are setting aside a little over 146 MB of wired, physical RAM just to hold metadata for your swap. :) -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 04:21:03 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 119FE16A407 for ; Thu, 11 Jan 2007 04:21:03 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from ns1.jnielsen.net (ns1.jnielsen.net [69.55.238.237]) by mx1.freebsd.org (Postfix) with ESMTP id E74B113C43E for ; Thu, 11 Jan 2007 04:21:02 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from c-68-59-28-54.hsd1.sc.comcast.net (jn@c-68-59-28-54.hsd1.sc.comcast.net [68.59.28.54]) (authenticated bits=0) by ns1.jnielsen.net (8.12.9p2/8.12.9) with ESMTP id l0B4L2Jv093201 for ; Wed, 10 Jan 2007 20:21:02 -0800 (PST) (envelope-from lists@jnielsen.net) From: John Nielsen To: freebsd-hackers@freebsd.org Date: Wed, 10 Jan 2007 23:21:01 -0500 User-Agent: KMail/1.9.5 X-Face: #X5#Y*q>F:]zT!DegL3z5Xo'^MN[$8k\[4^3rN~wm=s=Uw(sW}R?3b^*f1Wu*.<=?utf-8?q?of=5F4NrS=0A=09P*M/9CpxDo!D6?=)IY1w<9B1jB; tBQf[RU-R<,I)e"$q7N7 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200701102321.01562.lists@jnielsen.net> X-Virus-Scanned: ClamAV version 0.88.4, clamav-milter version 0.88.4 on ns1.jnielsen.net X-Virus-Status: Clean Subject: Best practices for using gjournal with gmirror? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 04:21:03 -0000 I have a few questions for pjd (or anyone else) about using gjournal, particularly when used with gmirror. 1) I'm running 6-STABLE and plan to test with gjournal6_20061030.patch (from the mailing list; updated version of 20061024 that applies cleanly). Is there a better/newer version for -STABLE that I should use instead? 2) When using gjournal and for a gmirror volume, does the journal need to be mirrored as well to maintain redundancy? If so, when storing the journal on the same physical disks as the mirror, is it better to mirror at the slice level (journal and fs on different partitions in the same mirror) or at the partition level (journal and fs each have their own mirror) or does it matter? 3) I remember reading where pjd said that gjournal plus gmirror or graid3 would eliminate the need to re-sync the array after a crash. While clearly a design goal, is that actually the case with the version of the patch mentioned above? If so, are any config changes needed or will it just happen automagically? 4) In the same vein as 3)--does a gjournal volume need to be fsck'ed after a crash? If not, will it just work (e.g. fsck -p sees that the filesystem is clean) or does it need to be disabled somehow? 5) Finally, how dangerous is this code? I realize it's experimental and only plan to use it with data that has recent backups, but how much should I worry about it blowing up my system or corrupting my files? Thanks! JN From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 06:21:10 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 75AD916A560 for ; Thu, 11 Jan 2007 06:21:10 +0000 (UTC) (envelope-from fcash@ocis.net) Received: from smtp.sd73.bc.ca (smtp.sd73.bc.ca [142.24.13.140]) by mx1.freebsd.org (Postfix) with ESMTP id 4C62A13C478 for ; Thu, 11 Jan 2007 06:21:10 +0000 (UTC) (envelope-from fcash@ocis.net) Received: from localhost (localhost [127.0.0.1]) by localhost.sd73.bc.ca (Postfix) with ESMTP id C16F51A000B3B for ; Wed, 10 Jan 2007 22:21:09 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at smtp.sd73.bc.ca Received: from smtp.sd73.bc.ca ([127.0.0.1]) by localhost (smtp.sd73.bc.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id UpnoRiXGm7MT for ; Wed, 10 Jan 2007 22:21:03 -0800 (PST) Received: from webmail.sd73.bc.ca (webmail.sd73.bc.ca [10.10.10.17]) by smtp.sd73.bc.ca (Postfix) with ESMTP id 5EADB1A0007C8 for ; Wed, 10 Jan 2007 22:21:03 -0800 (PST) Received: from 24.71.119.183 (SquirrelMail authenticated user fcash) by webmail.sd73.bc.ca with HTTP; Wed, 10 Jan 2007 22:21:03 -0800 (PST) Message-ID: <60737.24.71.119.183.1168496463.squirrel@webmail.sd73.bc.ca> Date: Wed, 10 Jan 2007 22:21:03 -0800 (PST) From: "Freddie Cash" To: hackers@freebsd.org User-Agent: SquirrelMail/1.5.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 06:21:10 -0000 On Wed, January 10, 2007 2:43 pm, Lamont Granquist wrote: > On Wed, 10 Jan 2007, Doug Barton wrote: >> Lamont Granquist wrote: >>> On Wed, 10 Jan 2007, Doug Barton wrote: >>>>> And if you're looking specifically at the /etc/rc.conf config >>>>> file, what would be more useful would be an /etc/rc.conf.d/ >>>>> directory. >>>> >>>> Good news for you, we already support that. :) I agree that it >>>> makes a great tool for the "many systems" problem, and could >>>> reasonably be used for part of the "dynamic laptop" problem too. >>>> >>> 7-current feature? I'm not seeing it in rc.conf(5) on my >>> RELENG_6-ish >>> system... >> >> It's not documented, but the code is there in /etc/rc.subr: >> >> grep 'rc.conf\.d' /etc/rc.subr if [ -f /etc/rc.conf.d/"$_name" ]; >> then debug "Sourcing /etc/rc.conf.d/${_name}" . >> /etc/rc.conf.d/"$_name" >> ... >> > If i understand that correctly its not *exactly* what i was looking > for, but its better than a monolithic /etc/rc.conf > > It looks like you must put /etc/rc.d/inetd config into either > /etc/rc.conf or /etc/rc.config.d/inetd. > > That means that if you've got two different orthogonal applications > runing on the same server which both need to run something orthogonal > out of inetd then they still wind up needing to do edits to the same > config file to get inetd configured correctly. I'd rather see > /etc/rc.config.d/app01 and /etc/rc.config.d/app02 both able to tweak > inetd settings. Of > course there is the possibility that app01 and app02 could drop > mutually conflicting inetd setttings, but you've got that problem > anyway in the existing scheme... To each their own, of course. Personally, I am so sick of the way system like Debian use dozens of config files for each app, all in their own conf.d/ sub-directories. Some apps, like PureFTPd actually use separate config files for each and every option it supports. Trying to configure these apps is a royal pain of opening and editing a dozen files. Maybe this makes it easier for automated configuration tools and GUIs, but it makes it a *ROYAL* pain in the arse for mere mortals using text editors to manage. What is wrong with 1 editable text file per app? With a single sub-directory per application for config files? Where you can quickly, and easily view all the options at a glance? The nicest thing about FreeBSD is /etc/rc.conf, a single configuration file that is easily editable in any text editor. Makes managing systems remotely so simple. ---- Freddie Cash fcash@ocis.net From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 07:56:59 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9531416A4D4 for ; Thu, 11 Jan 2007 07:56:59 +0000 (UTC) (envelope-from SRS0+IRu3+24+datalinktech.com.au=davidn@internode.on.net) Received: from mail.internode.on.net (bld-mail02.adl2.internode.on.net [203.16.214.66]) by mx1.freebsd.org (Postfix) with ESMTP id EE5A913C442 for ; Thu, 11 Jan 2007 07:56:58 +0000 (UTC) (envelope-from SRS0+IRu3+24+datalinktech.com.au=davidn@internode.on.net) Received: from [192.168.227.24] (unverified [59.167.64.5]) by mail.internode.on.net (SurgeMail 3.8f2) with ESMTP id 262091601-1869586 for multiple; Thu, 11 Jan 2007 18:11:33 +1030 (CDT) Message-ID: <45A5EA3B.9020000@datalinktech.com.au> Date: Thu, 11 Jan 2007 18:41:47 +1100 From: David Nugent User-Agent: Thunderbird 1.5.0.9 (X11/20070104) MIME-Version: 1.0 To: Freddie Cash References: <60737.24.71.119.183.1168496463.squirrel@webmail.sd73.bc.ca> In-Reply-To: <60737.24.71.119.183.1168496463.squirrel@webmail.sd73.bc.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: hackers@freebsd.org Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 07:56:59 -0000 Freddie Cash wrote: > To each their own, of course. Personally, I am so sick of the way > system like Debian use dozens of config files for each app, all in > their own conf.d/ sub-directories. Some apps, like PureFTPd actually > use separate config files for each and every option it supports. > Trying to configure these apps is a royal pain of opening and editing > a dozen files. Maybe this makes it easier for automated configuration > tools and GUIs, but it makes it a *ROYAL* pain in the arse for mere > mortals using text editors to manage. > But management of config data is a user interface, surely, and not directly related to the underlying storage mechanism. What is the logical difference between using a directory structure vs. an LDAP server containing essentially the same information (plus all of the overhead)? "dozens of config files" just equates to dozens of ldap entries (or dozens of entries in a single config file). Given the same or equivalent "friendly" UI, do you really care how the back end is managed? By moving the data to a directory you are making it less accessible to standard tools, so you're just removing the option to directly edit those config files and only gain on being able to use ldap editing tools instead of text editing tools. You could write a similarly "friendly" app that managed your conrfiguration files, and you won't need any LDAP expertise to use it. Network access and management of configuration data are the real advantages here, not the UI. Integration of LDAP would provide close to (and arguably less than) zero benefit to a stand alone system, really, and would effectively equate to a Windows registry with all of the pros and cons that come with that. Regards -d From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 09:44:52 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3460016A47C; Thu, 11 Jan 2007 09:44:52 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-3-125.belrs4.nsw.optusnet.com.au [220.239.3.125]) by mx1.freebsd.org (Postfix) with ESMTP id B744D13C459; Thu, 11 Jan 2007 09:44:51 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.8/8.13.8) with ESMTP id l0B9LsQh002171; Thu, 11 Jan 2007 20:21:54 +1100 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.8/8.13.8/Submit) id l0B9LrUf002170; Thu, 11 Jan 2007 20:21:53 +1100 (EST) (envelope-from peter) Date: Thu, 11 Jan 2007 20:21:53 +1100 From: Peter Jeremy To: John Baldwin Message-ID: <20070111092153.GG833@turion.vk2pj.dyndns.org> References: <20070110215207.GA85834@bsdone.bsdwins.com> <200701101753.24716.jhb@freebsd.org> <20070111001534.GA319@bsdone.bsdwins.com> <200701102211.39412.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="yVhtmJPUSI46BTXb" Content-Disposition: inline In-Reply-To: <200701102211.39412.jhb@freebsd.org> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.13 (2006-08-11) Cc: "Brad L. Chisholm" , freebsd-hackers@freebsd.org Subject: Re: Kernel hang on 6.x X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 09:44:52 -0000 --yVhtmJPUSI46BTXb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, 2007-Jan-10 22:11:38 -0500, John Baldwin wrote: >64 / 14. That gives a result of 153405586. However, you really want to >round this up to a multiple of 288 (because the kernel rounds it down to >a multiple of 288), so I'd use a value of at least 153405792. Looking at the code, it seems that each SWAPMETA object manages 16 pages. > And yes, >that means you are setting aside a little over 146 MB of wired, physical >RAM just to hold metadata for your swap. :) Given a system with 16GB RAM, this probably isn't a serious issue. --=20 Peter Jeremy --yVhtmJPUSI46BTXb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFpgGx/opHv/APuIcRAgMmAKC50wAPAHlnwpcF+OQCLqe+hk72aACgty4J PZ7yscipmY+K+k9xbSl75UM= =tCnE -----END PGP SIGNATURE----- --yVhtmJPUSI46BTXb-- From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 10:11:28 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 116A216A407 for ; Thu, 11 Jan 2007 10:11:28 +0000 (UTC) (envelope-from SRS0=LVA8ua=GU=vvelox.net=v.velox@yourhostingaccount.com) Received: from mailout12.yourhostingaccount.com (mailout12.yourhostingaccount.com [65.254.253.96]) by mx1.freebsd.org (Postfix) with ESMTP id C689E13C459 for ; Thu, 11 Jan 2007 10:11:27 +0000 (UTC) (envelope-from SRS0=LVA8ua=GU=vvelox.net=v.velox@yourhostingaccount.com) Received: from scan10.yourhostingaccount.com ([10.1.1.240] helo=scan10.yourhostingaccount.com) by mailout12.yourhostingaccount.com with esmtp (Exim) id 1H4wex-0003zK-Fd for hackers@freebsd.org; Thu, 11 Jan 2007 04:55:47 -0500 Received: from authsmtp10.yourhostingaccount.com ([10.1.18.10] ident=exim) by scan10.yourhostingaccount.com with spamscanlookuphost (Exim) id 1H4wex-0006ep-Cs for hackers@freebsd.org; Thu, 11 Jan 2007 04:55:47 -0500 Received: from authsmtp10.yourhostingaccount.com ([10.1.18.10] helo=authsmtp10.yourhostingaccount.com) by scan10.yourhostingaccount.com with esmtp (Exim) id 1H4wew-0006ek-RG for hackers@freebsd.org; Thu, 11 Jan 2007 04:55:46 -0500 Received: from [69.92.217.33] (helo=vixen42) by authsmtp10.yourhostingaccount.com with esmtpa (Exim) id 1H4wew-0002mq-4R; Thu, 11 Jan 2007 04:55:46 -0500 Date: Thu, 11 Jan 2007 03:55:49 -0600 From: Vulpes Velox To: David Nugent Message-ID: <20070111035549.7c11a450@vixen42> In-Reply-To: <45A5EA3B.9020000@datalinktech.com.au> References: <60737.24.71.119.183.1168496463.squirrel@webmail.sd73.bc.ca> <45A5EA3B.9020000@datalinktech.com.au> X-Mailer: Claws Mail 2.7.0 (GTK+ 2.10.7; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-EN-UserInfo: 0d1ca1697cdb7a831d4877828571b7ab:1570f0de6936c69fef9e164fffc541bc X-EN-AuthUser: vvelox2 Sender: Vulpes Velox Cc: hackers@freebsd.org Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 10:11:28 -0000 On Thu, 11 Jan 2007 18:41:47 +1100 David Nugent wrote: > Freddie Cash wrote: > > To each their own, of course. Personally, I am so sick of the way > > system like Debian use dozens of config files for each app, all in > > their own conf.d/ sub-directories. Some apps, like PureFTPd > > actually use separate config files for each and every option it > > supports. Trying to configure these apps is a royal pain of > > opening and editing a dozen files. Maybe this makes it easier > > for automated configuration tools and GUIs, but it makes it a > > *ROYAL* pain in the arse for mere mortals using text editors to > > manage. > But management of config data is a user interface, surely, and not > directly related to the underlying storage mechanism. > > What is the logical difference between using a directory structure > vs. an LDAP server containing essentially the same information > (plus all of the overhead)? "dozens of config files" just equates > to dozens of ldap entries (or dozens of entries in a single config > file). Given the same or equivalent "friendly" UI, do you really > care how the back end is managed? By moving the data to a directory > you are making it less accessible to standard tools, so you're just > removing the option to directly edit those config files and only > gain on being able to use ldap editing tools instead of text > editing tools. You could write a similarly "friendly" app that > managed your conrfiguration files, and you won't need any LDAP > expertise to use it. > > Network access and management of configuration data are the real > advantages here, not the UI. Integration of LDAP would provide > close to (and arguably less than) zero benefit to a stand alone > system, really, and would effectively equate to a Windows registry > with all of the pros and cons that come with that. I vote both are completely stupid. LDAP is nice organizing across many systems, but if you are just dealing with one computer it is complete over kill for any thing. Splitting rc.conf up into multiple files is just plain messy and stupid as well. I can see there being times when it is split into two, but I don't see any reason for more than that. There are plenty of nice ways to access and modify LDAP data. I would say it is easily as friendly as editing text files to be pulled across. I fail to see how LDAP is not a standard tool. It is a tool that is really under utilized. What this gains is being able to store a lot of configuration stuff in the same place. It makes permission handling a lot easier as well. If you store it in a file any one with write access can edit it, but with LDAP it can assign write access to specific attributes. With files you would have to split it up across multiple files. From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 10:51:53 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 864B216A403 for ; Thu, 11 Jan 2007 10:51:53 +0000 (UTC) (envelope-from pietro.cerutti@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.171]) by mx1.freebsd.org (Postfix) with ESMTP id 17A8213C45E for ; Thu, 11 Jan 2007 10:51:52 +0000 (UTC) (envelope-from pietro.cerutti@gmail.com) Received: by ug-out-1314.google.com with SMTP id o2so378219uge for ; Thu, 11 Jan 2007 02:51:51 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=qytGmkTaC2E2Lwj5hc8EbwmnFHk7Zwy835lsaAjr+pgt3AjZruYjg0cCO1bBwsTgUs4eRq5b2zyaH8XtKzdQ/ntyY468SKjyorAyuIZBOCPrwAAlQcfzIw4nIySKqkP3Mg0JyzX1iJkmGnnUgNt+s0iIP79zBgNjuZsHmY1xlHc= Received: by 10.67.91.6 with SMTP id t6mr1389847ugl.1168512711937; Thu, 11 Jan 2007 02:51:51 -0800 (PST) Received: by 10.67.23.8 with HTTP; Thu, 11 Jan 2007 02:51:51 -0800 (PST) Message-ID: Date: Thu, 11 Jan 2007 11:51:51 +0100 From: "Pietro Cerutti" To: "FreeBSD Questions" , freebsd-hackers@freebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: Subject: [SOLVED] re(4) incorrect checksum X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 10:51:53 -0000 Hi lists, ifconfig re0 -txcsum -rxcsum solved the problem.... Anyway, is this a bug in the driver or in the interface itself? Thanx, regards ---------- Forwarded message ---------- From: Pietro Cerutti Date: Jan 11, 2007 11:29 AM Subject: re(4) incorrect checksum To: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org Hi lists, FreeBSD gahrtop.localhost 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #1: Tue Jan 9 19:34:13 CET 2007 root@gahrtop:/usr/obj/usr/src/sys/GAHRTOP i386 CPU: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz (2000.15-MHz 686-class CPU) Cores per package: 2 re0: port 0xc800-0xc8ff mem 0xff2ff000-0xff2fffff irq 17 at device 0.0 on pci2 ($FreeBSD: src/sys/dev/re/if_re.c,v 1.46.2.20 2006/09/21 11:08:28 yongari Exp $) I get checksum errors on every packet I send, example: Checksum: 0x0bc5 [incorrect, should be 0x78fe (maybe caused by checksum offloading?)] I think this could be the cause of some web pages (e.g. Gmail in standard view [html view works well]) not to be displayed. I tracked down the problem to the re(4) driver just because wlan works good... Any ideas? Thanx, -- Pietro Cerutti ICQ: 117293691 PGP: 0x9571F78E - ASCII Ribbon Campaign - against HTML e-mail and proprietary attachments www.asciiribbon.org -- Pietro Cerutti ICQ: 117293691 PGP: 0x9571F78E - ASCII Ribbon Campaign - against HTML e-mail and proprietary attachments www.asciiribbon.org From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 10:57:03 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 69FF716A56A for ; Thu, 11 Jan 2007 10:57:03 +0000 (UTC) (envelope-from pietro.cerutti@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.168]) by mx1.freebsd.org (Postfix) with ESMTP id 837D513C4A8 for ; Thu, 11 Jan 2007 10:57:01 +0000 (UTC) (envelope-from pietro.cerutti@gmail.com) Received: by ug-out-1314.google.com with SMTP id o2so379397uge for ; Thu, 11 Jan 2007 02:57:00 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=K49NFJJj4QVhYH3Z+tCwDaiDgb7jgGwIanmV1hs911hsL6iJ8KCw2gNC8YlxtPNsiMuPWqATvXNSFy8qlpi1WltrOF6mfdFwAtcw2CcW56R425kvDq5Iktdog8gJeAtOyf/fDGP4+apdHei/HQ3bwcHt2Wt+iUF5NCwVvNwneok= Received: by 10.67.22.14 with SMTP id z14mr1515667ugi.1168511386754; Thu, 11 Jan 2007 02:29:46 -0800 (PST) Received: by 10.67.23.8 with HTTP; Thu, 11 Jan 2007 02:29:46 -0800 (PST) Message-ID: Date: Thu, 11 Jan 2007 11:29:46 +0100 From: "Pietro Cerutti" To: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: re(4) incorrect checksum X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 10:57:03 -0000 Hi lists, FreeBSD gahrtop.localhost 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #1: Tue Jan 9 19:34:13 CET 2007 root@gahrtop:/usr/obj/usr/src/sys/GAHRTOP i386 CPU: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz (2000.15-MHz 686-class CPU) Cores per package: 2 re0: port 0xc800-0xc8ff mem 0xff2ff000-0xff2fffff irq 17 at device 0.0 on pci2 ($FreeBSD: src/sys/dev/re/if_re.c,v 1.46.2.20 2006/09/21 11:08:28 yongari Exp $) I get checksum errors on every packet I send, example: Checksum: 0x0bc5 [incorrect, should be 0x78fe (maybe caused by checksum offloading?)] I think this could be the cause of some web pages (e.g. Gmail in standard view [html view works well]) not to be displayed. I tracked down the problem to the re(4) driver just because wlan works good... Any ideas? Thanx, -- Pietro Cerutti ICQ: 117293691 PGP: 0x9571F78E - ASCII Ribbon Campaign - against HTML e-mail and proprietary attachments www.asciiribbon.org From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 11:14:42 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A350D16A407 for ; Thu, 11 Jan 2007 11:14:42 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.175]) by mx1.freebsd.org (Postfix) with ESMTP id 393FE13C455 for ; Thu, 11 Jan 2007 11:14:42 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: by ug-out-1314.google.com with SMTP id 74so388602ugb for ; Thu, 11 Jan 2007 03:14:41 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding; b=pVOeTVlITWyRqWR2P5LWH8aM+gw6raQqwhB2qEZ//1x57MN3l61gyo32FcnxHsu23OIZpMcrJ01nmGcOIDQdFvxZQSQTS8Fy/ih8enfaFuz/p+isFBTH+nUU/YoqbdHIjH1aUbDBakdeJM5WvwHccMWV9wFwxo4mOKCiiky4xOk= Received: by 10.66.219.11 with SMTP id r11mr1551565ugg.1168514081083; Thu, 11 Jan 2007 03:14:41 -0800 (PST) Received: from ?192.168.123.201? ( [195.241.221.201]) by mx.google.com with ESMTP id k28sm643706ugd.2007.01.11.03.14.40; Thu, 11 Jan 2007 03:14:40 -0800 (PST) Message-ID: <45A61C1A.3090600@gmail.com> Date: Thu, 11 Jan 2007 12:14:34 +0100 From: Rene Ladan User-Agent: Thunderbird 1.5.0.9 (X11/20061224) MIME-Version: 1.0 To: Pietro Cerutti References: In-Reply-To: X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: re(4) incorrect checksum X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 11:14:42 -0000 Pietro Cerutti schreef: > Hi lists, > > FreeBSD gahrtop.localhost 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #1: > Tue Jan 9 19:34:13 CET 2007 > root@gahrtop:/usr/obj/usr/src/sys/GAHRTOP i386 > > CPU: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz (2000.15-MHz > 686-class CPU) > Cores per package: 2 > > re0: port 0xc800-0xc8ff > mem 0xff2ff000-0xff2fffff irq 17 at device 0.0 on pci2 > > ($FreeBSD: src/sys/dev/re/if_re.c,v 1.46.2.20 2006/09/21 11:08:28 > yongari Exp $) > > I get checksum errors on every packet I send, example: > > Checksum: 0x0bc5 [incorrect, should be 0x78fe (maybe caused by > checksum offloading?)] > > I think this could be the cause of some web pages (e.g. Gmail in > standard view [html view works well]) not to be displayed. > > I tracked down the problem to the re(4) driver just because wlan works > good... > > Any ideas? > I'm also seeing these www problems with my re(4) card (chipid 0x816810ec), see http://lists.freebsd.org/pipermail/freebsd-current/2006-December/068333.html Wireless is ok. > Thanx, > Regards, Rene -- GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) "It won't fit on the line." -- me, 2001 From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 12:00:20 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F3DD416A407 for ; Thu, 11 Jan 2007 12:00:19 +0000 (UTC) (envelope-from pietro.cerutti@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.169]) by mx1.freebsd.org (Postfix) with ESMTP id 5198B13C45E for ; Thu, 11 Jan 2007 12:00:19 +0000 (UTC) (envelope-from pietro.cerutti@gmail.com) Received: by ug-out-1314.google.com with SMTP id o2so394044uge for ; Thu, 11 Jan 2007 04:00:18 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=PORLn2gpO80d6pCkWvSlQML1Mwb4eyiL1p/dS7rTerg8sqUoqGYLIHna+7TUojof99ViOc2LvHrppY9PqlXDmoCSPIwvQHD19Sj6elcvQ1hqpjVtlqnmfjSYp/5nBLURbMT8jBoZdNctAGhM400QztdaZ+YyXOyKErKXzdoH/QQ= Received: by 10.67.106.3 with SMTP id i3mr1595562ugm.1168516818192; Thu, 11 Jan 2007 04:00:18 -0800 (PST) Received: by 10.67.23.8 with HTTP; Thu, 11 Jan 2007 04:00:18 -0800 (PST) Message-ID: Date: Thu, 11 Jan 2007 13:00:18 +0100 From: "Pietro Cerutti" To: "FreeBSD Questions" , freebsd-hackers@freebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070111114402.GX80390@cicely12.cicely.de> Cc: Subject: Fwd: [SOLVED] re(4) incorrect checksum X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 12:00:20 -0000 On 1/11/07, Bernd Walter wrote: > On Thu, Jan 11, 2007 at 11:51:51AM +0100, Pietro Cerutti wrote: > > Hi lists, > > ifconfig re0 -txcsum -rxcsum solved the problem.... > > > > Anyway, is this a bug in the driver or in the interface itself? > > That is how checksum offloading works. > tcpdump can't see a correct checksum, because it is not calculated > by the kernel and left for the hardware. Yes, I got it. > However checksum offloading is broken for re(4) based cards, therefor > it is disabled by default. I don't think so.... at least, I did nothing to enable it, but it were indeed enabled (RXCSUM,TXCSU showed up in the options field shown by ifconfig) > > -- > B.Walter http://www.bwct.de http://www.fizon.de > bernd@bwct.de info@bwct.de support@fizon.de > -- Pietro Cerutti ICQ: 117293691 PGP: 0x9571F78E - ASCII Ribbon Campaign - against HTML e-mail and proprietary attachments www.asciiribbon.org From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 12:11:57 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BF7A316A47B; Thu, 11 Jan 2007 12:11:57 +0000 (UTC) (envelope-from ticso@cicely12.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id 4B9B113C455; Thu, 11 Jan 2007 12:11:56 +0000 (UTC) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de ([10.1.1.7]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id l0BBiGus082266; Thu, 11 Jan 2007 12:44:16 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (cicely12.cicely.de [10.1.1.14]) by cicely5.cicely.de (8.13.4/8.13.4) with ESMTP id l0BBi37i032320 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 11 Jan 2007 12:44:04 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.13.4/8.13.3) with ESMTP id l0BBi3di091139; Thu, 11 Jan 2007 12:44:03 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.13.4/8.13.3/Submit) id l0BBi3ao091138; Thu, 11 Jan 2007 12:44:03 +0100 (CET) (envelope-from ticso) Date: Thu, 11 Jan 2007 12:44:03 +0100 From: Bernd Walter To: Pietro Cerutti Message-ID: <20070111114402.GX80390@cicely12.cicely.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD cicely12.cicely.de 5.4-STABLE alpha User-Agent: Mutt/1.5.9i X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED=-1.8, BAYES_00=-2.599 autolearn=ham version=3.1.7 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on cicely12.cicely.de Cc: freebsd-hackers@freebsd.org, FreeBSD Questions Subject: Re: [SOLVED] re(4) incorrect checksum X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 12:11:57 -0000 On Thu, Jan 11, 2007 at 11:51:51AM +0100, Pietro Cerutti wrote: > Hi lists, > ifconfig re0 -txcsum -rxcsum solved the problem.... > > Anyway, is this a bug in the driver or in the interface itself? That is how checksum offloading works. tcpdump can't see a correct checksum, because it is not calculated by the kernel and left for the hardware. However checksum offloading is broken for re(4) based cards, therefor it is disabled by default. -- B.Walter http://www.bwct.de http://www.fizon.de bernd@bwct.de info@bwct.de support@fizon.de From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 06:08:33 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8C4B216A403 for ; Thu, 11 Jan 2007 06:08:33 +0000 (UTC) (envelope-from fcash-ml@sd73.bc.ca) Received: from smtp.sd73.bc.ca (smtp.sd73.bc.ca [142.24.13.140]) by mx1.freebsd.org (Postfix) with ESMTP id 5B40C13C442 for ; Thu, 11 Jan 2007 06:08:31 +0000 (UTC) (envelope-from fcash-ml@sd73.bc.ca) Received: from localhost (localhost [127.0.0.1]) by localhost.sd73.bc.ca (Postfix) with ESMTP id 1E00A1A0007AC for ; Wed, 10 Jan 2007 21:37:11 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at smtp.sd73.bc.ca Received: from smtp.sd73.bc.ca ([127.0.0.1]) by localhost (smtp.sd73.bc.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 8rfZpXwV7-Rc for ; Wed, 10 Jan 2007 21:37:04 -0800 (PST) Received: from webmail.sd73.bc.ca (webmail.sd73.bc.ca [10.10.10.17]) by smtp.sd73.bc.ca (Postfix) with ESMTP id 9B8651A000B2A for ; Wed, 10 Jan 2007 21:37:04 -0800 (PST) Received: from 24.71.119.183 (SquirrelMail authenticated user fcash) by webmail.sd73.bc.ca with HTTP; Wed, 10 Jan 2007 21:37:04 -0800 (PST) Message-ID: <63903.24.71.119.183.1168493824.squirrel@webmail.sd73.bc.ca> In-Reply-To: References: <20070107190616.73dee7b0@vixen42> <45A1DE76.7000201@FreeBSD.org> <20070108185247.2b6e1f69@vixen42> <45A407D1.9030101@FreeBSD.org> <20070109184346.135e0bf4@vixen42> <45A56107.5050205@FreeBSD.org> <45A566D7.4040907@FreeBSD.org> Date: Wed, 10 Jan 2007 21:37:04 -0800 (PST) From: "Freddie Cash" To: freebsd-hackers@freebsd.org User-Agent: SquirrelMail/1.5.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailman-Approved-At: Thu, 11 Jan 2007 12:41:32 +0000 Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 06:08:33 -0000 On Wed, January 10, 2007 2:43 pm, Lamont Granquist wrote: > On Wed, 10 Jan 2007, Doug Barton wrote: >> Lamont Granquist wrote: >>> On Wed, 10 Jan 2007, Doug Barton wrote: >>>>> And if you're looking specifically at the /etc/rc.conf config >>>>> file, what would be more useful would be an /etc/rc.conf.d/ >>>>> directory. >>>> >>>> Good news for you, we already support that. :) I agree that it >>>> makes a great tool for the "many systems" problem, and could >>>> reasonably be used for part of the "dynamic laptop" problem too. >>>> >>> 7-current feature? I'm not seeing it in rc.conf(5) on my >>> RELENG_6-ish >>> system... >> >> It's not documented, but the code is there in /etc/rc.subr: >> >> grep 'rc.conf\.d' /etc/rc.subr if [ -f /etc/rc.conf.d/"$_name" ]; >> then debug "Sourcing /etc/rc.conf.d/${_name}" . >> /etc/rc.conf.d/"$_name" >> ... >> > If i understand that correctly its not *exactly* what i was looking > for, but its better than a monolithic /etc/rc.conf > > It looks like you must put /etc/rc.d/inetd config into either > /etc/rc.conf or /etc/rc.config.d/inetd. > > That means that if you've got two different orthogonal applications > runing on the same server which both need to run something orthogonal > out of inetd then they still wind up needing to do edits to the same > config file to get inetd configured correctly. I'd rather see > /etc/rc.config.d/app01 and /etc/rc.config.d/app02 both able to tweak > inetd settings. Of > course there is the possibility that app01 and app02 could drop > mutually conflicting inetd setttings, but you've got that problem > anyway in the existing scheme... To each their own, of course. Personally, I am so sick of the way system like Debian use dozens of config files for each app, all in their own conf.d/ sub-directories. Some apps, like PureFTPd actually use separate config files for each and every option it supports. Trying to configure these apps is a royal pain of opening and editing a dozen files. Maybe this makes it easier for automated configuration tools and GUIs, but it makes it a *ROYAL* pain in the arse for mere mortals using text editors to manage. What is wrong with 1 editable text file per app? With a single sub-directory per application for config files? Where you can quickly, and easily view all the options at a glance? The nicest thing about FreeBSD is /etc/rc.conf, a single configuration file that is easily editable in any text editor. Makes managing systems remotely so simple. ---- Freddie Cash, LPIC-2 CCNT CCLP Helpdesk / Network Support Tech. School District 73 (250) 377-HELP [377-4357] fcash@sd73.bc.ca helpdesk@sd73.bc.ca From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 07:08:42 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 837AC16A407; Thu, 11 Jan 2007 07:08:42 +0000 (UTC) (envelope-from blc@bsdwins.com) Received: from bsdone.bsdwins.com (www.bsdwins.com [192.58.184.33]) by mx1.freebsd.org (Postfix) with ESMTP id 4ABBC13C44B; Thu, 11 Jan 2007 07:08:42 +0000 (UTC) (envelope-from blc@bsdwins.com) Received: from bsdone.bsdwins.com (localhost [127.0.0.1]) by bsdone.bsdwins.com (8.13.6/8.13.6) with ESMTP id l0B74RhG055382; Thu, 11 Jan 2007 07:04:27 GMT (envelope-from blc@www.bsdwins.com) Received: (from blc@localhost) by bsdone.bsdwins.com (8.13.6/8.13.6/Submit) id l0B74QdT055379; Thu, 11 Jan 2007 02:04:26 -0500 (EST) (envelope-from blc) Date: Thu, 11 Jan 2007 02:04:26 -0500 From: "Brad L. Chisholm" To: John Baldwin Message-ID: <20070111070426.GB52964@bsdone.bsdwins.com> References: <20070110215207.GA85834@bsdone.bsdwins.com> <200701101753.24716.jhb@freebsd.org> <20070111001534.GA319@bsdone.bsdwins.com> <200701102211.39412.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200701102211.39412.jhb@freebsd.org> User-Agent: Mutt/1.4.2.1i X-Mailman-Approved-At: Thu, 11 Jan 2007 12:41:45 +0000 Cc: "Brad L. Chisholm" , freebsd-hackers@freebsd.org Subject: Re: Kernel hang on 6.x X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 07:08:42 -0000 On Wed, Jan 10, 2007 at 10:11:38PM -0500, John Baldwin wrote: > On Wednesday 10 January 2007 19:15, Brad L. Chisholm wrote: > > > > I notice the following in the vm.zone output captured just prior to > > a hang. Does this value correspond to the swap_zone you were referring > > to? This looks like a limit may have been reached. > > > > SWAPMETA: 288, 116519, 116519, 0, 116543 > > yep, that's exactly the issue you are hitting. > > > I don't seem to be able to query kern.maxswzone on our 6.2-BETA2 image: > > > > # sysctl kern.maxswzone > > sysctl: unknown oid 'kern.maxswzone' > > > > Is it available in 6.x, or is it something newer? > > It's only a tunable, not available as a sysctl. You can figure out the > current size from the vmstat output above, then do some math to figure > out a good guess to use based on how much swap it had in use when it > locked up. For example, right now you have 116519 objects of size 288, so > 33557472 bytes allocated. You said you die when 14 GB out of 64 total is > used, so you should probably try taking that value and multiplying it by > 64 / 14. That gives a result of 153405586. However, you really want to > round this up to a multiple of 288 (because the kernel rounds it down to > a multiple of 288), so I'd use a value of at least 153405792. And yes, > that means you are setting aside a little over 146 MB of wired, physical > RAM just to hold metadata for your swap. :) > Excellent! Increasing kern.maxswzone has indeed fixed the problem. Can this value be auto-tuned better based upon the size of swap, or is it the particular swapping pattern caused by our environment that caused the default size to be insufficient? In any case, the kernel printf you added recently should help make this much easier to diagnose in the future. Thanks for your help! --- Brad Chisholm blc@bsdwins.com From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 12:44:34 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 463B416A415 for ; Thu, 11 Jan 2007 12:44:34 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.232]) by mx1.freebsd.org (Postfix) with ESMTP id 0492113C458 for ; Thu, 11 Jan 2007 12:44:33 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by wx-out-0506.google.com with SMTP id s18so446644wxc for ; Thu, 11 Jan 2007 04:44:33 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=rJ5Y2EgupxdGRBiiW3KdTv8ZYWC8FAt2RAcoV7FEGxdNsWrlml6Eczv7cmjrZtSpuDDiWuURKyrzhD8CUB5PrzPj+6SMHd8zglkt9h/XAJYiXQb87FjATrWLk+hSNG3iCepdC4Aln7QGrCjKJdaijladvEyM2ul64WiAgME9CsQ= Received: by 10.70.36.9 with SMTP id j9mr2815034wxj.1168517958300; Thu, 11 Jan 2007 04:19:18 -0800 (PST) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTP id 13sm1427547wrl.2007.01.11.04.19.16; Thu, 11 Jan 2007 04:19:17 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id l0BCKnWj040487 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 11 Jan 2007 21:20:49 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l0BCKn1N040486; Thu, 11 Jan 2007 21:20:49 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Thu, 11 Jan 2007 21:20:49 +0900 From: Pyun YongHyeon To: Rene Ladan Message-ID: <20070111122049.GE33964@cdnetworks.co.kr> References: <45A61C1A.3090600@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45A61C1A.3090600@gmail.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-hackers@freebsd.org, Pietro Cerutti Subject: Re: re(4) incorrect checksum X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 12:44:34 -0000 On Thu, Jan 11, 2007 at 12:14:34PM +0100, Rene Ladan wrote: > Pietro Cerutti schreef: > > Hi lists, > > > > FreeBSD gahrtop.localhost 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #1: > > Tue Jan 9 19:34:13 CET 2007 > > root@gahrtop:/usr/obj/usr/src/sys/GAHRTOP i386 > > > > CPU: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz (2000.15-MHz > > 686-class CPU) > > Cores per package: 2 > > > > re0: port 0xc800-0xc8ff > > mem 0xff2ff000-0xff2fffff irq 17 at device 0.0 on pci2 > > > > ($FreeBSD: src/sys/dev/re/if_re.c,v 1.46.2.20 2006/09/21 11:08:28 > > yongari Exp $) > > > > I get checksum errors on every packet I send, example: > > > > Checksum: 0x0bc5 [incorrect, should be 0x78fe (maybe caused by > > checksum offloading?)] > > > > I think this could be the cause of some web pages (e.g. Gmail in > > standard view [html view works well]) not to be displayed. > > > > I tracked down the problem to the re(4) driver just because wlan works > > good... > > > > Any ideas? > > > I'm also seeing these www problems with my re(4) card (chipid > 0x816810ec), see > http://lists.freebsd.org/pipermail/freebsd-current/2006-December/068333.html > Does your re(4) also work when you disable checksum offload? > Wireless is ok. > > > Thanx, > > > Regards, > Rene > -- > GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 > (subkeys.pgp.net) > > "It won't fit on the line." > -- me, 2001 -- Regards, Pyun YongHyeon From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 12:46:43 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6FCA816A4A0 for ; Thu, 11 Jan 2007 12:46:43 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.227]) by mx1.freebsd.org (Postfix) with ESMTP id 2AEDF13C44C for ; Thu, 11 Jan 2007 12:46:43 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by wx-out-0506.google.com with SMTP id s18so447140wxc for ; Thu, 11 Jan 2007 04:46:43 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=eOoBJLd5FMPLSFKN1+t7zNx/phmqgkAljTcjW/kHAXTO44+KbyobHGMO0zBMxQgAgqzD5QI1XpqFLISYafl9FOUPqDqlMeR1IO9fvNG3DBhNIGJs04/dWTtMAa2naNcNJWqSZT7i8WnlR/tsgLrrBV/y5y8MdnMO2/XZA0nb5Co= Received: by 10.70.27.18 with SMTP id a18mr2823961wxa.1168517854224; Thu, 11 Jan 2007 04:17:34 -0800 (PST) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTP id 7sm988942wrl.2007.01.11.04.17.31; Thu, 11 Jan 2007 04:17:33 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id l0BCJ416040472 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 11 Jan 2007 21:19:04 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l0BCJ44W040471; Thu, 11 Jan 2007 21:19:04 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Thu, 11 Jan 2007 21:19:04 +0900 From: Pyun YongHyeon To: Pietro Cerutti Message-ID: <20070111121904.GD33964@cdnetworks.co.kr> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-hackers@freebsd.org, FreeBSD Questions Subject: Re: [SOLVED] re(4) incorrect checksum X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 12:46:43 -0000 On Thu, Jan 11, 2007 at 11:51:51AM +0100, Pietro Cerutti wrote: > Hi lists, > ifconfig re0 -txcsum -rxcsum solved the problem.... > In if_re.c, rev 1.46.2.18 wpaul@ fixed a long standing checksum offload issue by padding. Does re(4) work when you disable only Tx checksum offload?(i.e. ifconfig re0 -txcsum) > Anyway, is this a bug in the driver or in the interface itself? > > Thanx, regards > > ---------- Forwarded message ---------- > From: Pietro Cerutti > Date: Jan 11, 2007 11:29 AM > Subject: re(4) incorrect checksum > To: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org > > > Hi lists, > > FreeBSD gahrtop.localhost 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #1: > Tue Jan 9 19:34:13 CET 2007 > root@gahrtop:/usr/obj/usr/src/sys/GAHRTOP i386 > > CPU: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz (2000.15-MHz 686-class > CPU) > Cores per package: 2 > > re0: port 0xc800-0xc8ff > mem 0xff2ff000-0xff2fffff irq 17 at device 0.0 on pci2 > > ($FreeBSD: src/sys/dev/re/if_re.c,v 1.46.2.20 2006/09/21 11:08:28 yongari > Exp $) > > I get checksum errors on every packet I send, example: > > Checksum: 0x0bc5 [incorrect, should be 0x78fe (maybe caused by > checksum offloading?)] > > I think this could be the cause of some web pages (e.g. Gmail in > standard view [html view works well]) not to be displayed. > > I tracked down the problem to the re(4) driver just because wlan works > good... > > Any ideas? > > > Thanx, > > -- > Pietro Cerutti > ICQ: 117293691 > PGP: 0x9571F78E > > - ASCII Ribbon Campaign - > against HTML e-mail and > proprietary attachments > www.asciiribbon.org > > > -- > Pietro Cerutti > ICQ: 117293691 > PGP: 0x9571F78E > > - ASCII Ribbon Campaign - > against HTML e-mail and > proprietary attachments > www.asciiribbon.org > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" -- Regards, Pyun YongHyeon From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 14:35:11 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A62F016A412 for ; Thu, 11 Jan 2007 14:35:11 +0000 (UTC) (envelope-from freebsd-hackers@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 4CF1613C442 for ; Thu, 11 Jan 2007 14:35:11 +0000 (UTC) (envelope-from freebsd-hackers@m.gmane.org) Received: from root by ciao.gmane.org with local (Exim 4.43) id 1H511C-0007hB-H3 for freebsd-hackers@freebsd.org; Thu, 11 Jan 2007 15:35:02 +0100 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 11 Jan 2007 15:35:02 +0100 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 11 Jan 2007 15:35:02 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-hackers@freebsd.org From: Ivan Voras Date: Thu, 11 Jan 2007 15:30:06 +0100 Lines: 24 Message-ID: References: <200701102321.01562.lists@jnielsen.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 1.5.0.4 (X11/20060625) In-Reply-To: <200701102321.01562.lists@jnielsen.net> Sender: news Subject: Re: Best practices for using gjournal with gmirror? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 14:35:11 -0000 John Nielsen wrote: > 2) When using gjournal and for a gmirror volume, does the journal need to be > mirrored as well to maintain redundancy? If so, when storing the journal on Yes, and to maintain consistency. If your machine dies while data is still in journal and not yet committed to permanent storage, you might have corruption. > the same physical disks as the mirror, is it better to mirror at the slice > level (journal and fs on different partitions in the same mirror) or at the > partition level (journal and fs each have their own mirror) or does it > matter? It doesn't matter. By default journal will be created inside the same partition as the file system. > 4) In the same vein as 3)--does a gjournal volume need to be fsck'ed after a > crash? If not, will it just work (e.g. fsck -p sees that the filesystem is > clean) or does it need to be disabled somehow? Fsck will still run, but there will be no need for it to check the entire file system, only some summary information and unlinked files. It will be as fast as fsck on softupdates-enabled file system. From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 15:09:26 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 70A5516A407; Thu, 11 Jan 2007 15:09:26 +0000 (UTC) (envelope-from bsd@bsdhome.com) Received: from ms-smtp-03.southeast.rr.com (ms-smtp-03.southeast.rr.com [24.25.9.102]) by mx1.freebsd.org (Postfix) with ESMTP id 33FED13C465; Thu, 11 Jan 2007 15:09:26 +0000 (UTC) (envelope-from bsd@bsdhome.com) Received: from neutrino.bsdhome.com (cpe-071-070-208-236.nc.res.rr.com [71.70.208.236]) by ms-smtp-03.southeast.rr.com (8.13.6/8.13.6) with ESMTP id l0BF9JPV022609; Thu, 11 Jan 2007 10:09:19 -0500 (EST) Received: from neutrino.bsdhome.com (localhost [127.0.0.1]) by neutrino.bsdhome.com (8.13.1/8.13.1) with ESMTP id l0BF9ICr052168; Thu, 11 Jan 2007 10:09:18 -0500 (EST) (envelope-from bsd@neutrino.bsdhome.com) Received: (from bsd@localhost) by neutrino.bsdhome.com (8.13.1/8.13.1/Submit) id l0BF9AKH052167; Thu, 11 Jan 2007 10:09:10 -0500 (EST) (envelope-from bsd) Date: Thu, 11 Jan 2007 10:09:10 -0500 From: Brian Dean To: "Brad L. Chisholm" Message-ID: <20070111150910.GA51998@neutrino.bsdhome.com> References: <20070110215207.GA85834@bsdone.bsdwins.com> <200701101753.24716.jhb@freebsd.org> <20070111001534.GA319@bsdone.bsdwins.com> <200701102211.39412.jhb@freebsd.org> <20070111070426.GB52964@bsdone.bsdwins.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070111070426.GB52964@bsdone.bsdwins.com> User-Agent: Mutt/1.5.11 X-Virus-Scanned: Symantec AntiVirus Scan Engine Cc: freebsd-hackers@freebsd.org Subject: Re: Kernel hang on 6.x X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 15:09:26 -0000 > On Wed, Jan 10, 2007 at 10:11:38PM -0500, John Baldwin wrote: > > On Wednesday 10 January 2007 19:15, Brad L. Chisholm wrote: > > > > > > SWAPMETA: 288, 116519, 116519, 0, 116543 > > > > yep, that's exactly the issue you are hitting. Thanks, John! That's awesome. I agree with Brad that if it is possible to autosize this at boot based on swap size, that would be the thing to do. Thanks very much for your help. -Brian -- Brian Dean bsd@FreeBSD.org From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 15:36:05 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D9F1016A49E for ; Thu, 11 Jan 2007 15:36:05 +0000 (UTC) (envelope-from vd@datamax.bg) Received: from jengal.datamax.bg (jengal.datamax.bg [82.103.104.21]) by mx1.freebsd.org (Postfix) with ESMTP id 97DC913C4A6 for ; Thu, 11 Jan 2007 15:36:05 +0000 (UTC) (envelope-from vd@datamax.bg) Received: from qlovarnika.bg.datamax (qlovarnika.bg.datamax [192.168.10.2]) by jengal.datamax.bg (Postfix) with SMTP id 95D79B848; Thu, 11 Jan 2007 17:12:58 +0200 (EET) Received: (nullmailer pid 68934 invoked by uid 1002); Thu, 11 Jan 2007 15:12:58 -0000 Date: Thu, 11 Jan 2007 17:12:58 +0200 From: Vasil Dimov To: Ivan Voras Message-ID: <20070111151258.GA68876@qlovarnika.bg.datamax> References: <200701102321.01562.lists@jnielsen.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0OAP2g/MAC+5xKAE" Content-Disposition: inline In-Reply-To: Cc: freebsd-hackers@freebsd.org Subject: Re: Best practices for using gjournal with gmirror? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vd@FreeBSD.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 15:36:05 -0000 --0OAP2g/MAC+5xKAE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 11, 2007 at 15:30:06 +0100, Ivan Voras wrote: > John Nielsen wrote: [...] > > is it better to mirror at the slice=20 > > level (journal and fs on different partitions in the same mirror) or at= the=20 > > partition level (journal and fs each have their own mirror) or does it= =20 > > matter? >=20 > It doesn't matter. By default journal will be created inside the same > partition as the file system. It matters a bit - in case of a single mirror (and all partitions on top of it) when there is a crash, during disk activity, the whole mirror will get rebuild. While if there is a separate mirror for each filesystem the chance is that some filesystems will not be active during the power failure/crash and thus their mirror will not need to be rebuild. It is just a matter of speed, not data loss, and it depends on the usage of the filesystems. Currently I have 2 mirrors and after a crash just one of them is rebuild because the other one is rarely used. --=20 Vasil Dimov gro.DSBeerF@dv % Shaw's Principle: Build a system that even a fool can use, and only a fool will want to use it. --0OAP2g/MAC+5xKAE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- iD8DBQFFplP6Fw6SP/bBpCARArSvAKDfJM1NlnUHMmlOfv850l6EW31uWACdEuqY HQX8Qn4IowAdyWd6VDZyKWM= =kPjo -----END PGP SIGNATURE----- --0OAP2g/MAC+5xKAE-- From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 15:37:10 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9B2A616A541 for ; Thu, 11 Jan 2007 15:37:10 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.186]) by mx1.freebsd.org (Postfix) with ESMTP id 057AC13C455 for ; Thu, 11 Jan 2007 15:37:09 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: by nf-out-0910.google.com with SMTP id k27so907513nfc for ; Thu, 11 Jan 2007 07:37:08 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding; b=hzM9CzGhJBJDL9tgEEVjk9hsTg8WHLuPyDPTQjQeOei0GTqyRRus3+ebN/aeQ5i1ENSjQJm0C8wIpAQCOpJgRS+7mbQqV8ZlTsghu+tqEMxbgrFa6r2cXy5J0l0ZmvPKanHslwWghmW/W3U9mECwKC7latfYcET8wDnWV9oznSg= Received: by 10.48.245.17 with SMTP id s17mr2224873nfh.1168529828763; Thu, 11 Jan 2007 07:37:08 -0800 (PST) Received: from ?192.168.123.202? ( [195.241.221.201]) by mx.google.com with ESMTP id c28sm7461233nfb.2007.01.11.07.37.07; Thu, 11 Jan 2007 07:37:08 -0800 (PST) Message-ID: <45A659A1.2060401@gmail.com> Date: Thu, 11 Jan 2007 16:37:05 +0100 From: Rene Ladan User-Agent: Thunderbird 1.5.0.9 (X11/20061224) MIME-Version: 1.0 To: pyunyh@gmail.com References: <45A61C1A.3090600@gmail.com> <20070111122049.GE33964@cdnetworks.co.kr> In-Reply-To: <20070111122049.GE33964@cdnetworks.co.kr> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, Pietro Cerutti Subject: Re: re(4) incorrect checksum X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 15:37:10 -0000 Pyun YongHyeon schreef: > On Thu, Jan 11, 2007 at 12:14:34PM +0100, Rene Ladan wrote: > > Pietro Cerutti schreef: > > > Hi lists, > > > > > > FreeBSD gahrtop.localhost 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #1: > > > Tue Jan 9 19:34:13 CET 2007 > > > root@gahrtop:/usr/obj/usr/src/sys/GAHRTOP i386 > > > > > > CPU: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz (2000.15-MHz > > > 686-class CPU) > > > Cores per package: 2 > > > > > > re0: port 0xc800-0xc8ff > > > mem 0xff2ff000-0xff2fffff irq 17 at device 0.0 on pci2 > > > > > > ($FreeBSD: src/sys/dev/re/if_re.c,v 1.46.2.20 2006/09/21 11:08:28 > > > yongari Exp $) > > > > > > I get checksum errors on every packet I send, example: > > > > > > Checksum: 0x0bc5 [incorrect, should be 0x78fe (maybe caused by > > > checksum offloading?)] > > > > > > I think this could be the cause of some web pages (e.g. Gmail in > > > standard view [html view works well]) not to be displayed. > > > > > > I tracked down the problem to the re(4) driver just because wlan works > > > good... > > > > > > Any ideas? > > > > > I'm also seeing these www problems with my re(4) card (chipid > > 0x816810ec), see > > http://lists.freebsd.org/pipermail/freebsd-current/2006-December/068333.html > > > > Does your re(4) also work when you disable checksum offload? > Yes, 'ifconfig re0 -txcsum' does the trick. re0: port 0xc800-0xc8ff mem 0xfe0ff000-0xfe0fffff irq 16 at device 0.0 on pci2 if.re.c revision 1.80 2006/12/20 02:13:59 marius Regards, Rene -- GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) "It won't fit on the line." -- me, 2001 From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 16:34:21 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3030D16A407 for ; Thu, 11 Jan 2007 16:34:21 +0000 (UTC) (envelope-from pietro.cerutti@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.174]) by mx1.freebsd.org (Postfix) with ESMTP id B482D13C45B for ; Thu, 11 Jan 2007 16:34:20 +0000 (UTC) (envelope-from pietro.cerutti@gmail.com) Received: by ug-out-1314.google.com with SMTP id o2so468662uge for ; Thu, 11 Jan 2007 08:34:19 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Fg9b6zMtNFIHonlcuah0OuEagm/cBG07yDMJzTHf7u0u3BMLCwx84y6s8N7dPNZImOg9C2NSeJ7G+0T7IBpKGUevZXbA9YKhY9UTeC/vH9YEktiOviQmEVxzEH+HrdbvjtY2UMgu4NKEP7/bpAFew5iMFc3O+euMEFv3+E1bhgs= Received: by 10.67.93.6 with SMTP id v6mr1950835ugl.1168533259525; Thu, 11 Jan 2007 08:34:19 -0800 (PST) Received: by 10.67.23.8 with HTTP; Thu, 11 Jan 2007 08:34:19 -0800 (PST) Message-ID: Date: Thu, 11 Jan 2007 17:34:19 +0100 From: "Pietro Cerutti" To: pyunyh@gmail.com In-Reply-To: <20070111121904.GD33964@cdnetworks.co.kr> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070111121904.GD33964@cdnetworks.co.kr> Cc: freebsd-hackers@freebsd.org, FreeBSD Questions Subject: Re: [SOLVED] re(4) incorrect checksum X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 16:34:21 -0000 On 1/11/07, Pyun YongHyeon wrote: > In if_re.c, rev 1.46.2.18 wpaul@ fixed a long standing checksum > offload issue by padding. Does re(4) work when you disable only Tx > checksum offload?(i.e. ifconfig re0 -txcsum) yes, because -txcsum also disables Rx checksum on my NIC. # ifconfig re0 .... options=1b .... # ifconfig re0 -txcsum .... options=18 .... > -- > Regards, > Pyun YongHyeon > -- Pietro Cerutti ICQ: 117293691 PGP: 0x9571F78E - ASCII Ribbon Campaign - against HTML e-mail and proprietary attachments www.asciiribbon.org From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 16:41:42 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5139616A657 for ; Thu, 11 Jan 2007 16:41:41 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.freebsd.org (Postfix) with ESMTP id 111D413C45D for ; Thu, 11 Jan 2007 16:41:38 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id l0BGfHZT097859; Thu, 11 Jan 2007 11:41:31 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Peter Jeremy Date: Thu, 11 Jan 2007 11:22:09 -0500 User-Agent: KMail/1.9.1 References: <20070110215207.GA85834@bsdone.bsdwins.com> <200701102211.39412.jhb@freebsd.org> <20070111092153.GG833@turion.vk2pj.dyndns.org> In-Reply-To: <20070111092153.GG833@turion.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200701111122.09936.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Thu, 11 Jan 2007 11:41:31 -0500 (EST) X-Virus-Scanned: ClamAV 0.88.3/2436/Thu Jan 11 06:48:19 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: "Brad L. Chisholm" , freebsd-hackers@freebsd.org Subject: Re: Kernel hang on 6.x X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 16:41:42 -0000 On Thursday 11 January 2007 04:21, Peter Jeremy wrote: > On Wed, 2007-Jan-10 22:11:38 -0500, John Baldwin wrote: > >64 / 14. That gives a result of 153405586. However, you really want to > >round this up to a multiple of 288 (because the kernel rounds it down to > >a multiple of 288), so I'd use a value of at least 153405792. > > Looking at the code, it seems that each SWAPMETA object manages 16 pages. Up to 16 pages. Not all 16 slots are always used apparently (based on empirical evidence where I've locked up a box that had enough swap_zone items for all of swap space assuming each object mapped 16 pages and it still deadlocked). I think it depends on the access pattern as to how full the various objects are. -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 16:41:57 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7BC3F16A725 for ; Thu, 11 Jan 2007 16:41:57 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.freebsd.org (Postfix) with ESMTP id 7DFE313C465 for ; Thu, 11 Jan 2007 16:41:55 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id l0BGfHZU097859; Thu, 11 Jan 2007 11:41:37 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: "Brad L. Chisholm" Date: Thu, 11 Jan 2007 11:22:44 -0500 User-Agent: KMail/1.9.1 References: <20070110215207.GA85834@bsdone.bsdwins.com> <200701102211.39412.jhb@freebsd.org> <20070111070426.GB52964@bsdone.bsdwins.com> In-Reply-To: <20070111070426.GB52964@bsdone.bsdwins.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200701111122.45347.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Thu, 11 Jan 2007 11:41:38 -0500 (EST) X-Virus-Scanned: ClamAV 0.88.3/2436/Thu Jan 11 06:48:19 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-hackers@freebsd.org Subject: Re: Kernel hang on 6.x X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 16:41:57 -0000 On Thursday 11 January 2007 02:04, Brad L. Chisholm wrote: > On Wed, Jan 10, 2007 at 10:11:38PM -0500, John Baldwin wrote: > > On Wednesday 10 January 2007 19:15, Brad L. Chisholm wrote: > > > > > > I notice the following in the vm.zone output captured just prior to > > > a hang. Does this value correspond to the swap_zone you were referring > > > to? This looks like a limit may have been reached. > > > > > > SWAPMETA: 288, 116519, 116519, 0, 116543 > > > > yep, that's exactly the issue you are hitting. > > > > > I don't seem to be able to query kern.maxswzone on our 6.2-BETA2 image: > > > > > > # sysctl kern.maxswzone > > > sysctl: unknown oid 'kern.maxswzone' > > > > > > Is it available in 6.x, or is it something newer? > > > > It's only a tunable, not available as a sysctl. You can figure out the > > current size from the vmstat output above, then do some math to figure > > out a good guess to use based on how much swap it had in use when it > > locked up. For example, right now you have 116519 objects of size 288, so > > 33557472 bytes allocated. You said you die when 14 GB out of 64 total is > > used, so you should probably try taking that value and multiplying it by > > 64 / 14. That gives a result of 153405586. However, you really want to > > round this up to a multiple of 288 (because the kernel rounds it down to > > a multiple of 288), so I'd use a value of at least 153405792. And yes, > > that means you are setting aside a little over 146 MB of wired, physical > > RAM just to hold metadata for your swap. :) > > > > Excellent! Increasing kern.maxswzone has indeed fixed the problem. Can > this value be auto-tuned better based upon the size of swap, or is it the > particular swapping pattern caused by our environment that caused the > default size to be insufficient? In any case, the kernel printf you added > recently should help make this much easier to diagnose in the future. > > Thanks for your help! The kernel does do a guess, but it doesn't always get the guess right, and I think there might be a bug where it always guesses wrong for > 32GB of swap. :) -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 17:08:26 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4A65216A415 for ; Thu, 11 Jan 2007 17:08:26 +0000 (UTC) (envelope-from davidn@datalinktech.com.au) Received: from customer-domains.icp-qv1-irony14.iinet.net.au (customer-domains.icp-qv1-irony14.iinet.net.au [203.59.1.169]) by mx1.freebsd.org (Postfix) with ESMTP id BA7DA13C4A8 for ; Thu, 11 Jan 2007 17:08:25 +0000 (UTC) (envelope-from davidn@datalinktech.com.au) Received: from 203-206-162-119.perm.iinet.net.au (HELO mail.datalinktech.com.au) ([203.206.162.119]) by iinet-mail.icp-qv1-irony14.iinet.net.au with ESMTP; 12 Jan 2007 01:57:55 +0900 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao8CAL76pUXLzqJ3/2dsb2JhbAA X-IronPort-AV: i="4.13,174,1167577200"; d="scan'208"; a="90353703:sNHT15231090" Received: from [192.168.69.138] ([192.168.69.138]) by mail.datalinktech.com.au with esmtp; Fri, 12 Jan 2007 03:57:38 +1100 id 0017B854.45A66C82.00004602 Message-ID: <45A66C89.4070405@datalinktech.com.au> Date: Fri, 12 Jan 2007 03:57:45 +1100 From: David Nugent User-Agent: Thunderbird 1.5.0.9 (X11/20070109) MIME-Version: 1.0 To: Vulpes Velox References: <60737.24.71.119.183.1168496463.squirrel@webmail.sd73.bc.ca> <45A5EA3B.9020000@datalinktech.com.au> <20070111035549.7c11a450@vixen42> In-Reply-To: <20070111035549.7c11a450@vixen42> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: hackers@freebsd.org Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 17:08:26 -0000 Vulpes Velox wrote: > I vote both are completely stupid. LDAP is nice organizing across > many systems, but if you are just dealing with one computer it is > complete over kill for any thing. Splitting rc.conf up into > multiple files is just plain messy and stupid as well. I can see > there being times when it is split into two, but I don't see any > reason for more than that. > This is a UI issue. I personally prefer one file, I don't have to wade though directories searching for any specific knob. :) > There are plenty of nice ways to access and modify LDAP data. I would > say it is easily as friendly as editing text files to be pulled > across. > .. and can be scripted in a variety of languages. > I fail to see how LDAP is not a standard tool. It is a tool that is > really under utilized. > Because it is a tool that incurs a cost to learn, configure and deploy. I'm not denying the benefits at all. But I think it must be an option, at least until the advantages gain momentum. > What this gains is being able to store a lot of configuration stuff > in the same place. It makes permission handling a lot easier as well. > If you store it in a file any one with write access can edit it, but > with LDAP it can assign write access to specific attributes. With > files you would have to split it up across multiple files. > Again, there is a cost. You would be adding a third security framework to an ldap enabled system (we already have unix credentials overlaid by the MAC framework to which we add ldap directory rights), and they need to relate in some way since they are dependent when supporting a consistent security profile. LDAP ACLs and understanding issues such as DIT structure, schemas, properties and attributes and how and why of ldap searches doesn't come naturally either, so you're dealing with a non-trivial learning curve. The benefits are plain to the 'already enlightened' but difficult to convince those who are not unless there is a very real problem to solve, not just a desire to deploy the technology for whatever reason. Maybe the technology will eventually become completely robust, easily installed and managed and offer some very significant benefits. I may be wrong, but I don't think we are at that point quite yet, but I'd certainly like to see it happen and probably will at some point in the future. Regards, -d From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 17:33:44 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4A5E816A407 for ; Thu, 11 Jan 2007 17:33:44 +0000 (UTC) (envelope-from jgrosch@mooseriver.com) Received: from gdead.mooseriver.com (gdead.mooseriver.com [205.166.121.45]) by mx1.freebsd.org (Postfix) with ESMTP id 3426C13C458 for ; Thu, 11 Jan 2007 17:33:44 +0000 (UTC) (envelope-from jgrosch@mooseriver.com) Received: by gdead.mooseriver.com (Postfix, from userid 2010) id 134113C8ADD; Thu, 11 Jan 2007 09:04:31 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on gdead.mooseriver.com X-Spam-Level: X-Spam-Status: No, score=-0.7 required=5.0 tests=AWL,BAYES_00, DNS_FROM_RFC_WHOIS,FORGED_RCVD_HELO autolearn=no version=3.1.7 Received: from mooseriver.com (h-66-166-146-73.snvacaid.covad.net [66.166.146.73]) by gdead.mooseriver.com (Postfix) with ESMTP id 9984A3C8AD5 for ; Thu, 11 Jan 2007 09:04:25 -0800 (PST) Received: by mooseriver.com (Postfix, from userid 200) id DAA132F0513; Thu, 11 Jan 2007 09:04:24 -0800 (PST) Date: Thu, 11 Jan 2007 09:04:24 -0800 From: Josef Grosch To: freebsd-hackers@freebsd.org Message-ID: <20070111170424.GA85484@mooseriver.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="huq684BweRXVnRxX" Content-Disposition: inline User-Agent: Mutt/1.4.2.2i Organization: Moose River, LLC Subject: Getting a patch commited X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jgrosch@MooseRiver.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 17:33:44 -0000 --huq684BweRXVnRxX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I know everyone is busy with getting 6.2 out the door but could someone commit the patch at conf/107453 ? Thanks Josef --=20 Josef Grosch | Another day closer to a | FreeBSD 6.1 jgrosch@MooseRiver.com | Micro$oft free world | Berkeley, Ca. --huq684BweRXVnRxX Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- iD8DBQFFpm4Xy8prLS1GYSERAhXdAKCovRLB8t41Y88AbyKzX9NOXIfmmACgt0Sn r/QzqYxFZPV3ELiprTkyouI= =Qw0W -----END PGP SIGNATURE----- --huq684BweRXVnRxX-- From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 17:45:58 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 58DF316A407 for ; Thu, 11 Jan 2007 17:45:58 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: from mired.org (vpn.mired.org [66.92.153.74]) by mx1.freebsd.org (Postfix) with SMTP id DAFF313C441 for ; Thu, 11 Jan 2007 17:45:57 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: (qmail 54997 invoked by uid 1001); 11 Jan 2007 17:18:51 -0000 Received: by bhuda.mired.org (tmda-sendmail, from uid 1001); Thu, 11 Jan 2007 12:18:50 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17830.29050.791321.480369@bhuda.mired.org> Date: Thu, 11 Jan 2007 12:18:50 -0500 To: Vulpes Velox In-Reply-To: <20070111035549.7c11a450@vixen42> References: <60737.24.71.119.183.1168496463.squirrel@webmail.sd73.bc.ca> <45A5EA3B.9020000@datalinktech.com.au> <20070111035549.7c11a450@vixen42> X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.1.5 (Fettercairn) From: Mike Meyer Cc: hackers@freebsd.org Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 17:45:58 -0000 In <20070111035549.7c11a450@vixen42>, Vulpes Velox typed: > LDAP is nice organizing across many systems, but if you are just > dealing with one computer it is complete over kill for any thing. In that situation, it's not merely overkill, it's may actually be a bad idea. Can you say "AIX SDR"? How about "Windows registry"? Those system both took the approach of putting all the configuration information in a central database. This creates problems because the tools needed to examine/fix the config database require a complex environment - at least compared to a statically linked copy of ed. LDAP may not be so bad, but it still makes me nervous. On the other hand, if you've got a flock of boxes to manage, having a way to tell the rc subsystem "Go read config values from this LDAP server" seems like a very attractive alternative. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 18:25:38 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A268016A416 for ; Thu, 11 Jan 2007 18:25:38 +0000 (UTC) (envelope-from phi@evilphi.com) Received: from mail.twinthornes.com (mail.twinthornes.com [65.75.198.147]) by mx1.freebsd.org (Postfix) with ESMTP id 7E0C113C474 for ; Thu, 11 Jan 2007 18:25:38 +0000 (UTC) (envelope-from phi@evilphi.com) Received: from [10.9.70.3] (c-24-20-142-99.hsd1.or.comcast.net [24.20.142.99]) by mail.twinthornes.com (Postfix) with ESMTP id AA998E15; Thu, 11 Jan 2007 09:57:27 -0800 (PST) Message-ID: <45A67A34.5080001@evilphi.com> Date: Thu, 11 Jan 2007 09:56:04 -0800 From: Darren Pilgrim User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Mike Meyer References: <60737.24.71.119.183.1168496463.squirrel@webmail.sd73.bc.ca> <45A5EA3B.9020000@datalinktech.com.au> <20070111035549.7c11a450@vixen42> <17830.29050.791321.480369@bhuda.mired.org> In-Reply-To: <17830.29050.791321.480369@bhuda.mired.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Thu, 11 Jan 2007 18:39:13 +0000 Cc: hackers@freebsd.org, Vulpes Velox Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 18:25:38 -0000 Mike Meyer wrote: > In <20070111035549.7c11a450@vixen42>, Vulpes Velox typed: >> LDAP is nice organizing across many systems, but if you are just >> dealing with one computer it is complete over kill for any thing. > > In that situation, it's not merely overkill, it's may actually be a > bad idea. Can you say "AIX SDR"? How about "Windows registry"? > > Those system both took the approach of putting all the configuration > information in a central database. This creates problems because the > tools needed to examine/fix the config database require a complex > environment - at least compared to a statically linked copy of > ed. LDAP may not be so bad, but it still makes me nervous. > > On the other hand, if you've got a flock of boxes to manage, having a > way to tell the rc subsystem "Go read config values from this LDAP > server" seems like a very attractive alternative. And to think, all these years I've been wasting my time and effort using NFS and rsync to centralize the configurations of server farms. -- Darren Pilgrim From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 18:42:07 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0FAD716AA7D for ; Thu, 11 Jan 2007 18:42:07 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by mx1.freebsd.org (Postfix) with SMTP id B46A513C45A for ; Thu, 11 Jan 2007 18:42:06 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 25252 invoked by uid 399); 11 Jan 2007 18:42:06 -0000 Received: from localhost (HELO ?192.168.0.5?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 11 Jan 2007 18:42:06 -0000 X-Originating-IP: 127.0.0.1 Message-ID: <45A684FC.4070609@FreeBSD.org> Date: Thu, 11 Jan 2007 10:42:04 -0800 From: Doug Barton Organization: http://www.freebsd.org/ User-Agent: Thunderbird 1.5.0.8 (X11/20061215) MIME-Version: 1.0 To: Lamont Granquist References: <20070107190616.73dee7b0@vixen42> <45A1DE76.7000201@FreeBSD.org> <20070108185247.2b6e1f69@vixen42> <45A407D1.9030101@FreeBSD.org> <20070109184346.135e0bf4@vixen42> <45A56107.5050205@FreeBSD.org> <45A566D7.4040907@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Use of /etc/rc.conf.d (Was: Re: LDAP integration) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 18:42:07 -0000 Lamont Granquist wrote: > > On Wed, 10 Jan 2007, Doug Barton wrote: >> It's not documented, but the code is there in /etc/rc.subr: >> >> grep 'rc.conf\.d' /etc/rc.subr >> if [ -f /etc/rc.conf.d/"$_name" ]; then >> debug "Sourcing /etc/rc.conf.d/${_name}" >> . /etc/rc.conf.d/"$_name" >> ... > > If i understand that correctly its not *exactly* what i was looking for, > but its better than a monolithic /etc/rc.conf > > It looks like you must put /etc/rc.d/inetd config into either > /etc/rc.conf or /etc/rc.config.d/inetd. Actually you can use both, but where variable names overlap whatever is sourced last will "win." > That means that if you've got two different orthogonal applications > runing on the same server which both need to run something orthogonal > out of inetd then they still wind up needing to do edits to the same > config file to get inetd configured correctly. Not exactly (and I think you're overusing the term orthogonal). :) rc.conf and /etc/rc.conf.d only store configuration for the rc.d scripts themselves. The configuration of inetd is still stored in /etc/inetd.conf. $ grep inetd /etc/defaults/rc.conf inetd_enable="NO" # Run the network daemon dispatcher (YES/NO). inetd_program="/usr/sbin/inetd" # path to inetd, if you want a different one. inetd_flags="-wW -C 60" # Optional flags to inetd vs. everything that is in /etc/inetd.conf. > I'd rather see > /etc/rc.config.d/app01 and /etc/rc.config.d/app02 both able to tweak > inetd settings. Of course there is the possibility that app01 and app02 > could drop mutually conflicting inetd setttings, but you've got that > problem anyway in the existing scheme... I think this'd be great, I can't wait to see your patches. :) Doug -- This .signature sanitized for your protection From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 19:34:48 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 522D116A403 for ; Thu, 11 Jan 2007 19:34:48 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 3DBFD13C442 for ; Thu, 11 Jan 2007 19:34:48 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 1EDD81A4D97; Thu, 11 Jan 2007 11:34:48 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 8A8895156B; Thu, 11 Jan 2007 14:34:47 -0500 (EST) Date: Thu, 11 Jan 2007 14:34:47 -0500 From: Kris Kennaway To: Rene Ladan Message-ID: <20070111193447.GA35711@xor.obsecurity.org> References: <45A61C1A.3090600@gmail.com> <20070111122049.GE33964@cdnetworks.co.kr> <45A659A1.2060401@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="OgqxwSJOaUobr8KG" Content-Disposition: inline In-Reply-To: <45A659A1.2060401@gmail.com> User-Agent: Mutt/1.4.2.2i Cc: pyunyh@gmail.com, freebsd-hackers@freebsd.org, Pietro Cerutti Subject: Re: re(4) incorrect checksum X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 19:34:48 -0000 --OgqxwSJOaUobr8KG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 11, 2007 at 04:37:05PM +0100, Rene Ladan wrote: > Pyun YongHyeon schreef: > > On Thu, Jan 11, 2007 at 12:14:34PM +0100, Rene Ladan wrote: > > > Pietro Cerutti schreef: > > > > Hi lists, > > > >=20 > > > > FreeBSD gahrtop.localhost 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #1: > > > > Tue Jan 9 19:34:13 CET 2007 > > > > root@gahrtop:/usr/obj/usr/src/sys/GAHRTOP i386 > > > >=20 > > > > CPU: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz (2000.15-MHz > > > > 686-class CPU) > > > > Cores per package: 2 > > > >=20 > > > > re0: port 0xc800-0xc8ff > > > > mem 0xff2ff000-0xff2fffff irq 17 at device 0.0 on pci2 > > > >=20 > > > > ($FreeBSD: src/sys/dev/re/if_re.c,v 1.46.2.20 2006/09/21 11:08:28 > > > > yongari Exp $) > > > >=20 > > > > I get checksum errors on every packet I send, example: > > > >=20 > > > > Checksum: 0x0bc5 [incorrect, should be 0x78fe (maybe caused by > > > > checksum offloading?)] > > > >=20 > > > > I think this could be the cause of some web pages (e.g. Gmail in > > > > standard view [html view works well]) not to be displayed. > > > >=20 > > > > I tracked down the problem to the re(4) driver just because wlan w= orks > > > > good... > > > >=20 > > > > Any ideas? > > > >=20 > > > I'm also seeing these www problems with my re(4) card (chipid > > > 0x816810ec), see > > > http://lists.freebsd.org/pipermail/freebsd-current/2006-December/068= 333.html > > >=20 > >=20 > > Does your re(4) also work when you disable checksum offload? > >=20 > Yes, 'ifconfig re0 -txcsum' does the trick. >=20 > re0: port 0xc800-0xc8ff mem > 0xfe0ff000-0xfe0fffff irq 16 at device 0.0 on pci2 >=20 > if.re.c revision 1.80 2006/12/20 02:13:59 marius Can you confirm that you see checksum errors when viewing the packet from another host on the subnet? It's of course to be expected that a sending host with checksum offload on the NIC will not see the correct checksum before offloading the packet to the NIC, and this in itself does not indicate a problem. Kris --OgqxwSJOaUobr8KG Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.1 (FreeBSD) iD8DBQFFppFXWry0BWjoQKURAse2AJ40VBido0+37ilYXohYfbMj8t3DmQCeOCiH vxBjGZYIb5imJevNE5GrNS0= =ja4f -----END PGP SIGNATURE----- --OgqxwSJOaUobr8KG-- From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 19:40:53 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7F1EF16A7A9 for ; Thu, 11 Jan 2007 19:40:53 +0000 (UTC) (envelope-from craig@tobuj.gank.org) Received: from ion.gank.org (ion.gank.org [69.55.238.164]) by mx1.freebsd.org (Postfix) with ESMTP id 62C0D13C471 for ; Thu, 11 Jan 2007 19:40:53 +0000 (UTC) (envelope-from craig@tobuj.gank.org) Received: by ion.gank.org (Postfix, from userid 1001) id 1E82310F4B; Thu, 11 Jan 2007 13:21:45 -0600 (CST) Date: Thu, 11 Jan 2007 13:21:42 -0600 From: Craig Boston To: John Nielsen Message-ID: <20070111192142.GA1133@nowhere> Mail-Followup-To: Craig Boston , John Nielsen , freebsd-hackers@freebsd.org References: <200701102321.01562.lists@jnielsen.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200701102321.01562.lists@jnielsen.net> User-Agent: Mutt/1.4.2.2i Cc: freebsd-hackers@freebsd.org Subject: Re: Best practices for using gjournal with gmirror? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 19:40:53 -0000 On Wed, Jan 10, 2007 at 11:21:01PM -0500, John Nielsen wrote: > 5) Finally, how dangerous is this code? I realize it's experimental and only > plan to use it with data that has recent backups, but how much should I > worry about it blowing up my system or corrupting my files? Just my personal experience, but I've found the gjournal implementation to be extremely stable. I'm not doing anything terribly unusual with it, but both my laptop and my primary workstation use gjournal for all of their filesystems except / and /tmp. On my workstation one of the journaled filesystems (/home) is on a mirror using the ataraid(4) driver, but I've also successfully used it with gmirror. I do a lot of parallel source code extraction and building and have never run into a crash or panic that was caused by gjournal itself. The panics and deadlocks I have encountered due to other reasons have shown that using gjournal has actually significantly reduced the amount of FS corruption in those events. You still lose anything created or changed in the last ~30 seconds or so, but that's better than a corrupted FS. I would still be religious about backups just in case, but it's unlikely that gjournal will be the reason you have to use them. Craig * NOTE: I'm running the gjournal backport to RELENG_6. YMMV if running -CURRENT. From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 20:11:08 2007 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8369816A415; Thu, 11 Jan 2007 20:11:08 +0000 (UTC) (envelope-from lamont@scriptkiddie.org) Received: from sploit.scriptkiddie.org (sploit.scriptkiddie.org [216.231.47.214]) by mx1.freebsd.org (Postfix) with ESMTP id 4BF4C13C45D; Thu, 11 Jan 2007 20:11:08 +0000 (UTC) (envelope-from lamont@scriptkiddie.org) Received: from sploit (sploit [216.231.47.214]) by sploit.scriptkiddie.org (8.12.11/8.12.11) with ESMTP id l0BKB67g002846; Thu, 11 Jan 2007 12:11:06 -0800 (PST) Date: Thu, 11 Jan 2007 12:11:06 -0800 (PST) From: Lamont Granquist To: Doug Barton In-Reply-To: <45A684FC.4070609@FreeBSD.org> Message-ID: References: <20070107190616.73dee7b0@vixen42> <45A1DE76.7000201@FreeBSD.org> <20070108185247.2b6e1f69@vixen42> <45A407D1.9030101@FreeBSD.org> <20070109184346.135e0bf4@vixen42> <45A56107.5050205@FreeBSD.org> <45A566D7.4040907@FreeBSD.org> <45A684FC.4070609@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@FreeBSD.org Subject: Re: Use of /etc/rc.conf.d (Was: Re: LDAP integration) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 20:11:08 -0000 On Thu, 11 Jan 2007, Doug Barton wrote: > Lamont Granquist wrote: >> If i understand that correctly its not *exactly* what i was looking for, >> but its better than a monolithic /etc/rc.conf >> >> It looks like you must put /etc/rc.d/inetd config into either >> /etc/rc.conf or /etc/rc.config.d/inetd. > > Actually you can use both, but where variable names overlap whatever > is sourced last will "win." Yeah, poor english, I didn't mean to imply xor. >> That means that if you've got two different orthogonal applications >> runing on the same server which both need to run something orthogonal >> out of inetd then they still wind up needing to do edits to the same >> config file to get inetd configured correctly. > > Not exactly (and I think you're overusing the term orthogonal). :) I think what i really need to do is dig deeper to find truly orthogonal config in /etc/rc.conf. I realized after i posted that i was mixing up inetd settings of /etc/rc.conf and /etc/inetd.conf settings (the latter could really use being busted up int /etc/inetd.d or just using xinetd -- i'm guessing i'll probably find a bikeshed about xinetd if i search the archives though since i can't be the first person to suggest that...) >> I'd rather see >> /etc/rc.config.d/app01 and /etc/rc.config.d/app02 both able to tweak >> inetd settings. Of course there is the possibility that app01 and app02 >> could drop mutually conflicting inetd setttings, but you've got that >> problem anyway in the existing scheme... > > I think this'd be great, I can't wait to see your patches. :) I'll be diving in canada over the three day weekend, so we'll have to see how much i care about this issue a week from now... From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 20:21:46 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C102F16A412 for ; Thu, 11 Jan 2007 20:21:46 +0000 (UTC) (envelope-from lamont@scriptkiddie.org) Received: from sploit.scriptkiddie.org (sploit.scriptkiddie.org [216.231.47.214]) by mx1.freebsd.org (Postfix) with ESMTP id 81A0313C461 for ; Thu, 11 Jan 2007 20:21:46 +0000 (UTC) (envelope-from lamont@scriptkiddie.org) Received: from sploit (sploit [216.231.47.214]) by sploit.scriptkiddie.org (8.12.11/8.12.11) with ESMTP id l0BK3p4W002825; Thu, 11 Jan 2007 12:03:51 -0800 (PST) Date: Thu, 11 Jan 2007 12:03:51 -0800 (PST) From: Lamont Granquist To: Mike Meyer In-Reply-To: <17830.29050.791321.480369@bhuda.mired.org> Message-ID: References: <60737.24.71.119.183.1168496463.squirrel@webmail.sd73.bc.ca> <45A5EA3B.9020000@datalinktech.com.au> <20070111035549.7c11a450@vixen42> <17830.29050.791321.480369@bhuda.mired.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: hackers@freebsd.org, Vulpes Velox Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 20:21:46 -0000 On Thu, 11 Jan 2007, Mike Meyer wrote: > In <20070111035549.7c11a450@vixen42>, Vulpes Velox typed: >> LDAP is nice organizing across many systems, but if you are just >> dealing with one computer it is complete over kill for any thing. > > In that situation, it's not merely overkill, it's may actually be a > bad idea. Can you say "AIX SDR"? How about "Windows registry"? And then you take the windows registry from 1,000 machines and cram them into a centralized database and try to manage the resultant mess. I don't think this is a good solution. From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 20:21:47 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2BD3216A415 for ; Thu, 11 Jan 2007 20:21:47 +0000 (UTC) (envelope-from lamont@scriptkiddie.org) Received: from sploit.scriptkiddie.org (sploit.scriptkiddie.org [216.231.47.214]) by mx1.freebsd.org (Postfix) with ESMTP id DB58A13C478 for ; Thu, 11 Jan 2007 20:21:46 +0000 (UTC) (envelope-from lamont@scriptkiddie.org) Received: from sploit (sploit [216.231.47.214]) by sploit.scriptkiddie.org (8.12.11/8.12.11) with ESMTP id l0BK03Cv002799; Thu, 11 Jan 2007 12:00:03 -0800 (PST) Date: Thu, 11 Jan 2007 12:00:03 -0800 (PST) From: Lamont Granquist To: Vulpes Velox In-Reply-To: <20070111035549.7c11a450@vixen42> Message-ID: References: <60737.24.71.119.183.1168496463.squirrel@webmail.sd73.bc.ca> <45A5EA3B.9020000@datalinktech.com.au> <20070111035549.7c11a450@vixen42> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: hackers@freebsd.org, David Nugent Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 20:21:47 -0000 On Thu, 11 Jan 2007, Vulpes Velox wrote: > I vote both are completely stupid. LDAP is nice organizing across > many systems, but if you are just dealing with one computer it is > complete over kill for any thing. Splitting rc.conf up into > multiple files is just plain messy and stupid as well. I can see > there being times when it is split into two, but I don't see any > reason for more than that. When was the last time you worked on a configuration management system which maintained 30,000 servers and had ~50 people with commit access to it? In such a situation you wind up with multiple people managing horizontal slices out of all of the machines. You no longer have the model of a single admin for a single server who knows everything about the config of a given machine. In that situation it becomes very useful for admin #1 who is managing a particular aspect of the config to be able to drop a file like /etc/rc.conf.d/foo and admin #2 who is managing a different aspect of the config to be able to drop a file like /etc/rc.conf.d/bar. Having both of them editing /etc/rc.conf opens up the very real possiblity of having simple editing conflicts which corrupt the file. What I'm talking about with splitting up /etc/rc.conf isn't really orthogonal to anything that you've written about LDAP, however. You don't have to attack this idea just to make LDAP sound good. > There are plenty of nice ways to access and modify LDAP data. I would > say it is easily as friendly as editing text files to be pulled > across. > > I fail to see how LDAP is not a standard tool. It is a tool that is > really under utilized. In general database-driven configuration management is under utilized, I'll agree with that. LDAP is the first tool that you're going to pick up to do that, but I think its utility for the generalized problem is not as large as you think it is. > What this gains is being able to store a lot of configuration stuff > in the same place. It makes permission handling a lot easier as well. > If you store it in a file any one with write access can edit it, but > with LDAP it can assign write access to specific attributes. With > files you would have to split it up across multiple files. I simply don't understand why you want to start picking up raw configuration data on the end host and dumping it into LDAP. That doesn't solve a problem. I don't need host-by-host rc.conf variables or systls exposed through a database interface. I can use labels inside of cfengine to define roles which cause all kinds of actions to be taken, including setting /etc/rc.conf, setting sysctls, pushing scripts, managing daemons, mounting filesystems, etc, etc. What becomes useful is having those labels put into a database, not the results of the config itself. You could try to generate a completely database-driven configuration management language. So that in your schema for a given role you would attatch not only /etc/rc.conf information, but all the sysctls, daemon management, filesystem mounts, etc. But then the scope of what you're doing can be looked at as taking a cfengine configuration file (defining all the given config management steps taken for a given role) and putting it into a database. Without going all the way what you're trying to build isn't going to be very useful and I don't see the driver to do all that work. What is the compelling use case for taking the existing cfengine language (or any other CM language, e.g. puppet) and making it entirely database driven? From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 21:08:05 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 503A916A403 for ; Thu, 11 Jan 2007 21:08:05 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: from mired.org (vpn.mired.org [66.92.153.74]) by mx1.freebsd.org (Postfix) with SMTP id E9AB713C469 for ; Thu, 11 Jan 2007 21:08:04 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: (qmail 57778 invoked by uid 1001); 11 Jan 2007 21:07:40 -0000 Received: by bhuda.mired.org (tmda-sendmail, from uid 1001); Thu, 11 Jan 2007 16:07:40 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17830.42779.829357.835403@bhuda.mired.org> Date: Thu, 11 Jan 2007 16:07:39 -0500 To: Lamont Granquist In-Reply-To: References: <60737.24.71.119.183.1168496463.squirrel@webmail.sd73.bc.ca> <45A5EA3B.9020000@datalinktech.com.au> <20070111035549.7c11a450@vixen42> <17830.29050.791321.480369@bhuda.mired.org> X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.1.5 (Fettercairn) From: Mike Meyer Cc: hackers@freebsd.org, Vulpes Velox Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 21:08:05 -0000 In , Lamont Granquist typed: > > On Thu, 11 Jan 2007, Mike Meyer wrote: > > In <20070111035549.7c11a450@vixen42>, Vulpes Velox typed: > >> LDAP is nice organizing across many systems, but if you are just > >> dealing with one computer it is complete over kill for any thing. > > In that situation, it's not merely overkill, it's may actually be a > > bad idea. Can you say "AIX SDR"? How about "Windows registry"? > And then you take the windows registry from 1,000 machines and cram them > into a centralized database and try to manage the resultant mess. I don't > think this is a good solution. The difference is that when a single machine crashes, you can use a *different* machine to examine/fix the centralized database while you're working on that machine. If you just cram all the values into the central database, then you're no better off than you would be with flat files on every host. If, on the other hand, you organize the data in the database to reflect the organization of the systems, you can leverage things to cut down on the amount of work you have to do to propogate changes. Someone else mentioned rsync, and that works fairly well, though I prefer perforce. However, it's not quite as flexible - or as convenient - as a database. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 22:53:33 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 701BC16A407; Thu, 11 Jan 2007 22:53:33 +0000 (UTC) (envelope-from tataz@tataz.chchile.org) Received: from postfix2-g20.free.fr (postfix2-g20.free.fr [212.27.60.43]) by mx1.freebsd.org (Postfix) with ESMTP id 2B5D313C441; Thu, 11 Jan 2007 22:53:33 +0000 (UTC) (envelope-from tataz@tataz.chchile.org) Received: from smtp5-g19.free.fr (smtp5-g19.free.fr [212.27.42.35]) by postfix2-g20.free.fr (Postfix) with ESMTP id 334108DCADC; Thu, 11 Jan 2007 22:30:18 +0100 (CET) Received: from tatooine.tataz.chchile.org (tataz.chchile.org [82.233.239.98]) by smtp5-g19.free.fr (Postfix) with ESMTP id 1BF6627A9B; Thu, 11 Jan 2007 23:30:09 +0100 (CET) Received: from obiwan.tataz.chchile.org (unknown [192.168.1.25]) by tatooine.tataz.chchile.org (Postfix) with ESMTP id 665559D3DA; Thu, 11 Jan 2007 22:31:26 +0000 (UTC) Received: by obiwan.tataz.chchile.org (Postfix, from userid 1000) id 41F6E405D; Thu, 11 Jan 2007 23:31:26 +0100 (CET) Date: Thu, 11 Jan 2007 23:31:26 +0100 From: Jeremie Le Hen To: Vishal Patil Message-ID: <20070111223126.GJ2616@obiwan.tataz.chchile.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.13 (2006-08-11) Cc: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Subject: Re: vpnc problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 22:53:33 -0000 Hi Vishal, First of all you should avoid cross-posting. Additionaly, I don't think this is a question for -hackers@. On Wed, Jan 03, 2007 at 08:50:26PM -0500, Vishal Patil wrote: > I have found the answer to this question. I basically had to edit the > vpnc-script and replace the body of the function "get_default_gw" with > > netstat -r -n | sed 's/default/0.0.0.0/' | grep '^0.0.0.0' | awk '{print > $2}' > > So now I have vpnc-0.3.3 working on FreeBSD. The port stands in security/vpnc, you should use it. It guess the maintainer has tried it before updating the port and pushed the appropriate patch into the ports tree. Regards -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 12 00:30:52 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0FD8B16A416 for ; Fri, 12 Jan 2007 00:30:52 +0000 (UTC) (envelope-from fcash@ocis.net) Received: from smtp.sd73.bc.ca (smtp.sd73.bc.ca [142.24.13.140]) by mx1.freebsd.org (Postfix) with ESMTP id E574213C448 for ; Fri, 12 Jan 2007 00:30:51 +0000 (UTC) (envelope-from fcash@ocis.net) Received: from localhost (localhost [127.0.0.1]) by localhost.sd73.bc.ca (Postfix) with ESMTP id 56B6B1A000B2A for ; Thu, 11 Jan 2007 16:30:51 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at smtp.sd73.bc.ca Received: from smtp.sd73.bc.ca ([127.0.0.1]) by localhost (smtp.sd73.bc.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id ti-OUwksjhnH for ; Thu, 11 Jan 2007 16:30:44 -0800 (PST) Received: from coal (s10.sbo [192.168.0.10]) by smtp.sd73.bc.ca (Postfix) with ESMTP id D6CBB1A0007D6 for ; Thu, 11 Jan 2007 16:30:44 -0800 (PST) From: Freddie Cash To: freebsd-hackers@freebsd.org Date: Thu, 11 Jan 2007 16:30:43 -0800 User-Agent: KMail/1.9.5 References: <60737.24.71.119.183.1168496463.squirrel@webmail.sd73.bc.ca> <17830.29050.791321.480369@bhuda.mired.org> <45A67A34.5080001@evilphi.com> In-Reply-To: <45A67A34.5080001@evilphi.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200701111630.43734.fcash@ocis.net> Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2007 00:30:52 -0000 On Thursday 11 January 2007 09:56 am, Darren Pilgrim wrote: > Mike Meyer wrote: > > In <20070111035549.7c11a450@vixen42>, Vulpes Velox typed: > >> LDAP is nice organizing across many systems, but if you are just > >> dealing with one computer it is complete over kill for any thing. > > > > In that situation, it's not merely overkill, it's may actually be a > > bad idea. Can you say "AIX SDR"? How about "Windows registry"? > > > > Those system both took the approach of putting all the configuration > > information in a central database. This creates problems because the > > tools needed to examine/fix the config database require a complex > > environment - at least compared to a statically linked copy of > > ed. LDAP may not be so bad, but it still makes me nervous. > > > > On the other hand, if you've got a flock of boxes to manage, having a > > way to tell the rc subsystem "Go read config values from this LDAP > > server" seems like a very attractive alternative. > > And to think, all these years I've been wasting my time and effort > using NFS and rsync to centralize the configurations of server farms. I think (Mike will have to confirm/deny) what Mike was trying to say was that for a single system, a centralised database for configuration options was overkill and a problem. Using the Windows Registry as an example. But, using a centralised database for configuring dozens of systems (similar or otherwise) could be a good idea, and that LDAP may be good in that situation (a lot of reading going on at boot to create the configs). -- Freddie Cash fcash@ocis.net From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 12 02:00:14 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0AD3716A40F for ; Fri, 12 Jan 2007 02:00:13 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.238]) by mx1.freebsd.org (Postfix) with ESMTP id 8CEA013C441 for ; Fri, 12 Jan 2007 02:00:13 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by wx-out-0506.google.com with SMTP id s18so662055wxc for ; Thu, 11 Jan 2007 18:00:13 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=hwsGHxrJ515xZIuSC/hz0SmHwwh16w56UV8HxLvsAic6pfbveYzIq/4HqPwLlpnzRXLtWsfT9Ym8FfhiuSGVPz5HSVrXEe1UX/2D/aCX5EOD+LaS+MstrymlxMzVcD5ORO86eaEudWCpMOZcyklYSNyzcx9jnM6bkf9f3f+XjHo= Received: by 10.70.99.9 with SMTP id w9mr205338wxb.1168567213043; Thu, 11 Jan 2007 18:00:13 -0800 (PST) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTP id 44sm2104881wri.2007.01.11.18.00.10; Thu, 11 Jan 2007 18:00:12 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id l0C21oK3043075 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 12 Jan 2007 11:01:50 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l0C21oI4043074; Fri, 12 Jan 2007 11:01:50 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Fri, 12 Jan 2007 11:01:50 +0900 From: Pyun YongHyeon To: Rene Ladan Message-ID: <20070112020149.GA42529@cdnetworks.co.kr> References: <45A61C1A.3090600@gmail.com> <20070111122049.GE33964@cdnetworks.co.kr> <45A659A1.2060401@gmail.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="VbJkn9YxBvnuCH5J" Content-Disposition: inline In-Reply-To: <45A659A1.2060401@gmail.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-hackers@freebsd.org, Pietro Cerutti Subject: Re: re(4) incorrect checksum X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2007 02:00:14 -0000 --VbJkn9YxBvnuCH5J Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Jan 11, 2007 at 04:37:05PM +0100, Rene Ladan wrote: > Pyun YongHyeon schreef: > > On Thu, Jan 11, 2007 at 12:14:34PM +0100, Rene Ladan wrote: > > > Pietro Cerutti schreef: > > > > Hi lists, > > > > > > > > FreeBSD gahrtop.localhost 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #1: > > > > Tue Jan 9 19:34:13 CET 2007 > > > > root@gahrtop:/usr/obj/usr/src/sys/GAHRTOP i386 > > > > > > > > CPU: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz (2000.15-MHz > > > > 686-class CPU) > > > > Cores per package: 2 > > > > > > > > re0: port 0xc800-0xc8ff > > > > mem 0xff2ff000-0xff2fffff irq 17 at device 0.0 on pci2 > > > > > > > > ($FreeBSD: src/sys/dev/re/if_re.c,v 1.46.2.20 2006/09/21 11:08:28 > > > > yongari Exp $) > > > > > > > > I get checksum errors on every packet I send, example: > > > > > > > > Checksum: 0x0bc5 [incorrect, should be 0x78fe (maybe caused by > > > > checksum offloading?)] > > > > > > > > I think this could be the cause of some web pages (e.g. Gmail in > > > > standard view [html view works well]) not to be displayed. > > > > > > > > I tracked down the problem to the re(4) driver just because wlan works > > > > good... > > > > > > > > Any ideas? > > > > > > > I'm also seeing these www problems with my re(4) card (chipid > > > 0x816810ec), see > > > http://lists.freebsd.org/pipermail/freebsd-current/2006-December/068333.html > > > > > > > Does your re(4) also work when you disable checksum offload? > > > Yes, 'ifconfig re0 -txcsum' does the trick. > > re0: port 0xc800-0xc8ff mem > 0xfe0ff000-0xfe0fffff irq 16 at device 0.0 on pci2 > > if.re.c revision 1.80 2006/12/20 02:13:59 marius > I've never encountered checksum offload issue after wpaul's fix. How about attached one? It's just vague guess but please give it try and let me know the result. -- Regards, Pyun YongHyeon --VbJkn9YxBvnuCH5J Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="if_re.checksum.patch" Index: if_re.c =================================================================== RCS file: /home/ncvs/src/sys/dev/re/if_re.c,v retrieving revision 1.80 diff -u -r1.80 if_re.c --- if_re.c 20 Dec 2006 02:13:59 -0000 1.80 +++ if_re.c 12 Jan 2007 01:42:59 -0000 @@ -2027,9 +2027,9 @@ arg.rl_flags = RL_TDESC_CMD_LGSEND | ((uint32_t)(*m_head)->m_pkthdr.tso_segsz << RL_TDESC_CMD_MSSVAL_SHIFT); - else { - if ((*m_head)->m_pkthdr.csum_flags & CSUM_IP) - arg.rl_flags |= RL_TDESC_CMD_IPCSUM; + else if (((*m_head)->m_pkthdr.csum_flags & + (CSUM_IP | CSUM_TCP | CSUM_UDP)) != 0) { + arg.rl_flags |= RL_TDESC_CMD_IPCSUM; if ((*m_head)->m_pkthdr.csum_flags & CSUM_TCP) arg.rl_flags |= RL_TDESC_CMD_TCPCSUM; if ((*m_head)->m_pkthdr.csum_flags & CSUM_UDP) --VbJkn9YxBvnuCH5J-- From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 19:04:56 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 18C8316A416 for ; Thu, 11 Jan 2007 19:04:56 +0000 (UTC) (envelope-from nathan@vidican.com) Received: from wmptl.net (mail.wmptl.com [216.8.159.133]) by mx1.freebsd.org (Postfix) with ESMTP id BC80A13C448 for ; Thu, 11 Jan 2007 19:04:55 +0000 (UTC) (envelope-from nathan@vidican.com) Received: from [10.0.0.11] ([10.0.0.11]) by wmptl.net (8.13.4/8.13.4) with ESMTP id l0BIsgOd091167; Thu, 11 Jan 2007 13:54:42 -0500 (EST) (envelope-from nathan@vidican.com) Message-ID: <45A687F6.2020907@vidican.com> Date: Thu, 11 Jan 2007 13:54:46 -0500 From: Nathan Vidican User-Agent: Thunderbird 1.5.0.7 (X11/20061027) MIME-Version: 1.0 To: Mike Meyer , hackers@freebsd.org References: <60737.24.71.119.183.1168496463.squirrel@webmail.sd73.bc.ca> <45A5EA3B.9020000@datalinktech.com.au> <20070111035549.7c11a450@vixen42> <17830.29050.791321.480369@bhuda.mired.org> In-Reply-To: <17830.29050.791321.480369@bhuda.mired.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.54 on 10.0.0.80 X-Mailman-Approved-At: Fri, 12 Jan 2007 02:02:48 +0000 Cc: Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 19:04:56 -0000 Mike Meyer wrote: > In <20070111035549.7c11a450@vixen42>, Vulpes Velox typed: > >> LDAP is nice organizing across many systems, but if you are just >> dealing with one computer it is complete over kill for any thing. >> > > In that situation, it's not merely overkill, it's may actually be a > bad idea. Can you say "AIX SDR"? How about "Windows registry"? > > Those system both took the approach of putting all the configuration > information in a central database. This creates problems because the > tools needed to examine/fix the config database require a complex > environment - at least compared to a statically linked copy of > ed. LDAP may not be so bad, but it still makes me nervous. > > On the other hand, if you've got a flock of boxes to manage, having a > way to tell the rc subsystem "Go read config values from this LDAP > server" seems like a very attractive alternative. > > Ok, so the general consensus seems to be that it's a good idea in some cases and not in others. I myself agree that it should not be part of the base setup for issues regarding the complication of the base distribution... but why not make a package for it? Take this idea, and run with it... build a package that installs over the base installation, bundling the LDAP client libs, new rc structure, tools, etc all in one shot. Add it to the ports collection and call it done. - After all that's the wonder that is opensource... if ya want to improve something, go for it - even better if you can contribute your additions back to the community. I think it could be the start of something really handy for those out there managing large banks of servers... a central configuration repository, key-based or something where you take a freshly installed server, and point it to a config 'key', reboot and poof! That server goes down, simply tell a spare one to use it's config 'key' and reboot - back up and running :) You'd get all the redundancy of LDAP, the organization of a directory tree, and the simplicity of uniform configuration information. This of course with some assumptions about storage and backup situations, but hey - it's an idea not a reality here I'm talking about. Anyways... without digressing way too much, my point was this: if there's enough people interested in the idea, then collaborate and by all means try to make something of it. If it works out well, lots of people start adopting it, THEN we (the FreeBSD community) should look at including it as part of the base... until then, make it as a bundled package or something. I'm using LDAP here for users, groups, email and account information shared to many servers - and it works great, but it's certainly not for everyone and I'd never expect it to come out-of-the box with everything required to do so. Have to weigh the benefits against the costs. This thread keeps arguing the good or the bad points of doing this - and it seems to me not something worth arguing the merits of. If you believe in it enough, then do it or at least try it. Lets move on from if we should or shouldn't, and look more to HOW we could... Just my two and a half cents. -- Nathan Vidican nvidican@wmptl.com Windsor Match Plate & Tool Ltd. http://www.wmptl.com/ From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 11 22:44:23 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9ED3316A403 for ; Thu, 11 Jan 2007 22:44:23 +0000 (UTC) (envelope-from jroberson@chesapeake.net) Received: from webaccess-cl.virtdom.com (webaccess-cl.virtdom.com [216.240.101.25]) by mx1.freebsd.org (Postfix) with ESMTP id 5378413C457 for ; Thu, 11 Jan 2007 22:44:23 +0000 (UTC) (envelope-from jroberson@chesapeake.net) Received: from [10.0.0.1] (216-160-98-154.tukw.qwest.net [216.160.98.154]) (authenticated bits=0) by webaccess-cl.virtdom.com (8.13.6/8.13.6) with ESMTP id l0BMiKXU098553 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO) for ; Thu, 11 Jan 2007 17:44:22 -0500 (EST) (envelope-from jroberson@chesapeake.net) Date: Thu, 11 Jan 2007 14:42:48 -0800 (PST) From: Jeff Roberson X-X-Sender: jroberson@10.0.0.1 To: freebsd-hackers@freebsd.org Message-ID: <20070111144013.C729@10.0.0.1> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Mailman-Approved-At: Fri, 12 Jan 2007 02:03:02 +0000 Subject: Looking for help with schedgraph; phython/tkinter programming. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jan 2007 22:44:23 -0000 I'm looking for someone who might like to help implement new features in schedgraph. This is /usr/src/tools/sched/schedgraph.py. Schedgraph graphs scheduler and system load behavior, sort of like a graphical top. Some example output is here: http://www.chesapeake.net/~jroberson/schedgraph.jpg Some of the features I'd be interested in are: 1) Sortable and mutable thread listings. 2) A seperate per-cpu line that displays which thread is presently running 3) Support for graphing generic counters provided via KTR. 4) Various other stats/cleanup/beautification/etc. Please keep me in the cc list on replies. Any hackers interested? Thanks, Jeff From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 12 02:19:09 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 04F2B16A403 for ; Fri, 12 Jan 2007 02:19:09 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outA.internet-mail-service.net (outA.internet-mail-service.net [216.240.47.224]) by mx1.freebsd.org (Postfix) with ESMTP id DCC6313C468 for ; Fri, 12 Jan 2007 02:19:08 +0000 (UTC) (envelope-from julian@elischer.org) Received: from shell.idiom.com (HELO idiom.com) (216.240.47.20) by out.internet-mail-service.net (qpsmtpd/0.32) with ESMTP; Thu, 11 Jan 2007 18:00:14 -0800 Received: from [10.251.23.190] (nat.ironport.com [63.251.108.100]) by idiom.com (Postfix) with ESMTP id 380DF125AD1; Thu, 11 Jan 2007 18:19:06 -0800 (PST) Message-ID: <45A6F019.5000001@elischer.org> Date: Thu, 11 Jan 2007 18:19:05 -0800 From: Julian Elischer User-Agent: Thunderbird 1.5.0.9 (Macintosh/20061207) MIME-Version: 1.0 To: Jeff Roberson References: <20070111144013.C729@10.0.0.1> In-Reply-To: <20070111144013.C729@10.0.0.1> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Looking for help with schedgraph; phython/tkinter programming. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2007 02:19:09 -0000 Jeff Roberson wrote: > I'm looking for someone who might like to help implement new features in > schedgraph. This is /usr/src/tools/sched/schedgraph.py. Schedgraph > graphs scheduler and system load behavior, sort of like a graphical top. > Some example output is here: > > http://www.chesapeake.net/~jroberson/schedgraph.jpg > > Some of the features I'd be interested in are: > > 1) Sortable and mutable thread listings. > 2) A seperate per-cpu line that displays which thread is presently running I think rwatson had a tool that does that.. > 3) Support for graphing generic counters provided via KTR. > 4) Various other stats/cleanup/beautification/etc. > > Please keep me in the cc list on replies. > > Any hackers interested? > > Thanks, > Jeff > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 12 03:17:13 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6A4F316A504 for ; Fri, 12 Jan 2007 03:17:13 +0000 (UTC) (envelope-from MTaylor@bytecraft.com.au) Received: from bcmelmx.bytecraft.au.com (bcmelmx.bytecraft.au.com [203.39.118.2]) by mx1.freebsd.org (Postfix) with ESMTP id CDD4A13C45E for ; Fri, 12 Jan 2007 03:17:12 +0000 (UTC) (envelope-from MTaylor@bytecraft.com.au) Received: from svmarshal2.bytecraft.internal (svmarshal2.bytecraft.internal [10.0.0.3]) by bcmelmx.bytecraft.au.com (8.12.11/8.12.11) with ESMTP id l0C2juGc081921; Fri, 12 Jan 2007 13:45:56 +1100 (EST) (envelope-from MTaylor@bytecraft.com.au) Received: from svmailmel.bytecraft.internal (Not Verified[10.0.0.24]) by svmarshal2.bytecraft.internal with MailMarshal (v6, 1, 4, 441) id ; Fri, 12 Jan 2007 13:45:56 +1100 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Date: Fri, 12 Jan 2007 13:44:52 +1100 Message-ID: <04E232FDCD9FBE43857F7066CAD3C0F12671F3@svmailmel.bytecraft.internal> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: LDAP integration Thread-Index: Acc17etmee+KQJhrQSSYY5ZvXUmxSAABW9Cw From: "Murray Taylor" To: "Nathan Vidican" , "Mike Meyer" , Cc: Subject: RE: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2007 03:17:13 -0000 =20 > -----Original Message----- > From: owner-freebsd-hackers@freebsd.org=20 > [mailto:owner-freebsd-hackers@freebsd.org] On Behalf Of Nathan Vidican > Sent: Friday, 12 January 2007 5:55 AM > To: Mike Meyer; hackers@freebsd.org > Subject: Re: LDAP integration >=20 > Mike Meyer wrote: > > In <20070111035549.7c11a450@vixen42>, Vulpes Velox=20 > typed: > > =20 > >> LDAP is nice organizing across many systems, but if you are just > >> dealing with one computer it is complete over kill for any thing. > >> =20 > > > > In that situation, it's not merely overkill, it's may actually be a > > bad idea. Can you say "AIX SDR"? How about "Windows registry"? > > > > Those system both took the approach of putting all the configuration > > information in a central database. This creates problems because the > > tools needed to examine/fix the config database require a complex > > environment - at least compared to a statically linked copy of > > ed. LDAP may not be so bad, but it still makes me nervous. > > > > On the other hand, if you've got a flock of boxes to=20 > manage, having a > > way to tell the rc subsystem "Go read config values from this LDAP > > server" seems like a very attractive alternative. > > > > > =20 > Ok, so the general consensus seems to be that it's a good=20 > idea in some=20 > cases and not in others. I myself agree that it should not be part of=20 > the base setup for issues regarding the complication of the base=20 > distribution... but why not make a package for it? >=20 > Take this idea, and run with it... build a package that installs over=20 > the base installation, bundling the LDAP client libs, new rc=20 > structure,=20 > tools, etc all in one shot. Add it to the ports collection=20 > and call it=20 > done. - After all that's the wonder that is opensource... if=20 > ya want to=20 > improve something, go for it - even better if you can contribute your=20 > additions back to the community. >=20 > I think it could be the start of something really handy for those out=20 > there managing large banks of servers... a central configuration=20 > repository, key-based or something where you take a freshly installed=20 > server, and point it to a config 'key', reboot and poof! That server=20 > goes down, simply tell a spare one to use it's config 'key'=20 > and reboot -=20 > back up and running :) You'd get all the redundancy of LDAP, the=20 > organization of a directory tree, and the simplicity of uniform=20 > configuration information. This of course with some assumptions about=20 > storage and backup situations, but hey - it's an idea not a=20 > reality here=20 > I'm talking about. >=20 > Anyways... without digressing way too much, my point was this: if=20 > there's enough people interested in the idea, then collaborate and by=20 > all means try to make something of it. If it works out well, lots of=20 > people start adopting it, THEN we (the FreeBSD community)=20 > should look at=20 > including it as part of the base... until then, make it as a bundled=20 > package or something. I'm using LDAP here for users, groups,=20 > email and=20 > account information shared to many servers - and it works great, but=20 > it's certainly not for everyone and I'd never expect it to come=20 > out-of-the box with everything required to do so. Have to weigh the=20 > benefits against the costs. >=20 > This thread keeps arguing the good or the bad points of doing=20 > this - and=20 > it seems to me not something worth arguing the merits of. If=20 > you believe=20 > in it enough, then do it or at least try it. Lets move on from if we=20 > should or shouldn't, and look more to HOW we could... >=20 > Just my two and a half cents. >=20 >=20 > -- > Nathan Vidican > nvidican@wmptl.com > Windsor Match Plate & Tool Ltd. > http://www.wmptl.com/ I would be in favour of this being put together asa port.. says he looking into the future where a multi server /=20 multi service 'system' is lurking. Might be nice for configuring blade server arrays too. mjt Murray Taylor Special Projects Engineer Bytecraft Systems E: mtaylor@bytecraft.com.au=20 -- "Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction." --Albert Einstein=20 --------------------------------------------------------------- The information transmitted in this e-mail is for the exclusive use of the intended addressee and may contain confidential and/or privileged material. Any review, re-transmission, dissemination or other use of it, or the taking of any action in reliance upon this information by persons and/or entities other than the intended recipient is prohibited. If you received this in error, please inform the sender and/or addressee immediately and delete the material.=20 E-mails may not be secure, may contain computer viruses and may be corrupted in transmission. Please carefully check this e-mail (and any attachment) accordingly. No warranties are given and no liability is accepted for any loss or damage caused by such matters. --------------------------------------------------------------- ### This e-mail message has been scanned for Viruses by Bytecraft ### From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 12 06:47:46 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A340B16A403 for ; Fri, 12 Jan 2007 06:47:46 +0000 (UTC) (envelope-from ssouhlal@FreeBSD.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 937F913C45A for ; Fri, 12 Jan 2007 06:47:46 +0000 (UTC) (envelope-from ssouhlal@FreeBSD.org) Received: from [192.168.0.100] (c-67-188-127-3.hsd1.ca.comcast.net [67.188.127.3]) by elvis.mu.org (Postfix) with ESMTP id 69CD91A3C1A; Thu, 11 Jan 2007 22:47:46 -0800 (PST) Message-ID: <45A72ED8.8070402@FreeBSD.org> Date: Thu, 11 Jan 2007 22:46:48 -0800 From: Suleiman Souhlal User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051204) X-Accept-Language: en-us, en MIME-Version: 1.0 To: darran kartaschew References: <20070110012250.HM.0000000000000G0@chewy509.bos-mail-wwl8.lycos.com> In-Reply-To: <20070110012250.HM.0000000000000G0@chewy509.bos-mail-wwl8.lycos.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: sbrk vs mmap X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2007 06:47:46 -0000 darran kartaschew wrote: > Hi Guys, > I'm having some issues with rewriting a simple malloc() function to be > with FreeBSD (AMD64). This is part of porting an application from > Linux > to FreeBSD. > After pulling my hair out for a while, I've found that the sbrk() > system call just returns "45 - Operation Not Supported" error, > irrespective of the parameters passed to it. (I've found the source > for sbrk() and see that it's not implemented). > So I decided to try using mmap() instead. All memory allocations don't > have to be continuous, so mmap() will suffice. The problem is I'm > getting an invalid file handle error? According to the man page, if > you > use MAP_ANON you're just allocating a block of memory without linking > to a file, and a handle of -1 should be supplied... Any way code is as > follows: > memInit: > mov r4, 0 ; don't care where the memory is allocated > mov r5, 1048576 ; alloc 1MB > mov r3, 3 ; RW access to memory > mov r2, 4096 ; MAP_ANON - not a file > mov r8d, -1 ; -1 for file handle if using MAP_ANON > mov r9, 0 ; ignored for MAP_ANON > mov r0, 197 ; mmap(); > syscall > mov qword [_mmap], r0 ; save address so we can release it on exit; > ret > It fails with an EBADF (9) ; Bad File Descriptor error... > Note: r0 = rax, r1 = rbx, r2 = rcx, r3 = rdx, r4 = rdi, r5 = rsi, r6 = > rbp, r7 = rsp. Various parameters for mmap() are found in mman.h>. > So does anyone have an example of a working call to mmap() or tell me > what's wrong with the above code? > I've done up a test C program that simple calls mmap(), after > tracing through the compiled C program using gdb I can't see that > I'm doing anything different to what gcc/glibc are doing? (except > the macro expansion that's in libc which adds an additional > 0 to the top of the stack). > PS. FASM 1.66 running on FreeBSD 6.1 (AMD64). > PPS. This is NOT a homework assignment! (tm) :P I think you are missing a parameter. mmap (as well as pwrite, lseek, truncate and ftruncate), has a "hidden" parameter just before the offset that is ignored, due to a bug in ancient GCC versions. So, basically, you should also push a 0 on the stack. Take a look at src/sys/libc/sys/mmap.c . I have a patch to remove this useless argument, but haven't committed it yet. -- Suleiman From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 12 10:35:57 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D05AC16A554 for ; Fri, 12 Jan 2007 10:35:57 +0000 (UTC) (envelope-from bra@fsn.hu) Received: from people.fsn.hu (people.fsn.hu [195.228.252.137]) by mx1.freebsd.org (Postfix) with ESMTP id 8FDCF13C469 for ; Fri, 12 Jan 2007 10:35:57 +0000 (UTC) (envelope-from bra@fsn.hu) Received: from localhost (localhost [127.0.0.1]) by people.fsn.hu (Postfix) with ESMTP id D46CE84423; Fri, 12 Jan 2007 11:35:55 +0100 (CET) Received: from people.fsn.hu ([127.0.0.1]) by localhost (people.fsn.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 43713-04; Fri, 12 Jan 2007 11:35:50 +0100 (CET) Received: from [IPv6:::1] (unknown [192.168.2.3]) by people.fsn.hu (Postfix) with ESMTP id 56C6D84420; Fri, 12 Jan 2007 11:35:50 +0100 (CET) Message-ID: <45A76480.6010108@fsn.hu> Date: Fri, 12 Jan 2007 11:35:44 +0100 From: Attila Nagy User-Agent: Thunderbird 1.5.0.9 (X11/20061221) MIME-Version: 1.0 To: Kris Kennaway References: <45A0229F.7070701@fsn.hu> <45a03a95.08FguubdCa9DFcxj%perryh@pluto.rain.com> <45A0DD27.4020704@fsn.hu> <20070111010149.GA2704@xor.obsecurity.org> In-Reply-To: <20070111010149.GA2704@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at fsn.hu Cc: freebsd-hackers@freebsd.org, perryh@pluto.rain.com Subject: Re: ufs_rename: fvp == tvp (can't happen), but it did X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2007 10:35:57 -0000 On 01/11/07 02:01, Kris Kennaway wrote: > On Sun, Jan 07, 2007 at 12:44:39PM +0100, Attila Nagy wrote: > >> On 2007.01.07. 1:11, perryh@pluto.rain.com wrote: >> >>> It sounds as if the caller of ufs_rename() is confused. You could >>> try setting a breakpoint on the printf(), or change it to a panic() >>> to get a dump, and try to figure out who the caller is and what is >>> going on. >>> >>> >> Yes this would be very good, especially if this wouldn't be a production >> machine or if I could reproduce this on a test system. But neither of >> this are true. :( >> >> Maybe I will try it on a sleepless night, in the maintenance window, >> thanks for the idea. >> > > Try forcing a fsck, sometimes bizarre FS panics are due to filesystem > corruption. > I've already thought of that, but in that case the FC array must be bad, since going with only the locally attached disks in the mirror, the error doesn't appear... -- Attila Nagy e-mail: Attila.Nagy@fsn.hu Free Software Network (FSN.HU) phone: +3630 306 6758 http://www.fsn.hu/ From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 12 14:37:41 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DD7CD16A50B for ; Fri, 12 Jan 2007 14:37:41 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe09.swip.net [212.247.155.1]) by mx1.freebsd.org (Postfix) with ESMTP id 7A5BC13C45E for ; Fri, 12 Jan 2007 14:37:41 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] Received: from [193.217.102.48] (account mc467741@c2i.net HELO [10.0.0.249]) by mailfe09.swip.net (CommuniGate Pro SMTP 5.0.12) with ESMTPA id 211859336 for freebsd-hackers@freebsd.org; Fri, 12 Jan 2007 14:37:34 +0100 From: Hans Petter Selasky To: freebsd-hackers@freebsd.org Date: Fri, 12 Jan 2007 14:37:09 +0100 User-Agent: KMail/1.7 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200701121437.10273.hselasky@c2i.net> Subject: mii_bus problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2007 14:37:41 -0000 Hi, Can someone here explain from where I can call "mii_pollstat()". I read somewhere on the internet that I cannot call this function from the so called "tick" routine, where "mii_tick()" is called. I currently have the following code: static void aue_cfg_tick(struct aue_softc *sc, struct aue_config_copy *cc, u_int16_t refcount) { printf("%s:%d\n", __FUNCTION__, __LINE__); struct ifnet * ifp = sc->sc_ifp; struct mii_data * mii = GET_MII(sc); if ((cc == NULL) || (ifp == NULL) || (mii == NULL)) { /* not ready */ return; } mii_tick(mii); mii_pollstat(mii); if ((sc->sc_flags & AUE_FLAG_WAIT_LINK) && (mii->mii_media_status & IFM_ACTIVE) && (IFM_SUBTYPE(mii->mii_media_active) != IFM_NONE)) { sc->sc_flags &= ~AUE_FLAG_WAIT_LINK; } sc->sc_media_active = mii->mii_media_active; sc->sc_media_status = mii->mii_media_status; /* start stopped transfers, if any */ aue_start_transfers(sc); return; } But after this function returns, the kernel corrupts, and it pagefaults in the "swi6 taskqueue". Commenting out "mii_pollstat()" fixes the kernel panic. My ifmedia status callback looks like this: static void aue_ifmedia_sts_cb(struct ifnet *ifp, struct ifmediareq *ifmr) { printf("%s:%d\n", __FUNCTION__, __LINE__); struct aue_softc *sc = ifp->if_softc; mtx_lock(&(sc->sc_mtx)); //mii_pollstat(mii); I don't want this here hence it sleeps! ifmr->ifm_active = sc->sc_media_active; ifmr->ifm_status = sc->sc_media_status; mtx_unlock(&(sc->sc_mtx)); return; } The question is, is it at all possible to poll the MII status outside the ifmedia status callback ? And if yes, how? Thanks --HPS From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 12 15:40:20 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A5C2216A416 for ; Fri, 12 Jan 2007 15:40:20 +0000 (UTC) (envelope-from doublef-ctm@yandex.ru) Received: from smtp2.yandex.ru (smtp2.yandex.ru [213.180.200.18]) by mx1.freebsd.org (Postfix) with ESMTP id EBAED13C448 for ; Fri, 12 Jan 2007 15:40:19 +0000 (UTC) (envelope-from doublef-ctm@yandex.ru) Received: from [85.172.94.221] ([85.172.94.221]:14276 "EHLO shark" smtp-auth: "doublef-ctm" TLS-CIPHER: TLS-PEER-CN1: ) by mail.yandex.ru with ESMTP id S3375862AbXALPYG (ORCPT ); Fri, 12 Jan 2007 18:24:06 +0300 X-Comment: RFC 2476 MSA function at smtp2.yandex.ru logged sender identity as: doublef-ctm Received: by shark (Postfix, from userid 1000) id 6A5B41776B; Fri, 12 Jan 2007 18:24:03 +0300 (MSK) Date: Fri, 12 Jan 2007 18:24:03 +0300 From: Sergey Zaharchenko To: Eugene Grosbein Message-ID: <20070112152403.GA2336@shark.localdomain> Mail-Followup-To: Sergey Zaharchenko , Eugene Grosbein , Kostik Belousov , freebsd-hackers@freebsd.org References: <200701031601.05541.jhb@freebsd.org> <20070104040727.GD21325@deviant.kiev.zoral.com.ua> <20070104103708.GF21325@deviant.kiev.zoral.com.ua> <20070104105208.GA78979@svzserv.kemerovo.su> <20070104110208.GG21325@deviant.kiev.zoral.com.ua> <20070104114327.GA81011@svzserv.kemerovo.su> <20070104114849.GH21325@deviant.kiev.zoral.com.ua> <20070104120603.GA84934@svzserv.kemerovo.su> <20070104121245.GI21325@deviant.kiev.zoral.com.ua> <20070104181146.GA90801@svzserv.kemerovo.su> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BOKacYhQ+x31HxR3" Content-Disposition: inline In-Reply-To: <20070104181146.GA90801@svzserv.kemerovo.su> X-Listening-To: Silence User-Agent: Mutt/1.5.11 Cc: Kostik Belousov , freebsd-hackers@freebsd.org Subject: nVidia driver (Was: Re: WITNESS & RELENG_6) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2007 15:40:20 -0000 --BOKacYhQ+x31HxR3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hello, Eugene! Fri, Jan 05, 2007 at 01:11:46AM +0700 you wrote: > On Thu, Jan 04, 2007 at 02:12:45PM +0200, Kostik Belousov wrote: > > > mplayer hangs hard the whole system in the moment it switches to full-screen. > > > > When hangs, does it answer ping/allow ssh connections ? > > > Can't check just now, but can establish serial console if you wish. > > It would be better to check this in both cases (mplayer and return to vty). > I've established ethernet and serial links with this box and checked. > In both cases this is X server locked in "devdrn" state. > All other processes and the kernel run just fine. FWIW I have just came across the same with recent -CURRENT after updating the nvidia driver (8*** worked all right). Any mode switch (like Ctrl Alt +/-, vty switch, etc.) puts Xorg into devdrn (with all other processes working fine) and a while later the machine reboots (without dumping core). -- DoubleF No virus detected in this message. Ehrm, wait a minute... /kernel: pid 56921 (antivirus), uid 32000: exited on signal 9 Oh yes, no virus:) --BOKacYhQ+x31HxR3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.1 (FreeBSD) iD8DBQFFp6gSwo7hT/9lVdwRAistAJ4rYIR4hqd/CETL+hvYkAX6iWVVqQCggcGe +9ivCTEGnEC/2uXiG+D0SH4= =XH4s -----END PGP SIGNATURE----- --BOKacYhQ+x31HxR3-- From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 12 16:08:54 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 50AB116A407 for ; Fri, 12 Jan 2007 16:08:54 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.187]) by mx1.freebsd.org (Postfix) with ESMTP id DC36613C428 for ; Fri, 12 Jan 2007 16:08:53 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: by nf-out-0910.google.com with SMTP id k27so1236916nfc for ; Fri, 12 Jan 2007 08:08:52 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding; b=GMin57ytAlFiia9yHt7AecNijFulaF24Ra6+XbsBIQcCFplX+/zz5bpOQlsd/+mO1mbgzqrQxZj6dXaHmmNUeOcQW05ueZ9lCixx8UuEJD2W6VFErdyNYUwVNchNVhlLqFmNhLaonbHhty2XyT93cFpQJwqzEEoGvH+ezD3llUo= Received: by 10.48.48.18 with SMTP id v18mr601413nfv.1168618132603; Fri, 12 Jan 2007 08:08:52 -0800 (PST) Received: from ?192.168.123.202? ( [195.241.221.201]) by mx.google.com with ESMTP id v20sm10739379nfc.2007.01.12.08.08.50; Fri, 12 Jan 2007 08:08:51 -0800 (PST) Message-ID: <45A7B291.9040405@gmail.com> Date: Fri, 12 Jan 2007 17:08:49 +0100 From: Rene Ladan User-Agent: Thunderbird 1.5.0.9 (X11/20061224) MIME-Version: 1.0 To: pyunyh@gmail.com References: <45A61C1A.3090600@gmail.com> <20070111122049.GE33964@cdnetworks.co.kr> <45A659A1.2060401@gmail.com> <20070112020149.GA42529@cdnetworks.co.kr> In-Reply-To: <20070112020149.GA42529@cdnetworks.co.kr> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, Pietro Cerutti Subject: Re: re(4) incorrect checksum X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2007 16:08:54 -0000 Pyun YongHyeon schreef: > On Thu, Jan 11, 2007 at 04:37:05PM +0100, Rene Ladan wrote: > > Pyun YongHyeon schreef: > > > On Thu, Jan 11, 2007 at 12:14:34PM +0100, Rene Ladan wrote: > > > > Pietro Cerutti schreef: > > > > > Hi lists, > > > > > [..] > > > > > re0: port 0xc800-0xc8ff > > > > > mem 0xff2ff000-0xff2fffff irq 17 at device 0.0 on pci2 > > > > > > > > > > ($FreeBSD: src/sys/dev/re/if_re.c,v 1.46.2.20 2006/09/21 11:08:28 > > > > > yongari Exp $) > > > > > > > > > > I get checksum errors on every packet I send, example: > > > > > > > > > > Checksum: 0x0bc5 [incorrect, should be 0x78fe (maybe caused by > > > > > checksum offloading?)] > > > > > > > > > > I think this could be the cause of some web pages (e.g. Gmail in > > > > > standard view [html view works well]) not to be displayed. > > > > > > > > > > I tracked down the problem to the re(4) driver just because wlan works > > > > > good... > > > > > > > > > > Any ideas? > > > > > > > > > I'm also seeing these www problems with my re(4) card (chipid > > > > 0x816810ec), see > > > > http://lists.freebsd.org/pipermail/freebsd-current/2006-December/068333.html > > > > > > > > > > Does your re(4) also work when you disable checksum offload? > > > > > Yes, 'ifconfig re0 -txcsum' does the trick. > > > > re0: port 0xc800-0xc8ff mem > > 0xfe0ff000-0xfe0fffff irq 16 at device 0.0 on pci2 > > > > if.re.c revision 1.80 2006/12/20 02:13:59 marius > > > > I've never encountered checksum offload issue after wpaul's fix. > How about attached one? It's just vague guess but please give it > try and let me know the result. > The patch doesn't work :( I still need to pass -txcsum (or go wireless using wpi(4) :) ) -- GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) "It won't fit on the line." -- me, 2001 From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 12 16:36:36 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7903016A407 for ; Fri, 12 Jan 2007 16:36:36 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: from kiwi-computer.com (keira.kiwi-computer.com [63.224.10.3]) by mx1.freebsd.org (Postfix) with SMTP id 04F5813C45D for ; Fri, 12 Jan 2007 16:36:35 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: (qmail 82722 invoked by uid 2001); 12 Jan 2007 16:09:54 -0000 Date: Fri, 12 Jan 2007 10:09:54 -0600 From: "Rick C. Petty" To: Nathan Vidican Message-ID: <20070112160954.GA82541@keira.kiwi-computer.com> References: <60737.24.71.119.183.1168496463.squirrel@webmail.sd73.bc.ca> <45A5EA3B.9020000@datalinktech.com.au> <20070111035549.7c11a450@vixen42> <17830.29050.791321.480369@bhuda.mired.org> <45A687F6.2020907@vidican.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45A687F6.2020907@vidican.com> User-Agent: Mutt/1.4.2.1i Cc: hackers@freebsd.org Subject: Re: LDAP integration X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rick-freebsd@kiwi-computer.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2007 16:36:36 -0000 On Thu, Jan 11, 2007 at 01:54:46PM -0500, Nathan Vidican wrote: > > Take this idea, and run with it... build a package that installs over > the base installation, bundling the LDAP client libs, new rc structure, > tools, etc all in one shot. Add it to the ports collection and call it > done. I don't like the idea of any ports installing themselves over the base installation. If you do a "make installworld", you'll wipe the port, and a portupgrade will wipe out the base.. We have /usr/local/ for a reason. Having a port install the same libraries as the base is already problematic enough (look at security/heimdal), but at least the separation is manageable. -- Rick C. Petty From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 12 19:25:19 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9A1ED16A403 for ; Fri, 12 Jan 2007 19:25:19 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.freebsd.org (Postfix) with ESMTP id 0FA7313C455 for ; Fri, 12 Jan 2007 19:25:19 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 778DD4880F; Fri, 12 Jan 2007 20:07:31 +0100 (CET) Received: from localhost (154.81.datacomsa.pl [195.34.81.154]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 0190E487F0; Fri, 12 Jan 2007 20:07:26 +0100 (CET) Date: Fri, 12 Jan 2007 20:06:55 +0100 From: Pawel Jakub Dawidek To: Attila Nagy Message-ID: <20070112190655.GC90718@garage.freebsd.pl> References: <45A0229F.7070701@fsn.hu> <45a03a95.08FguubdCa9DFcxj%perryh@pluto.rain.com> <45A0DD27.4020704@fsn.hu> <20070111010149.GA2704@xor.obsecurity.org> <45A76480.6010108@fsn.hu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="E/DnYTRukya0zdZ1" Content-Disposition: inline In-Reply-To: <45A76480.6010108@fsn.hu> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-hackers@freebsd.org, perryh@pluto.rain.com, Kris Kennaway Subject: Re: ufs_rename: fvp == tvp (can't happen), but it did X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2007 19:25:19 -0000 --E/DnYTRukya0zdZ1 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 12, 2007 at 11:35:44AM +0100, Attila Nagy wrote: > On 01/11/07 02:01, Kris Kennaway wrote: > >On Sun, Jan 07, 2007 at 12:44:39PM +0100, Attila Nagy wrote: > > =20 > >>On 2007.01.07. 1:11, perryh@pluto.rain.com wrote: > >> =20 > >>>It sounds as if the caller of ufs_rename() is confused. You could > >>>try setting a breakpoint on the printf(), or change it to a panic() > >>>to get a dump, and try to figure out who the caller is and what is > >>>going on. > >>> =20 > >>Yes this would be very good, especially if this wouldn't be a productio= n machine or if I could reproduce this on a test system. But neither of thi= s are true. :( > >> > >>Maybe I will try it on a sleepless night, in the maintenance window, th= anks for the idea. > >> =20 > > > >Try forcing a fsck, sometimes bizarre FS panics are due to filesystem > >corruption. > > =20 > I've already thought of that, but in that case the FC array must be bad, = since going with only the locally attached disks in the mirror, the error d= oesn't appear... Silent data corruptions happens, look for example at the "problem with 4T volume under FreeBSD" thread on current@. I'd suggest configuring geli with data authentication on top of the FC array. geli will detect silent data corruptions. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --E/DnYTRukya0zdZ1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFp9xPForvXbEpPzQRAucgAJ4k20fCH3iZ50KOs9sECeStVzGxFgCgvRe4 KaTie0JyuHSyW9W+Yi5HAdE= =EeCD -----END PGP SIGNATURE----- --E/DnYTRukya0zdZ1-- From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 12 19:25:19 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B646616A47B; Fri, 12 Jan 2007 19:25:19 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.freebsd.org (Postfix) with ESMTP id 2A6EA13C461; Fri, 12 Jan 2007 19:25:19 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 5161948808; Fri, 12 Jan 2007 20:03:27 +0100 (CET) Received: from localhost (154.81.datacomsa.pl [195.34.81.154]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id C7EE6487F0; Fri, 12 Jan 2007 20:03:20 +0100 (CET) Date: Fri, 12 Jan 2007 20:02:49 +0100 From: Pawel Jakub Dawidek To: Danny Braniss Message-ID: <20070112190249.GB90718@garage.freebsd.pl> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="s/l3CgOIzMHHjg/5" Content-Disposition: inline In-Reply-To: X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-scsi@FreeBSD.org, freebsd-hackers@freebsd.org Subject: Re: iSCSI disconnects dilema X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2007 19:25:19 -0000 --s/l3CgOIzMHHjg/5 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jan 09, 2007 at 09:06:46AM +0200, Danny Braniss wrote: > Hi, > While I think I have almost solved the problem of network disconnects, > It downed on me a major problem: > When a 'local' disk crashes, the kernel will probably hang/panic/crash. > if i don't try to recover, then there is no change in the above scenario. > if i try to recover, then the client does not know that it should > umount/fsck/mount. > While all this seems familiar, removing a floppy/disk-on-key while it's > mounted, we could always say "you shouldn't have done that!", with > a network connection, it can happen very often - rebooting the target, a > network hickup, etc. >=20 > So, any ideas? In my opinion it should be done this way: You have a queue of I/O requests. You send the to the other end and wait for confirmation. Until confirmation is received, you keep the requests queued. If the other end dies, you try to reconnect (until some timeout expires, the processes which send those requests will just wait), if you reconnect successfully, you resend not-confirmed requests, if you won't be able to reconnect, you just pass the errors up. This is what I did in ggate and it seems to work. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --s/l3CgOIzMHHjg/5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFp9tZForvXbEpPzQRAv4EAKD3CxdlCygVo4AgET/J5bD8XZM4dgCgpmCV FUgOAZDi82SVgQSFXu+PqTY= =BHwP -----END PGP SIGNATURE----- --s/l3CgOIzMHHjg/5-- From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 12 19:25:19 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CA9C216A47C for ; Fri, 12 Jan 2007 19:25:19 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.freebsd.org (Postfix) with ESMTP id 0F91013C44C for ; Fri, 12 Jan 2007 19:25:19 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id CCC6948805; Fri, 12 Jan 2007 19:57:59 +0100 (CET) Received: from localhost (154.81.datacomsa.pl [195.34.81.154]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 99A1A487F0; Fri, 12 Jan 2007 19:57:53 +0100 (CET) Date: Fri, 12 Jan 2007 19:57:22 +0100 From: Pawel Jakub Dawidek To: John Nielsen Message-ID: <20070112185722.GA90718@garage.freebsd.pl> References: <200701102321.01562.lists@jnielsen.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2fHTh5uZTiUOsy+g" Content-Disposition: inline In-Reply-To: <200701102321.01562.lists@jnielsen.net> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-hackers@freebsd.org Subject: Re: Best practices for using gjournal with gmirror? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2007 19:25:19 -0000 --2fHTh5uZTiUOsy+g Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 10, 2007 at 11:21:01PM -0500, John Nielsen wrote: > I have a few questions for pjd (or anyone else) about using gjournal,=20 > particularly when used with gmirror. >=20 > 1) I'm running 6-STABLE and plan to test with gjournal6_20061030.patch (f= rom=20 > the mailing list; updated version of 20061024 that applies cleanly). Is= =20 > there a better/newer version for -STABLE that I should use instead? There probably should be a newer version as there were some minor changes after I committed the code to HEAD. I'll try to create a new patch during the weekend. > 2) When using gjournal and for a gmirror volume, does the journal need to= be=20 > mirrored as well to maintain redundancy? If so, when storing the journal = on=20 > the same physical disks as the mirror, is it better to mirror at the slic= e=20 > level (journal and fs on different partitions in the same mirror) or at t= he=20 > partition level (journal and fs each have their own mirror) or does it=20 > matter? The problem with mirroring each partition/slice separately is that when you have a crash, on boot, gmirror will start to rebuild all partitions at once, which may be problematic. On the other hand, when you mirror each partition/slice separately, and some partitions weren't modified in last few seconds before the crash, gmirror will not resync them on boot, so not entire disk will be synchronized. When you run gjournal on top of gmirror/graid3 there is no need for resync after a crash, so bascially all cons against mirroring the whole disks and against mirroring partitions are no longer true. Both configurations will work the same. In that case I'd suggest mirroring the whole disks, because when one of your disks dies, you may just replace it and be down with it. If you mirror partitions separately, you first have to create partitions and insert each of them into their mirrors, which is more complex than simple 'gmirror insert foo newdisk'. > 3) I remember reading where pjd said that gjournal plus gmirror or graid3= =20 > would eliminate the need to re-sync the array after a crash. While clearl= y=20 > a design goal, is that actually the case with the version of the patch=20 > mentioned above? If so, are any config changes needed or will it just=20 > happen automagically? No, you need to: # gmirror configure -F > 4) In the same vein as 3)--does a gjournal volume need to be fsck'ed afte= r a=20 > crash? If not, will it just work (e.g. fsck -p sees that the filesystem i= s=20 > clean) or does it need to be disabled somehow? Gjournaled file system has to be fscked, but only to handle orphaned files. Such fsck on multiterabyte provider takes seconds, not hours. > 5) Finally, how dangerous is this code? I realize it's experimental and o= nly=20 > plan to use it with data that has recent backups, but how much should I= =20 > worry about it blowing up my system or corrupting my files? I'm using it in production, my customer using it in production on large number of FreeBSD servers and I also have heard already many success stories, BUT I still consider the code to be experimental. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --2fHTh5uZTiUOsy+g Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFp9oSForvXbEpPzQRAv89AJ4u9p5zh+63oPL2yUJ9lCTAtId/GgCg0MQd 2wZV3Qy5cK7UjiDtCz9wcNs= =M3O6 -----END PGP SIGNATURE----- --2fHTh5uZTiUOsy+g-- From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 12 19:31:06 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D6FB016A47E; Fri, 12 Jan 2007 19:31:06 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.freebsd.org (Postfix) with ESMTP id 90A3713C480; Fri, 12 Jan 2007 19:31:06 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1H5S7E-000BS0-RR; Fri, 12 Jan 2007 21:31:04 +0200 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Pawel Jakub Dawidek In-reply-to: Your message of Fri, 12 Jan 2007 20:02:49 +0100 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 12 Jan 2007 21:31:04 +0200 From: Danny Braniss Message-ID: Cc: freebsd-scsi@FreeBSD.org, freebsd-hackers@freebsd.org Subject: Re: iSCSI disconnects dilema X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2007 19:31:06 -0000 > > --s/l3CgOIzMHHjg/5 > Content-Type: text/plain; charset=iso-8859-2 > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > On Tue, Jan 09, 2007 at 09:06:46AM +0200, Danny Braniss wrote: > > Hi, > > While I think I have almost solved the problem of network disconnects, > > It downed on me a major problem: > > When a 'local' disk crashes, the kernel will probably hang/panic/crash. > > if i don't try to recover, then there is no change in the above scenario. > > if i try to recover, then the client does not know that it should > > umount/fsck/mount. > > While all this seems familiar, removing a floppy/disk-on-key while it's > > mounted, we could always say "you shouldn't have done that!", with > > a network connection, it can happen very often - rebooting the target, a > > network hickup, etc. > >=20 > > So, any ideas? > > In my opinion it should be done this way: > > You have a queue of I/O requests. You send the to the other end and wait > for confirmation. Until confirmation is received, you keep the requests > queued. If the other end dies, you try to reconnect (until some timeout > expires, the processes which send those requests will just wait), if you > reconnect successfully, you resend not-confirmed requests, if you won't > be able to reconnect, you just pass the errors up. > > This is what I did in ggate and it seems to work. That is basically what i'm doing - unacked request get requed. the problem I fear (and maybe I'm paranoid :-): assume the following scenario, the client(initiator) sends a write command, the target acks it, then it crashes, if the write was never completed, the initiator goes on as nothing ever happened. danny From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 12 20:14:12 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 09EC516A415; Fri, 12 Jan 2007 20:14:12 +0000 (UTC) (envelope-from wb@freebie.xs4all.nl) Received: from smtp-vbr16.xs4all.nl (smtp-vbr16.xs4all.nl [194.109.24.36]) by mx1.freebsd.org (Postfix) with ESMTP id 9654413C474; Fri, 12 Jan 2007 20:14:11 +0000 (UTC) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp-vbr16.xs4all.nl (8.13.8/8.13.8) with ESMTP id l0CJtow6022924; Fri, 12 Jan 2007 20:55:51 +0100 (CET) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.13.8/8.13.3) with ESMTP id l0CJtoGl077324; Fri, 12 Jan 2007 20:55:50 +0100 (CET) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.13.8/8.13.6/Submit) id l0CJto9I077323; Fri, 12 Jan 2007 20:55:50 +0100 (CET) (envelope-from wb) Date: Fri, 12 Jan 2007 20:55:50 +0100 From: Wilko Bulte To: Danny Braniss Message-ID: <20070112195549.GA77181@freebie.xs4all.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-scsi@freebsd.org, Pawel Jakub Dawidek , freebsd-hackers@freebsd.org Subject: Re: iSCSI disconnects dilema X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2007 20:14:12 -0000 On Fri, Jan 12, 2007 at 09:31:04PM +0200, Danny Braniss wrote.. > > > > --s/l3CgOIzMHHjg/5 > > Content-Type: text/plain; charset=iso-8859-2 > > Content-Disposition: inline > > Content-Transfer-Encoding: quoted-printable > > > > On Tue, Jan 09, 2007 at 09:06:46AM +0200, Danny Braniss wrote: > > > Hi, > > > While I think I have almost solved the problem of network disconnects, > > > It downed on me a major problem: > > > When a 'local' disk crashes, the kernel will probably hang/panic/crash. > > > if i don't try to recover, then there is no change in the above scenario. > > > if i try to recover, then the client does not know that it should > > > umount/fsck/mount. > > > While all this seems familiar, removing a floppy/disk-on-key while it's > > > mounted, we could always say "you shouldn't have done that!", with > > > a network connection, it can happen very often - rebooting the target, a > > > network hickup, etc. > > >=20 > > > So, any ideas? > > > > In my opinion it should be done this way: > > > > You have a queue of I/O requests. You send the to the other end and wait > > for confirmation. Until confirmation is received, you keep the requests > > queued. If the other end dies, you try to reconnect (until some timeout > > expires, the processes which send those requests will just wait), if you > > reconnect successfully, you resend not-confirmed requests, if you won't > > be able to reconnect, you just pass the errors up. > > > > This is what I did in ggate and it seems to work. > > That is basically what i'm doing - unacked request get requed. > the problem I fear (and maybe I'm paranoid :-): Paranoia is a Good Thing(TM) in data storage land :-) > assume the following scenario, the client(initiator) sends a write command, > the target acks it, then it crashes, if the write was never completed, > the initiator goes on as nothing ever happened. Yes, but what can the initiator do about that? I mean, it does not have any visibility of what the target has (or has not) done with the data. ' This is roughly the same as a RAID box accepting a write into a writeback cache and ACK-ing to the host. You can only assume that the RAID box' cache will get flushed to the spindles properly. All the usual horror scenarios with a broken battery backup of the cache and a powerfailure etc apply here. Wilko -- Wilko Bulte wilko@FreeBSD.org From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 12 21:43:22 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1CA0516A40F for ; Fri, 12 Jan 2007 21:43:22 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by mx1.freebsd.org (Postfix) with SMTP id 6A8F013C467 for ; Fri, 12 Jan 2007 21:43:21 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 1748 invoked by uid 399); 12 Jan 2007 21:43:20 -0000 Received: from localhost (HELO ?192.168.0.5?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 12 Jan 2007 21:43:20 -0000 X-Originating-IP: 127.0.0.1 Message-ID: <45A800F4.20504@FreeBSD.org> Date: Fri, 12 Jan 2007 13:43:16 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: jgrosch@MooseRiver.com References: <20070111170424.GA85484@mooseriver.com> In-Reply-To: <20070111170424.GA85484@mooseriver.com> X-Enigmail-Version: 0.94.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Getting a patch commited X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2007 21:43:22 -0000 Josef Grosch wrote: > I know everyone is busy with getting 6.2 out the door but could someone > commit the patch at conf/107453 ? You generally get a better response to requests like this if you: 1. Mention briefly what the patch is about. 2. Include the URL to the PR 3. cc the responsible person for the PR hth, Doug -- This .signature sanitized for your protection From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 12 22:25:31 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1F0C916A403 for ; Fri, 12 Jan 2007 22:25:31 +0000 (UTC) (envelope-from deuza42@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.191]) by mx1.freebsd.org (Postfix) with ESMTP id AC06013C43E for ; Fri, 12 Jan 2007 22:25:30 +0000 (UTC) (envelope-from deuza42@gmail.com) Received: by nf-out-0910.google.com with SMTP id k27so1321835nfc for ; Fri, 12 Jan 2007 14:25:29 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=OiXB+a3AFJiKX1HLnkJg9LcjNJfan0GXoqDhCZTdXqHP34GG4uDaqEtc+7wMxk6hYp7ISSX9Q/YW/If2rjbchUludnAXhxIMYpQXSVLXkPwL0WJPT+xufXR0TF1HoV+yQq1MlJNOoxtc5wR5TcybtItD50esCuPk3b5AJm8KJhU= Received: by 10.82.169.4 with SMTP id r4mr222742bue.1168639009057; Fri, 12 Jan 2007 13:56:49 -0800 (PST) Received: by 10.82.183.13 with HTTP; Fri, 12 Jan 2007 13:56:48 -0800 (PST) Message-ID: Date: Fri, 12 Jan 2007 22:56:49 +0100 From: DeuZa To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: ATKBD_DFLT_KEYMAP kernel's options ??? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2007 22:25:31 -0000 Hello everybody, On my "old" box (5-STABLE from 4 March) this kernel's options works fine : options ATKBD_DFLT_KEYMAP # Gestion du clavier FR makeoptions ATKBD_DFLT_KEYMAP=fr.iso.acc But on my new p4 (6-STABLE, sources tonight) this doesn't work :/ Without error, and the options appears always in the LINT file ... Are you any ideas please ? Best regards Alain From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 12 22:53:07 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1B87816A403 for ; Fri, 12 Jan 2007 22:53:07 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.freebsd.org (Postfix) with SMTP id 7613013C458 for ; Fri, 12 Jan 2007 22:53:05 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie ([134.226.81.10] helo=walton.maths.tcd.ie) by salmon.maths.tcd.ie with SMTP id ; 12 Jan 2007 22:05:52 +0000 (GMT) Date: Fri, 12 Jan 2007 22:05:51 +0000 From: David Malone To: Attila Nagy Message-ID: <20070112220551.GA34667@walton.maths.tcd.ie> References: <45A0229F.7070701@fsn.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45A0229F.7070701@fsn.hu> User-Agent: Mutt/1.5.6i Sender: dwmalone@maths.tcd.ie Cc: freebsd-hackers@freebsd.org Subject: Re: ufs_rename: fvp == tvp (can't happen), but it did X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2007 22:53:07 -0000 On Sat, Jan 06, 2007 at 11:28:47PM +0100, Attila Nagy wrote: > The strange thing happens when both the local and FC disks are working > in the mirrors. I get the following warning very often: > ufs_rename: fvp == tvp (can't happen) We get these occasionally on a 4.11 NFS server, and we've been getting them for years. They do seem to be harmless in our case. David. From owner-freebsd-hackers@FreeBSD.ORG Sat Jan 13 00:13:22 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D5B3416A412 for ; Sat, 13 Jan 2007 00:13:22 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) by mx1.freebsd.org (Postfix) with ESMTP id 66DAF13C45D for ; Sat, 13 Jan 2007 00:13:22 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.13.8/8.13.8/ALCHEMY.FRANKEN.DE) with ESMTP id l0D02mGg093404; Sat, 13 Jan 2007 01:02:55 +0100 (CET) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.13.8/8.13.8/Submit) id l0D02l4h093403; Sat, 13 Jan 2007 01:02:47 +0100 (CET) (envelope-from marius) Date: Sat, 13 Jan 2007 01:02:47 +0100 From: Marius Strobl To: DeuZa Message-ID: <20070113000247.GA93293@alchemy.franken.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i Cc: freebsd-hackers@freebsd.org Subject: Re: ATKBD_DFLT_KEYMAP kernel's options ??? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2007 00:13:22 -0000 On Fri, Jan 12, 2007 at 10:56:49PM +0100, DeuZa wrote: > Hello everybody, > > On my "old" box (5-STABLE from 4 March) this kernel's options works fine : > > options ATKBD_DFLT_KEYMAP # Gestion du clavier FR > makeoptions ATKBD_DFLT_KEYMAP=fr.iso.acc > > But on my new p4 (6-STABLE, sources tonight) this doesn't work :/ > Without error, and the options appears always in the LINT file ... > > Are you any ideas please ? > If you're using kbdmux(4) try to disable it (either via the hint described in the kbdmux(4) man page or just remove it from your kernel). {AT,SUN,U}KBD_DFLT_KEYMAP can't work with kbdmux(4) and so far kbdmux(4) doesn't implement something equivalent itself. Marius From owner-freebsd-hackers@FreeBSD.ORG Sat Jan 13 08:50:23 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B95D316A407 for ; Sat, 13 Jan 2007 08:50:23 +0000 (UTC) (envelope-from deuza42@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.185]) by mx1.freebsd.org (Postfix) with ESMTP id 52B5513C442 for ; Sat, 13 Jan 2007 08:50:23 +0000 (UTC) (envelope-from deuza42@gmail.com) Received: by nf-out-0910.google.com with SMTP id k27so1429166nfc for ; Sat, 13 Jan 2007 00:50:22 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=VNNW5R2pIHrWYBgovcpmtZCQGB4ReRFY7/MRR122z1nUQK7hhWePwo2lJwZ8GUxyS3JlYIbqvyAvWW+/gl+NxsJfFcuwcpHlGpYJZCpbUFw9ybAihhZC71XHfCW6kh2J0oroyGzwBiSuljHQxSsb8WvbrbsE0gZ7Xx8Fn6gBXmA= Received: by 10.82.120.15 with SMTP id s15mr281924buc.1168678221744; Sat, 13 Jan 2007 00:50:21 -0800 (PST) Received: by 10.82.183.13 with HTTP; Sat, 13 Jan 2007 00:50:20 -0800 (PST) Message-ID: Date: Sat, 13 Jan 2007 09:50:20 +0100 From: DeuZa To: freebsd-hackers@freebsd.org In-Reply-To: <20070113000247.GA93293@alchemy.franken.de> MIME-Version: 1.0 References: <20070113000247.GA93293@alchemy.franken.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: ATKBD_DFLT_KEYMAP kernel's options ??? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2007 08:50:23 -0000 > If you're using kbdmux(4) try to disable it (either via the hint > described in the kbdmux(4) man page or just remove it from your > kernel). {AT,SUN,U}KBD_DFLT_KEYMAP can't work with kbdmux(4) and > so far kbdmux(4) doesn't implement something equivalent itself. > > Marius > > I have rebuild my kernel without this device and all work nice now :) Thanks Marius ! Best regards 2A From owner-freebsd-hackers@FreeBSD.ORG Sat Jan 13 10:13:57 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EA30E16A412; Sat, 13 Jan 2007 10:13:57 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.freebsd.org (Postfix) with ESMTP id 782FE13C4DB; Sat, 13 Jan 2007 10:13:57 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1H5ftb-000Okd-FO; Sat, 13 Jan 2007 12:13:55 +0200 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Scott Long In-reply-to: <45A7F6A4.4030707@samsco.org> References: <20070112195549.GA77181@freebie.xs4all.nl> <45A7F6A4.4030707@samsco.org> Comments: In-reply-to Scott Long message dated "Fri, 12 Jan 2007 13:59:16 -0700." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 13 Jan 2007 12:13:55 +0200 From: Danny Braniss Message-ID: Cc: Wilko Bulte , Pawel Jakub Dawidek , freebsd-hackers@freebsd.org, freebsd-scsi@freebsd.org Subject: Re: iSCSI disconnects dilema X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2007 10:13:58 -0000 > Wilko Bulte wrote: > > On Fri, Jan 12, 2007 at 09:31:04PM +0200, Danny Braniss wrote.. > >>> --s/l3CgOIzMHHjg/5 > >>> Content-Type: text/plain; charset=iso-8859-2 > >>> Content-Disposition: inline > >>> Content-Transfer-Encoding: quoted-printable > >>> > >>> On Tue, Jan 09, 2007 at 09:06:46AM +0200, Danny Braniss wrote: > >>>> Hi, > >>>> While I think I have almost solved the problem of network disconnects, > >>>> It downed on me a major problem: > >>>> When a 'local' disk crashes, the kernel will probably hang/panic/crash. > >>>> if i don't try to recover, then there is no change in the above scenario. > >>>> if i try to recover, then the client does not know that it should > >>>> umount/fsck/mount. > >>>> While all this seems familiar, removing a floppy/disk-on-key while it's > >>>> mounted, we could always say "you shouldn't have done that!", with > >>>> a network connection, it can happen very often - rebooting the target, a > >>>> network hickup, etc. > >>>> =20 > >>>> So, any ideas? > >>> In my opinion it should be done this way: > >>> > >>> You have a queue of I/O requests. You send the to the other end and wait > >>> for confirmation. Until confirmation is received, you keep the requests > >>> queued. If the other end dies, you try to reconnect (until some timeout > >>> expires, the processes which send those requests will just wait), if you > >>> reconnect successfully, you resend not-confirmed requests, if you won't > >>> be able to reconnect, you just pass the errors up. > >>> > >>> This is what I did in ggate and it seems to work. > >> That is basically what i'm doing - unacked request get requed. > >> the problem I fear (and maybe I'm paranoid :-): > > > > Paranoia is a Good Thing(TM) in data storage land :-) > > > >> assume the following scenario, the client(initiator) sends a write command, > >> the target acks it, then it crashes, if the write was never completed, > >> the initiator goes on as nothing ever happened. > > > > Yes, but what can the initiator do about that? I mean, it does not have any > > visibility of what the target has (or has not) done with the data. ' > > > > This is roughly the same as a RAID box accepting a write into a writeback cache > > and ACK-ing to the host. You can only assume that the RAID box' cache > > will get flushed to the spindles properly. All the usual horror scenarios > > with a broken battery backup of the cache and a powerfailure etc apply here. > > > > Wilko > > > > I forget, does iSCSI have a concept of a flush_cache command, or the > equivalent of what parallel SCSI does with ordered tags? not realy - or I can't find it. iSCSI is mainly and envelope for scsi commands, so whatever the CAM does, it will pass it on. There are some managemenet commands, so the target can tell the initiator that it's going down for example (and what should the driver do in such a case in freebsd?) > If so, then > that's how your app or OS knows that the transaction got committed to > stable storage. It's been long assumed in the external storage world > that you are at the mercy of the external storage cache, so the problem > that Danny is referring to is nothing new. The real question is how > to implement the equivalent mechanism that iSCSI provides in a way that > the OS/app can make use of it. For example, CAM issues an ordered tag > periodically to flush the disk cache to stable storage. nice, (or wishful thinking :-), the scsi part of iSCSI is/can be software/virtual. > Most storage > drivers, including CAM, will issue some sort of a flush_cache command to > the controller and media during system shutdown. this took me a long time to fix! the userland program got killed at shutdown, the link was lost, and so there was no way to flush buffers, fixed by calling fget(...) too. I guess I can summarize: (and use the 3 monkey law :-) 1- assume the target is 'well behaved' and will flush cache. 2- there is - currently - no way to tell the OS that not all seems to be as expected. 3- keep quiet and hope for the best. danny From owner-freebsd-hackers@FreeBSD.ORG Sat Jan 13 10:49:46 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 33D6D16A412 for ; Sat, 13 Jan 2007 10:49:46 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe07.swip.net [212.247.154.193]) by mx1.freebsd.org (Postfix) with ESMTP id CAC0913C455 for ; Sat, 13 Jan 2007 10:49:45 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] Received: from [193.217.102.48] (account mc467741@c2i.net HELO [10.0.0.249]) by mailfe07.swip.net (CommuniGate Pro SMTP 5.0.12) with ESMTPA id 382832843 for freebsd-hackers@freebsd.org; Sat, 13 Jan 2007 11:49:43 +0100 From: Hans Petter Selasky To: freebsd-hackers@freebsd.org Date: Sat, 13 Jan 2007 11:49:19 +0100 User-Agent: KMail/1.7 References: <200701121437.10273.hselasky@c2i.net> In-Reply-To: <200701121437.10273.hselasky@c2i.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200701131149.20182.hselasky@c2i.net> Subject: Re: mii_bus problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2007 10:49:46 -0000 On Friday 12 January 2007 14:37, Hans Petter Selasky wrote: > Hi, > > Can someone here explain from where I can call "mii_pollstat()". I read > somewhere on the internet that I cannot call this function from the so > called "tick" routine, where "mii_tick()" is called. I currently have the > following code: > > static void > aue_cfg_tick(struct aue_softc *sc, > struct aue_config_copy *cc, u_int16_t refcount) > { > printf("%s:%d\n", __FUNCTION__, __LINE__); > > struct ifnet * ifp = sc->sc_ifp; > struct mii_data * mii = GET_MII(sc); > > if ((cc == NULL) || > (ifp == NULL) || > (mii == NULL)) { > /* not ready */ > return; > } > > mii_tick(mii); > > mii_pollstat(mii); > > if ((sc->sc_flags & AUE_FLAG_WAIT_LINK) && > (mii->mii_media_status & IFM_ACTIVE) && > (IFM_SUBTYPE(mii->mii_media_active) != IFM_NONE)) { > sc->sc_flags &= ~AUE_FLAG_WAIT_LINK; > } > > sc->sc_media_active = mii->mii_media_active; > sc->sc_media_status = mii->mii_media_status; > > /* start stopped transfers, if any */ > > aue_start_transfers(sc); > > return; > } > > > But after this function returns, the kernel corrupts, and it pagefaults in > the "swi6 taskqueue". Commenting out "mii_pollstat()" fixes the kernel > panic. After some debugging I found out that the kernel corrupted because there was not a pointer to "struct ifnet" at the beginning of the softc. I see that some parts of the MII code uses an "EVIL HACK" to get the "struct ifnet" pointer. This should be fixed. Now calling mii_pollstat() works. --HPS From owner-freebsd-hackers@FreeBSD.ORG Sat Jan 13 12:49:11 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4049616A407 for ; Sat, 13 Jan 2007 12:49:11 +0000 (UTC) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (eva.fit.vutbr.cz [147.229.176.14]) by mx1.freebsd.org (Postfix) with ESMTP id B693B13C45E for ; Sat, 13 Jan 2007 12:49:10 +0000 (UTC) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (localhost [127.0.0.1]) by eva.fit.vutbr.cz (envelope-from xdivac02@eva.fit.vutbr.cz) (8.13.8/8.13.7) with ESMTP id l0DCUh12008384 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 13 Jan 2007 13:30:43 +0100 (CET) Received: (from xdivac02@localhost) by eva.fit.vutbr.cz (8.13.8/8.13.3/Submit) id l0DCUhgE008383 for hackers@freebsd.org; Sat, 13 Jan 2007 13:30:43 +0100 (CET) Date: Sat, 13 Jan 2007 13:30:43 +0100 From: Divacky Roman To: hackers@freebsd.org Message-ID: <20070113123043.GA8332@stud.fit.vutbr.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.2i X-Scanned-By: MIMEDefang 2.57 on 147.229.176.14 Cc: Subject: ISOPEN flag to namei X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2007 12:49:11 -0000 hi what is the ISOPEN flag to namei good for? the description there says "caller is opening; return a real vnode." but the flag doesnt seem to be used anywhere for anything thnx roman From owner-freebsd-hackers@FreeBSD.ORG Sat Jan 13 22:54:09 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A085016A407 for ; Sat, 13 Jan 2007 22:54:09 +0000 (UTC) (envelope-from jgrosch@mooseriver.com) Received: from gdead.mooseriver.com (gdead.mooseriver.com [205.166.121.45]) by mx1.freebsd.org (Postfix) with ESMTP id 830D813C442 for ; Sat, 13 Jan 2007 22:54:09 +0000 (UTC) (envelope-from jgrosch@mooseriver.com) Received: by gdead.mooseriver.com (Postfix, from userid 2010) id 741863C9301; Sat, 13 Jan 2007 14:54:09 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on gdead.mooseriver.com X-Spam-Level: X-Spam-Status: No, score=-0.9 required=5.0 tests=AWL,BAYES_00, DNS_FROM_RFC_WHOIS,FORGED_RCVD_HELO autolearn=no version=3.1.7 Received: from mooseriver.com (h-66-166-146-73.snvacaid.covad.net [66.166.146.73]) by gdead.mooseriver.com (Postfix) with ESMTP id 2ECD73C92FC; Sat, 13 Jan 2007 14:54:07 -0800 (PST) Received: by mooseriver.com (Postfix, from userid 200) id 0673E2F06AD; Sat, 13 Jan 2007 14:54:07 -0800 (PST) Date: Sat, 13 Jan 2007 14:54:07 -0800 From: Josef Grosch To: Doug Barton Message-ID: <20070113225406.GB22396@mooseriver.com> References: <20070111170424.GA85484@mooseriver.com> <45A800F4.20504@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PmA2V3Z32TCmWXqI" Content-Disposition: inline In-Reply-To: <45A800F4.20504@FreeBSD.org> User-Agent: Mutt/1.4.2.2i Organization: Moose River, LLC Cc: freebsd-hackers@freebsd.org Subject: Re: Getting a patch commited X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jgrosch@MooseRiver.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2007 22:54:09 -0000 --PmA2V3Z32TCmWXqI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 12, 2007 at 01:43:16PM -0800, Doug Barton wrote: > Josef Grosch wrote: > > I know everyone is busy with getting 6.2 out the door but could someone > > commit the patch at conf/107453 ? >=20 > You generally get a better response to requests like this if you: >=20 > 1. Mention briefly what the patch is about. > 2. Include the URL to the PR > 3. cc the responsible person for the PR >=20 > hth, >=20 > Doug Thanks Doug. I'll keep that in mind. Josef --=20 Josef Grosch | Another day closer to a | FreeBSD 6.1 jgrosch@MooseRiver.com | Micro$oft free world | Berkeley, Ca. --PmA2V3Z32TCmWXqI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- iD8DBQFFqWMNy8prLS1GYSERAo0yAKDrjEb9aewTHJ4FRLdXYdvyZCdrXACgwZ2F kmDSURwfYp65p5Qi4QL/c64= =YFV0 -----END PGP SIGNATURE----- --PmA2V3Z32TCmWXqI--