From owner-fam@oss.sgi.com Sun Feb 4 17:42:21 2001 Received: by oss.sgi.com id ; Sun, 4 Feb 2001 17:42:02 -0800 Received: from ritchie.pisoftware.com ([203.20.51.20]:39174 "EHLO ritchie.pisoftware.com") by oss.sgi.com with ESMTP id ; Sun, 4 Feb 2001 17:41:55 -0800 Received: from morris.staff.pisoftware.com (stallman.pisoftware.com [203.20.51.50]) by ritchie.pisoftware.com (8.11.0/8.11.0/Debian 8.11.0-1) with ESMTP id f151d8c25998 for ; Mon, 5 Feb 2001 11:39:08 +1000 X-Authentication-Warning: ritchie.pisoftware.com: Host stallman.pisoftware.com [203.20.51.50] claimed to be morris.staff.pisoftware.com Received: from pisoftware.com (keith@pike.staff.pisoftware.com [192.168.20.82]) by morris.staff.pisoftware.com (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id LAA19680 for ; Mon, 5 Feb 2001 11:41:23 +1000 X-Authentication-Warning: morris.staff.pisoftware.com: Host keith@pike.staff.pisoftware.com [192.168.20.82] claimed to be pisoftware.com Message-ID: <3A7E04C3.30526143@pisoftware.com> Date: Mon, 05 Feb 2001 11:41:23 +1000 From: Keith Ahern X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.17 i686) X-Accept-Language: en MIME-Version: 1.0 To: fam@oss.sgi.com Subject: [fam] Will FAM work on an SMB Mounted partition? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-fam@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;fam-outgoing I'm currently looking for non-polling solutions for monitoring filesystems FAM is perfect for our Linux/Un*x needs but we also need a solution for windows. I was wondering if FAM would detect changes on a vfat (SMB) mounted filesystem (via Samba). Comments ? Keith Ahern Plugged In Software -- Source code, list archive, and docs: http://oss.sgi.com/projects/fam/ To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com From owner-fam@oss.sgi.com Mon Feb 5 04:09:04 2001 Received: by oss.sgi.com id ; Mon, 5 Feb 2001 04:08:54 -0800 Received: from sgi.SGI.COM ([192.48.153.1]:5429 "EHLO sgi.com") by oss.sgi.com with ESMTP id ; Mon, 5 Feb 2001 04:08:49 -0800 Received: from rlyeh.engr.sgi.com ([198.29.76.98]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id EAA05113 for ; Mon, 5 Feb 2001 04:08:48 -0800 (PST) mail_from (rusty@rlyeh.engr.sgi.com) Received: (from rusty@localhost) by rlyeh.engr.sgi.com (SGI-8.9.3/8.9.3) id EAA17378; Mon, 5 Feb 2001 04:08:32 -0800 (PST) From: "Rusty Ballinger" Message-Id: <10102050408.ZM17367@rlyeh.engr.sgi.com> Date: Mon, 5 Feb 2001 04:08:31 -0800 In-Reply-To: Keith Ahern "[fam] Will FAM work on an SMB Mounted partition?" (Feb 5, 11:41am) References: <3A7E04C3.30526143@pisoftware.com> X-Face: #)4}U4e`O6YEe%oBzE}>ycmT!Xt?Myiqo~|p3Wh'UuQ[N7)&4\4?8:1n)bmPX]b@#k94%!VojpODdmk:sCr1b\-aXD&P:wjBqupMB:ag6}BwVseJZM@K{$E|0J9}&,Rpdg{&N4/Y8&PTm6>|r[,gI2T*qN!`AZhl>Bdy7JR`dDvP(/pz.}?Q@dg':mlV`RX51Z_ZG?Gta|Q!iA[MaOh Reply-To: rusty@sgi.com X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: keith@pisoftware.com Subject: Re: [fam] Will FAM work on an SMB Mounted partition? Cc: fam@oss.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-fam@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;fam-outgoing > I was wondering if FAM would detect changes on a vfat (SMB) > mounted filesystem (via Samba). I think changes should be noticed by fam if they originate on the local host & you've got imon support. Changes originating on the server, or on other clients, won't be noticed by fam unless it's polling the SMB filesystem. Fam has stuff built in for nfs where it will try to talk to fam on the nfs server, and get updates without having to poll the NFS filesystem, but I don't think it does anything similar for Samba. (I don't really know anything about Samba; if it's similar enough to NFS, it might "just work" the same way, but I'd be really surprised.) --Rusty -- Source code, list archive, and docs: http://oss.sgi.com/projects/fam/ To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com From owner-fam@oss.sgi.com Tue Feb 13 21:06:00 2001 Received: by oss.sgi.com id ; Tue, 13 Feb 2001 21:05:50 -0800 Received: from haml-37.res.umass.edu ([128.119.123.37]:6 "HELO Abulafia.gnosis.org") by oss.sgi.com with SMTP id ; Tue, 13 Feb 2001 21:05:28 -0800 Received: from [192.168.0.2] (Rei [192.168.0.2]) by Abulafia.gnosis.org (Postfix) with ESMTP id C416C133002 for ; Wed, 14 Feb 2001 00:05:25 -0500 (EST) Date: Wed, 14 Feb 2001 00:05:25 -0500 (EST) From: dirac X-X-Sender: To: Subject: [fam] Imon for 2.4.0 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-fam@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;fam-outgoing Hello, I'm sorry to bother you all, but I was just wondering when the imon patch will be released for the final 2.4 kernel. I would like to experiment with Enlightenment DR17 and I have heard that this patch will allow things to go much more smoothly in the efsd program. Thanks. Joseph -- "As long as you remain in your private vacuum, you can pretend you are in harmony with the one. But the moment you pick up the clay, electronic or otherwise, you become a demiurge, and he who embarks on the creation of worlds is already tainted with corruption and evil." -- "Foucault's Pendulum", Umberto Eco -- Source code, list archive, and docs: http://oss.sgi.com/projects/fam/ To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com From owner-fam@oss.sgi.com Wed Feb 14 21:02:00 2001 Received: by oss.sgi.com id ; Wed, 14 Feb 2001 21:01:50 -0800 Received: from fly.HiWAAY.net ([208.147.154.56]:33810 "EHLO mail.hiwaay.net") by oss.sgi.com with ESMTP id ; Wed, 14 Feb 2001 21:01:30 -0800 Received: from hiwaay.net (IDENT:nickh@tnt11-216-180-128-71.dialup.hiwaay.net [216.180.128.71]) by mail.hiwaay.net (8.11.0/8.11.0) with ESMTP id f1F51So20722 for ; Wed, 14 Feb 2001 23:01:28 -0600 (CST) Message-ID: <3A8B62D0.74CED073@hiwaay.net> Date: Wed, 14 Feb 2001 23:02:08 -0600 From: Nick Hudson X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.17-21mdk i686) X-Accept-Language: en MIME-Version: 1.0 To: fam@oss.sgi.com Subject: Re: [fam] Imon for 2.4.0 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-fam@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;fam-outgoing Just for the record I dont use imon to run e17 cv. If you run efsd in your .xsession script with the -f option it will fork it into the background and it woirks just fine with fam only Nick dirac wrote: > > Hello, I'm sorry to bother you all, but I was just wondering > when the imon patch will be released for the final 2.4 kernel. I would > like to experiment with Enlightenment DR17 and I have heard that this > patch will allow things to go much more smoothly in the efsd program. > Thanks. > > Joseph > > -- > "As long as you remain in your private vacuum, you can pretend you are in harmony with the one. But the moment you pick up the clay, electronic or otherwise, you become a demiurge, and he who embarks on the creation of worlds is already tainted with corruption and evil." > -- "Foucault's Pendulum", Umberto Eco > > -- > Source code, list archive, and docs: http://oss.sgi.com/projects/fam/ > To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com -- Source code, list archive, and docs: http://oss.sgi.com/projects/fam/ To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com From owner-fam@oss.sgi.com Wed Feb 21 17:01:48 2001 Received: by oss.sgi.com id ; Wed, 21 Feb 2001 17:01:38 -0800 Received: from c418236-a.clmba1.mo.home.com ([24.12.203.134]:65130 "EHLO babylon.merseine.nu") by oss.sgi.com with ESMTP id ; Wed, 21 Feb 2001 17:01:14 -0800 Received: (from ishmael@localhost) by babylon.merseine.nu (8.11.2/8.11.2) id f1M12Wn95961 for fam@oss.sgi.com; Wed, 21 Feb 2001 19:02:32 -0600 (CST) (envelope-from ishmael) Date: Wed, 21 Feb 2001 19:02:32 -0600 From: Jeremy Norris To: fam@oss.sgi.com Subject: [fam] Fam on BSD Message-ID: <20010221190232.A95417@babylon.merseine.nu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-fam@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;fam-outgoing Quite a few months ago, someone posted on this list a message about having almost successfully gotten fam going on FreeBSD. However, no followups to that appear to have been made. I'm just curious what became of that effort, and if there are still people out there working or looking at getting fam going on the BSDs? Jeremy -- Source code, list archive, and docs: http://oss.sgi.com/projects/fam/ To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com From owner-fam@oss.sgi.com Wed Feb 21 18:13:28 2001 Received: by oss.sgi.com id ; Wed, 21 Feb 2001 18:13:18 -0800 Received: from ont24-60.member.dsl-only.net ([63.105.24.60]:1548 "EHLO sub24-60.member.dsl-only.net") by oss.sgi.com with ESMTP id ; Wed, 21 Feb 2001 18:13:04 -0800 Received: (from eito@localhost) by sub24-60.member.dsl-only.net (8.11.1/8.9.3) id f1M2Cmr85758; Wed, 21 Feb 2001 18:12:48 -0800 (PST) (envelope-from eito) Date: Wed, 21 Feb 2001 18:12:48 -0800 From: eito@cs.pdx.edu To: Jeremy Norris Cc: fam@oss.sgi.com Subject: Re: [fam] Fam on BSD Message-ID: <20010221181248.B73901@sub24-60.member.dsl-only.net> Reply-To: eito@cs.pdx.edu References: <20010221190232.A95417@babylon.merseine.nu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Mutt/1.2.5i-jp2 In-Reply-To: <20010221190232.A95417@babylon.merseine.nu> Sender: owner-fam@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;fam-outgoing Hi Jeremy, I am not the person who posted the message you mentioned, but I myself ported fam version 2.6.4 on FreeBSD, and have used it with EFM (enlightenment file manager) a couple of month ago. It seemed to work, I am not sure if I did it right... If you are curious, you can get the tar ball from http://www.cs.pdx.edu/~eito/fam-oss-2.6.4-freebsd.tar.gz I have used this on FreeBSD 4.{0,1}-stable. I am sure that it would work on 4.2-stable, but I have not tried. :eito On Wed, Feb 21, 2001 at 07:02:32PM -0600, Jeremy Norris wrote: > Quite a few months ago, someone posted on this list a message about having > almost successfully gotten fam going on FreeBSD. However, no followups to that > appear to have been made. I'm just curious what became of that effort, and if > there are still people out there working or looking at getting fam going on > the BSDs? > > Jeremy -- Source code, list archive, and docs: http://oss.sgi.com/projects/fam/ To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com From owner-fam@oss.sgi.com Mon Feb 26 07:00:18 2001 Received: by oss.sgi.com id ; Mon, 26 Feb 2001 07:00:09 -0800 Received: from ns.oddjob.se ([194.23.92.14]:14943 "EHLO mail.oddjob.se") by oss.sgi.com with ESMTP id ; Mon, 26 Feb 2001 06:59:53 -0800 Received: from bart.mgon.com ([192.168.0.100] helo=bart) by mail.oddjob.se with smtp (Exim 3.13 #3) id 14XPki-0002u2-00 for fam@oss.sgi.com; Mon, 26 Feb 2001 16:39:56 +0100 From: "Johan Isacsson" To: Subject: [fam] Max number of inodes? Date: Mon, 26 Feb 2001 15:52:36 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-fam@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;fam-outgoing Hello, Is there a limit in the number of inodes that imon can monitor? I guess it depends on system resources, is there a way to calculate on it? The reason i wonder is that i'm having trouble when i try to monitor a directory that's using 42776 inodes. What happens is this (after a while, i'm having a perl script adding directories to FAM): My perl script stops In the console i get many of theese: Kmalloc: Size (196608) Too large! (I have lots of free memory) And when i ctrl-c out of the script i get lots of lines looking like theese: fam[28346]: fd 6 write error: Broken pipe fam[28346]: fd 6 write error: Broken pipe fam[28346]: IMONIOC_EXPRESS on "/web/622/cgi-data/trade/auction/greatlakes/rare" failed (euid: 0): Cannot allocate memory fam[28346]: fd 6 write error: Broken pipe fam[28346]: IMONIOC_EXPRESS on "961461914.dat" with cwd "/web/622/cgi-data/trade/auction/greatlakes/rare" failed (euid: 0): Cannot allocate memory fam[28346]: fd 6 write error: Broken pipe fam[28346]: IMONIOC_EXPRESS on "961461991.dat" with cwd "/web/622/cgi-data/trade/auction/greatlakes/rare" failed (euid: 0): Cannot allocate memory fam[28346]: fd 6 write error: Broken pipe fam[28346]: fd 6 write error: Broken pipe fam[28346]: IMONIOC_EXPRESS on "/web/622/cgi-data/trade/auction/greatlakes/misc" failed (euid: 0): Cannot allocate memory fam[28346]: fd 6 write error: Broken pipe .... i run fam like this: fam -v & I'm using imon 0.0.2 on Linux kernel 2.2.17, latest version of fam. Plese respond to johan@mgon.com, i'm not (yet) on the mailinglist. I'd appretiate all help i can get to get this working, i think this is excellent software! :) Thanks, Johan Isacsson MGON -- Source code, list archive, and docs: http://oss.sgi.com/projects/fam/ To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com From owner-fam@oss.sgi.com Mon Feb 26 08:08:49 2001 Received: by oss.sgi.com id ; Mon, 26 Feb 2001 08:08:30 -0800 Received: from dsl-2-dslam1-31.urbanet.ch ([195.202.196.17]:33036 "HELO convert =?ISO-8859-1?Q?rfc822-to-8bitoss.sg=B9>=01?= lausanne.4unet.net") by oss.sgi.com with SMTP id ; Mon, 26 Feb 2001 08:08:26 -0800 Received: from developer.ch (madmag [172.23.17.210]) by lausanne.4unet.net (Postfix) with ESMTP id EE74223700; Mon, 26 Feb 2001 17:59:54 +0100 (CET) Message-ID: <3A9A7F5D.2FA7D636@developer.ch> Date: Mon, 26 Feb 2001 17:07:57 +0100 From: Atif Ghaffar Reply-To: atif@4unet.net Organization: 4unet X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.16 i686) X-Accept-Language: en MIME-Version: 1.0 To: fam@oss.sgi.com Subject: [fam] Max number of inodes? Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-fam@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;fam-outgoing Hi, The script Johan mentioned is: http://madmag.ispman.net/~aghaffar/lfparser-2.9/article.199/article/fam_mirror.html I am using (trying to use) fam + imon for data replication. Here are the ideas/reasons http://madmag.ispman.net/~aghaffar/lfparser-2.9/article.199/article/article199.shtml I am having same problems These are from /var/log/messages (after I start monitoring and trigger and event such as delete a file) node2:/usr/src/linux # Feb 26 17:34:00 node2 fam[24076]: imon event received by fam built without imon support... tell fam@oss.sgi.com to fix this! Feb 26 17:34:00 node2 inetd[726]: /usr/local/bin/fam: exit signal 0x6 Feb 26 17:34:00 node2 fam[24076]: imon event received by fam built without imon support... tell fam@oss.sgi.com to fix this! Feb 26 17:34:00 node2 inetd[726]: /usr/local/bin/fam: exit signal 0x6 I have kernel 2.2.16 with imon support compiled (not as a module) imon-meter says node2:/usr/src/linux # cat /proc/fs/imon-meter min shift: 8 (256 entries) max shift: 17 (131072 entries) shift: 12 (4096 entries) upper alpha: 2048/4096 lower alpha: 512/4096 current table: lookups: 5696 probes: 3163 hits: 2 misses: 4191 adds: 1342 grows: 4 shrinks: 0 deletes: 0 dprobes: 0 dmoves: 0 Any help is much appreciated. thanks & best regards -- Atif Ghaffar Internet Development Manager 4unet AG/SA/Ltd. Unix! Me too. -------------------------. +41 21 351 53 60 ¦ voice +41 78 787 51 45 ¦ mobile +41 86 0796598972¦ fax http://www.4unet.net ¦ www http://atif.developer.ch ¦ homepage atif.ghaffar@4unet.net ¦ email -- Source code, list archive, and docs: http://oss.sgi.com/projects/fam/ To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com From owner-fam@oss.sgi.com Mon Feb 26 14:13:22 2001 Received: by oss.sgi.com id ; Mon, 26 Feb 2001 14:13:13 -0800 Received: from mirapoint2.brutele.be ([212.68.193.7]:40733 "EHLO mirapoint2.brutele.be") by oss.sgi.com with ESMTP id ; Mon, 26 Feb 2001 14:12:55 -0800 Received: from nexus6.brutele.be ([212.68.216.196]) by mirapoint2.brutele.be (Mirapoint) with ESMTP id ABK08051; Mon, 26 Feb 2001 23:12:51 +0100 (CET) Received: from shellc.jdegreef.net ([192.168.0.2] ident=mail) by nexus6.brutele.be with esmtp (Exim 3.12 #1 (Debian)) id 14XVsx-0003pE-00 for ; Mon, 26 Feb 2001 23:12:51 +0100 Received: from jdegreef by shellc.jdegreef.net with local (Exim 3.22 #1 (Debian)) id 14XVsw-0004bM-00 for ; Mon, 26 Feb 2001 23:12:50 +0100 Date: Mon, 26 Feb 2001 23:12:50 +0100 From: Jerome De Greef To: fam@oss.sgi.com Subject: [fam] imon 0.0.[12]-2.4.0-test9 compile error Message-ID: <20010226231250.A16202@shellc.jdegreef.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.15i X-Editor: Vim http://www.vim.org/ X-Operating-System: Linux/2.4.1 (i686) X-Uptime: 11:07pm up 1 day, 6:31, 1 user, load average: 0.30, 1.35, 1.42 Sender: owner-fam@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;fam-outgoing Hi, Here's what I get when compiling imon 0.0.1 or 0.0.2 for Linux with kernel 2.4.0-test9 ld -m elf_i386 -T /usr/src/linux/arch/i386/vmlinux.lds -e stext arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/main.o init/version.o \ --start-group \ arch/i386/kernel/kernel.o arch/i386/mm/mm.o kernel/kernel.o mm/mm.o fs/fs.o ipc/ipc.o \ drivers/block/block.o drivers/char/char.o drivers/misc/misc.o drivers/net/net.o drivers/media/media.o drivers/parport/parport.a drivers/char/drm/drm.o drivers/ide/idedriver.o drivers/cdrom/cdrom.a drivers/pci/pci.a drivers/video/video.o \ net/network.o \ /usr/src/linux/arch/i386/lib/lib.a /usr/src/linux/lib/lib.a /usr/src/linux/arch/i386/lib/lib.a \ --end-group \ -o vmlinux kernel/kernel.o: In function `do_exit': kernel/kernel.o(.text+0x7b9f): undefined reference to `imon_enabled' kernel/kernel.o(.text+0x7bbf): undefined reference to `imon_event' kernel/kernel.o(__ksymtab+0x610): undefined reference to `imon_event' kernel/kernel.o(__ksymtab+0x618): undefined reference to `imon_broadcast' kernel/kernel.o(__ksymtab+0x620): undefined reference to `imon_enabled' fs/fs.o: In function `sys_write': fs/fs.o(.text+0x178d): undefined reference to `imon_enabled' fs/fs.o(.text+0x1799): undefined reference to `imon_event' fs/fs.o: In function `sys_writev': fs/fs.o(.text+0x1a9c): undefined reference to `imon_enabled' fs/fs.o(.text+0x1ab3): undefined reference to `imon_event' fs/fs.o: In function `do_execve': fs/fs.o(.text+0x9fbf): undefined reference to `imon_enabled' fs/fs.o(.text+0x9fd9): undefined reference to `imon_event' fs/fs.o(.text+0xa017): undefined reference to `imon_enabled' fs/fs.o(.text+0xa029): undefined reference to `imon_event' fs/fs.o: In function `vfs_create': fs/fs.o(.text+0xbe33): undefined reference to `imon_enabled' fs/fs.o(.text+0xbe43): undefined reference to `imon_event' fs/fs.o: In function `sys_mknod': fs/fs.o(.text+0xc67c): undefined reference to `imon_enabled' fs/fs.o(.text+0xc692): undefined reference to `imon_event' fs/fs.o: In function `vfs_mkdir': fs/fs.o(.text+0xc767): undefined reference to `imon_enabled' fs/fs.o(.text+0xc777): undefined reference to `imon_event' fs/fs.o: In function `vfs_rmdir': fs/fs.o(.text+0xca17): undefined reference to `imon_enabled' fs/fs.o(.text+0xca27): undefined reference to `imon_event' fs/fs.o: In function `vfs_unlink': fs/fs.o(.text+0xccb2): undefined reference to `imon_enabled' fs/fs.o(.text+0xccc2): undefined reference to `imon_event' fs/fs.o(.text+0xccd0): undefined reference to `imon_enabled' fs/fs.o(.text+0xcce3): undefined reference to `imon_event' fs/fs.o: In function `vfs_symlink': fs/fs.o(.text+0xcea9): undefined reference to `imon_enabled' fs/fs.o(.text+0xceb9): undefined reference to `imon_event' fs/fs.o: In function `vfs_link': fs/fs.o(.text+0xd060): undefined reference to `imon_enabled' fs/fs.o(.text+0xd070): undefined reference to `imon_event' fs/fs.o: In function `vfs_rename_dir': fs/fs.o(.text+0xd672): undefined reference to `imon_enabled' fs/fs.o(.text+0xd681): undefined reference to `imon_event' fs/fs.o(.text+0xd693): undefined reference to `imon_enabled' fs/fs.o(.text+0xd6a9): undefined reference to `imon_event' fs/fs.o: In function `vfs_rename_other': fs/fs.o(.text+0xd978): undefined reference to `imon_enabled' fs/fs.o(.text+0xd984): undefined reference to `imon_event' fs/fs.o(.text+0xd992): undefined reference to `imon_enabled' fs/fs.o(.text+0xd99e): undefined reference to `imon_event' fs/fs.o: In function `notify_change': fs/fs.o(.text+0x146b2): undefined reference to `imon_enabled' fs/fs.o(.text+0x146c2): undefined reference to `imon_event' make: *** [vmlinux] Error 1 I'm using Debian unstable (sid) and kernel 2.4.0-test9 Does anyone have an idea on how to solve this? Thanks, Jerome -- +-------------------------------------------------------------------+ | Jerome De Greef | jdegreef@linuxbe.org | jdegreef@brutele.be | +-----------------+ jdegr@geac.com | jdegreef@linuxmail.org | +-------------------------------------------------+ -- Source code, list archive, and docs: http://oss.sgi.com/projects/fam/ To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com From owner-fam@oss.sgi.com Mon Feb 26 14:38:12 2001 Received: by oss.sgi.com id ; Mon, 26 Feb 2001 14:37:52 -0800 Received: from mirapoint2.brutele.be ([212.68.193.7]:52769 "EHLO mirapoint2.brutele.be") by oss.sgi.com with ESMTP id ; Mon, 26 Feb 2001 14:37:46 -0800 Received: from nexus6.brutele.be ([212.68.216.196]) by mirapoint2.brutele.be (Mirapoint) with ESMTP id ABK08715; Mon, 26 Feb 2001 23:37:42 +0100 (CET) Received: from shellc.jdegreef.net ([192.168.0.2] ident=mail) by nexus6.brutele.be with esmtp (Exim 3.12 #1 (Debian)) id 14XWH0-0003qO-00 for ; Mon, 26 Feb 2001 23:37:42 +0100 Received: from jdegreef by shellc.jdegreef.net with local (Exim 3.22 #1 (Debian)) id 14XWH0-0006yk-00 for ; Mon, 26 Feb 2001 23:37:42 +0100 Date: Mon, 26 Feb 2001 23:37:41 +0100 From: Jerome De Greef To: fam@oss.sgi.com Subject: [fam] imon 0.0.[12]-2.4.0-test9 compile error Message-ID: <20010226233741.B16202@shellc.jdegreef.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.15i X-Editor: Vim http://www.vim.org/ X-Operating-System: Linux/2.4.1 (i686) X-Uptime: 11:36pm up 1 day, 7:00, 1 user, load average: 0.75, 1.65, 1.46 Sender: owner-fam@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;fam-outgoing Hi, Forgot to say that I was compiling imon as a module... Jerome -- +-------------------------------------------------------------------+ | Jerome De Greef | jdegreef@linuxbe.org | jdegreef@brutele.be | +-----------------+ jdegr@geac.com | jdegreef@linuxmail.org | +-------------------------------------------------+ -- Source code, list archive, and docs: http://oss.sgi.com/projects/fam/ To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com From owner-fam@oss.sgi.com Mon Feb 26 15:07:22 2001 Received: by oss.sgi.com id ; Mon, 26 Feb 2001 15:07:12 -0800 Received: from sgi.SGI.COM ([192.48.153.1]:43892 "EHLO sgi.com") by oss.sgi.com with ESMTP id ; Mon, 26 Feb 2001 15:07:05 -0800 Received: from rlyeh.engr.sgi.com ([198.29.76.98]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id PAA00147 for ; Mon, 26 Feb 2001 15:07:01 -0800 (PST) mail_from (rusty@rlyeh.engr.sgi.com) Received: (from rusty@localhost) by rlyeh.engr.sgi.com (SGI-8.9.3/8.9.3) id PAA19424; Mon, 26 Feb 2001 15:07:12 -0800 (PST) From: "Rusty Ballinger" Message-Id: <10102261507.ZM19457@rlyeh.engr.sgi.com> Date: Mon, 26 Feb 2001 15:07:11 -0800 In-Reply-To: Jerome De Greef "[fam] imon 0.0.[12]-2.4.0-test9 compile error" (Feb 26, 11:12pm) References: <20010226231250.A16202@shellc.jdegreef.net> X-Face: #)4}U4e`O6YEe%oBzE}>ycmT!Xt?Myiqo~|p3Wh'UuQ[N7)&4\4?8:1n)bmPX]b@#k94%!VojpODdmk:sCr1b\-aXD&P:wjBqupMB:ag6}BwVseJZM@K{$E|0J9}&,Rpdg{&N4/Y8&PTm6>|r[,gI2T*qN!`AZhl>Bdy7JR`dDvP(/pz.}?Q@dg':mlV`RX51Z_ZG?Gta|Q!iA[MaOh Reply-To: rusty@sgi.com X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: jdegreef@brutele.be Subject: Re: [fam] imon 0.0.[12]-2.4.0-test9 compile error Cc: fam@oss.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-fam@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;fam-outgoing > Here's what I get when compiling imon 0.0.1 or 0.0.2 for Linux with > kernel 2.4.0-test9 ... > I'm using Debian unstable (sid) and kernel 2.4.0-test9 > > Does anyone have an idea on how to solve this? Two things- 1. I think imon doesn't work as a module. (The makefiles aren't quite right; there's one file containing the definition of imon_enabled & imon_event which needs to be built in even when the rest of imon is being built as a module.) If you build imon into the kernel, what happens? That brings us to point 2... 2. I haven't tried imon on 2.4.0-x yet. Maybe other people have? --Rusty -- Source code, list archive, and docs: http://oss.sgi.com/projects/fam/ To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com From owner-fam@oss.sgi.com Mon Feb 26 15:11:12 2001 Received: by oss.sgi.com id ; Mon, 26 Feb 2001 15:10:53 -0800 Received: from sgi.SGI.COM ([192.48.153.1]:19318 "EHLO sgi.com") by oss.sgi.com with ESMTP id ; Mon, 26 Feb 2001 15:10:50 -0800 Received: from rlyeh.engr.sgi.com ([198.29.76.98]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id PAA06823 for ; Mon, 26 Feb 2001 15:10:49 -0800 (PST) mail_from (rusty@rlyeh.engr.sgi.com) Received: (from rusty@localhost) by rlyeh.engr.sgi.com (SGI-8.9.3/8.9.3) id PAA19549; Mon, 26 Feb 2001 15:11:00 -0800 (PST) From: "Rusty Ballinger" Message-Id: <10102261510.ZM19474@rlyeh.engr.sgi.com> Date: Mon, 26 Feb 2001 15:10:59 -0800 In-Reply-To: "Rusty Ballinger" "Re: [fam] imon 0.0.[12]-2.4.0-test9 compile error" (Feb 26, 3:07pm) References: <20010226231250.A16202@shellc.jdegreef.net> <10102261507.ZM19457@rlyeh.engr.sgi.com> X-Face: #)4}U4e`O6YEe%oBzE}>ycmT!Xt?Myiqo~|p3Wh'UuQ[N7)&4\4?8:1n)bmPX]b@#k94%!VojpODdmk:sCr1b\-aXD&P:wjBqupMB:ag6}BwVseJZM@K{$E|0J9}&,Rpdg{&N4/Y8&PTm6>|r[,gI2T*qN!`AZhl>Bdy7JR`dDvP(/pz.}?Q@dg':mlV`RX51Z_ZG?Gta|Q!iA[MaOh Reply-To: rusty@sgi.com X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: jdegreef@brutele.be Subject: Re: [fam] imon 0.0.[12]-2.4.0-test9 compile error Cc: fam@oss.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-fam@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;fam-outgoing > 2. I haven't tried imon on 2.4.0-x yet. Maybe other people have? Kindly ignore the boneheaded second half of point 2. --Rusty -- Source code, list archive, and docs: http://oss.sgi.com/projects/fam/ To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com From owner-fam@oss.sgi.com Mon Feb 26 15:33:03 2001 Received: by oss.sgi.com id ; Mon, 26 Feb 2001 15:32:53 -0800 Received: from sgi.SGI.COM ([192.48.153.1]:44671 "EHLO sgi.com") by oss.sgi.com with ESMTP id ; Mon, 26 Feb 2001 15:32:51 -0800 Received: from rlyeh.engr.sgi.com ([198.29.76.98]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id PAA04576 for ; Mon, 26 Feb 2001 15:32:49 -0800 (PST) mail_from (rusty@rlyeh.engr.sgi.com) Received: (from rusty@localhost) by rlyeh.engr.sgi.com (SGI-8.9.3/8.9.3) id PAA19625; Mon, 26 Feb 2001 15:32:59 -0800 (PST) From: "Rusty Ballinger" Message-Id: <10102261532.ZM19621@rlyeh.engr.sgi.com> Date: Mon, 26 Feb 2001 15:32:58 -0800 In-Reply-To: Jerome De Greef "Re: [fam] imon 0.0.[12]-2.4.0-test9 compile error" (Feb 27, 12:24am) References: <20010226231250.A16202@shellc.jdegreef.net> <10102261507.ZM19457@rlyeh.engr.sgi.com> <20010227002436.F16202@shellc.jdegreef.net> X-Face: #)4}U4e`O6YEe%oBzE}>ycmT!Xt?Myiqo~|p3Wh'UuQ[N7)&4\4?8:1n)bmPX]b@#k94%!VojpODdmk:sCr1b\-aXD&P:wjBqupMB:ag6}BwVseJZM@K{$E|0J9}&,Rpdg{&N4/Y8&PTm6>|r[,gI2T*qN!`AZhl>Bdy7JR`dDvP(/pz.}?Q@dg':mlV`RX51Z_ZG?Gta|Q!iA[MaOh Reply-To: rusty@sgi.com X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: jdegreef@brutele.be Subject: Re: [fam] imon 0.0.[12]-2.4.0-test9 compile error Cc: fam@oss.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-fam@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;fam-outgoing > Hum, quoting Documentation/Configure.help (patched): > > " If you don't know whether you want imon, it doesn't do any harm to > say N here. (If you want imon, say M, not Y.)" > > But maybe that's wrong so... "Kindly disregard the boneheaded first half of point 1?" (It has obviously been too long since I've fiddled with imon. I remembered that it works one way and not the other, so when you said it wasn't working as a module, I just assumed that's the way it didn't work, rather than trying to figure out what the problem was.) --Rusty -- Source code, list archive, and docs: http://oss.sgi.com/projects/fam/ To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com From owner-fam@oss.sgi.com Tue Feb 27 01:00:08 2001 Received: by oss.sgi.com id ; Tue, 27 Feb 2001 00:59:48 -0800 Received: from sgi.SGI.COM ([192.48.153.1]:63081 "EHLO sgi.com") by oss.sgi.com with ESMTP id ; Tue, 27 Feb 2001 00:59:23 -0800 Received: from rlyeh.engr.sgi.com ([198.29.76.98]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id AAA02836 for ; Tue, 27 Feb 2001 00:59:21 -0800 (PST) mail_from (rusty@rlyeh.engr.sgi.com) Received: (from rusty@localhost) by rlyeh.engr.sgi.com (SGI-8.9.3/8.9.3) id AAA20365; Tue, 27 Feb 2001 00:59:12 -0800 (PST) From: "Rusty Ballinger" Message-Id: <10102270059.ZM20377@rlyeh.engr.sgi.com> Date: Tue, 27 Feb 2001 00:59:11 -0800 In-Reply-To: "Johan Isacsson" "[fam] Max number of inodes?" (Feb 26, 3:52pm) References: X-Face: #)4}U4e`O6YEe%oBzE}>ycmT!Xt?Myiqo~|p3Wh'UuQ[N7)&4\4?8:1n)bmPX]b@#k94%!VojpODdmk:sCr1b\-aXD&P:wjBqupMB:ag6}BwVseJZM@K{$E|0J9}&,Rpdg{&N4/Y8&PTm6>|r[,gI2T*qN!`AZhl>Bdy7JR`dDvP(/pz.}?Q@dg':mlV`RX51Z_ZG?Gta|Q!iA[MaOh Reply-To: rusty@sgi.com X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: johan@mgon.com Subject: Re: [fam] Max number of inodes? Cc: fam@oss.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-fam@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;fam-outgoing > Is there a limit in the number of inodes that imon can monitor? > I guess it depends on system resources, is there a way to calculate on it? > > The reason i wonder is that i'm having trouble when i try to monitor a > directory that's using 42776 inodes. Hmmm, that is interesting. (Presumably it fails the same way when you monitor 2 directories, each with 42776/2 inodes? Wait... don't bother to check that.) > What happens is this (after a while, i'm having a perl script adding > directories to FAM): > My perl script stops > In the console i get many of theese: > Kmalloc: Size (196608) Too large! > (I have lots of free memory) Hmm, it looks like 131072 is the most you can get from one call to kmalloc. The two places imon allocates memory is when it creates the event queue (which it does once, but the size is configurable), and when it grows the hash table of monitored dev/inode pairs (which it does whenever the table fills up). One thing you might try, which might work around the problem easily: in mm/slab.c, look for that 131072, and try adding some larger entries to cache_sizes and cache_sizes_name. (I have no idea what that might break, whether those sizes are arbitrary, etc. If it does make your machine burst into flames or summon Satan, at least try to videotape it!) If that works, the problem will still be there; it's just that hopefully the limit will be higher than the amount of memory it takes to hash the number of inodes you're monitoring. If that doesn't work (and there's not some kernel-memory-allocation-routine which can give you as much memory as you ask for), I don't know what to try other than to fix imon to handle its hash table being split into non- contiguous blocks of memory, or to use trees, etc. --Rusty -- Source code, list archive, and docs: http://oss.sgi.com/projects/fam/ To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com From owner-fam@oss.sgi.com Tue Feb 27 01:00:48 2001 Received: by oss.sgi.com id ; Tue, 27 Feb 2001 01:00:39 -0800 Received: from sgi.SGI.COM ([192.48.153.1]:14698 "EHLO sgi.com") by oss.sgi.com with ESMTP id ; Tue, 27 Feb 2001 01:00:19 -0800 Received: from rlyeh.engr.sgi.com ([198.29.76.98]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id BAA01274 for ; Tue, 27 Feb 2001 01:00:18 -0800 (PST) mail_from (rusty@rlyeh.engr.sgi.com) Received: (from rusty@localhost) by rlyeh.engr.sgi.com (SGI-8.9.3/8.9.3) id BAA20393; Tue, 27 Feb 2001 01:00:29 -0800 (PST) From: "Rusty Ballinger" Message-Id: <10102270100.ZM20384@rlyeh.engr.sgi.com> Date: Tue, 27 Feb 2001 01:00:28 -0800 In-Reply-To: Atif Ghaffar "[fam] Max number of inodes?" (Feb 26, 5:07pm) References: <3A9A7F5D.2FA7D636@developer.ch> X-Face: #)4}U4e`O6YEe%oBzE}>ycmT!Xt?Myiqo~|p3Wh'UuQ[N7)&4\4?8:1n)bmPX]b@#k94%!VojpODdmk:sCr1b\-aXD&P:wjBqupMB:ag6}BwVseJZM@K{$E|0J9}&,Rpdg{&N4/Y8&PTm6>|r[,gI2T*qN!`AZhl>Bdy7JR`dDvP(/pz.}?Q@dg':mlV`RX51Z_ZG?Gta|Q!iA[MaOh Reply-To: rusty@sgi.com X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: aghaffar@developer.ch Subject: Re: [fam] Max number of inodes? Cc: fam@oss.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-fam@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;fam-outgoing > These are from /var/log/messages (after I start monitoring and trigger > and event such as delete a file) > node2:/usr/src/linux # Feb 26 17:34:00 node2 fam[24076]: imon event > received by fam built without imon support... tell fam@oss.sgi.com to > fix this! > Feb 26 17:34:00 node2 inetd[726]: /usr/local/bin/fam: exit signal 0x6 Just to make sure... did you build your own version of fam on a box which didn't have imon at the time? If so, it won't have found the kernel header it needs for building imon support, so it will have been built without imon support. ("then it shouldn't have opened /dev/imon, right?" Yeah, well... at least this way you know you *could* be using imon if you rebuild fam, rather than polling on a system which has imon.) Anyway, if that's the problem, try rebuilding fam. (You might have to remove config.cache first, and re-run the configure script, and then make.) If the configure test which checks for imon.h fails, it should print out a big warning message. If you didn't build your own version of fam, or you know you built it with imon support, then something else is the problem. :) --Rusty -- Source code, list archive, and docs: http://oss.sgi.com/projects/fam/ To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com From owner-fam@oss.sgi.com Tue Feb 27 02:23:40 2001 Received: by oss.sgi.com id ; Tue, 27 Feb 2001 02:23:30 -0800 Received: from ns.oddjob.se ([194.23.92.14]:9812 "EHLO mail.oddjob.se") by oss.sgi.com with ESMTP id ; Tue, 27 Feb 2001 02:23:04 -0800 Received: from bart.mgon.com ([192.168.0.100] helo=bart) by mail.oddjob.se with smtp (Exim 3.13 #3) id 14XhuD-0006u2-00; Tue, 27 Feb 2001 12:02:57 +0100 From: "Johan Isacsson" To: Cc: Subject: SV: [fam] Max number of inodes? Date: Tue, 27 Feb 2001 11:23:22 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 In-Reply-To: <10102270059.ZM20377@rlyeh.engr.sgi.com> Sender: owner-fam@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;fam-outgoing Hello, I tried to add some entries to cache_sizes and cache_sizes_names but i got a kernel panic upon boot. So i probably missed something. But, it might actually be better to find a better solution to this. I got the impression that the kernel folks don't want the memory size that kmalloc can allocate to be much more than 128k because they are conserned about memory fragmentation. I'm not at all into kernel hacking so i might be wrong about some things here. But one suggestion seems to be to use vmalloc instead of kmalloc since vmalloc donesn't have the same size limitation that kmalloc has (128k). The difference is that vmalloc allocates virtual continous memory insted of physical. Would that be a problem for imon? I guess it's a bit slower... I'll give it a try but as i said, i'm not very good at this, so if anyone else is interested please try it yourself :) Right now we seem to have a limitation in the number of inodes that imon can monitor. You should be able to calculate on it if you know how much memory each inode entry takes up in the hash table. (i don't). I can see a very good use for imon/fam to monitor a filesystem that's being replicated to multiple slaves (webservers) in realtime. This limit is very much in the way for such applications though. Regards, Johan Isacsson MGON > -----Ursprungligt meddelande----- > Fran: Rusty Ballinger [mailto:rusty@rlyeh.engr.sgi.com] > Skickat: den 27 februari 2001 09:59 > Till: johan@mgon.com > Kopia: fam@oss.sgi.com > Amne: Re: [fam] Max number of inodes? > > > > Is there a limit in the number of inodes that imon can monitor? > > I guess it depends on system resources, is there a way to > calculate on it? > > > > The reason i wonder is that i'm having trouble when i try to monitor a > > directory that's using 42776 inodes. > > Hmmm, that is interesting. (Presumably it fails the same way when you > monitor 2 directories, each with 42776/2 inodes? Wait... don't bother to > check that.) > > > What happens is this (after a while, i'm having a perl script adding > > directories to FAM): > > My perl script stops > > In the console i get many of theese: > > Kmalloc: Size (196608) Too large! > > (I have lots of free memory) > > Hmm, it looks like 131072 is the most you can get from one call > to kmalloc. > > The two places imon allocates memory is when it creates the event queue > (which it does once, but the size is configurable), and when it grows the > hash table of monitored dev/inode pairs (which it does whenever the table > fills up). > > One thing you might try, which might work around the problem easily: in > mm/slab.c, look for that 131072, and try adding some larger entries to > cache_sizes and cache_sizes_name. (I have no idea what that might break, > whether those sizes are arbitrary, etc. If it does make your machine > burst into flames or summon Satan, at least try to videotape it!) If that > works, the problem will still be there; it's just that hopefully the limit > will be higher than the amount of memory it takes to hash the number of > inodes you're monitoring. > > If that doesn't work (and there's not some > kernel-memory-allocation-routine > which can give you as much memory as you ask for), I don't know > what to try > other than to fix imon to handle its hash table being split into non- > contiguous blocks of memory, or to use trees, etc. > > --Rusty > -- Source code, list archive, and docs: http://oss.sgi.com/projects/fam/ To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com