From owner-fam@oss.sgi.com Thu May 2 12:53:02 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.3/8.12.3) with ESMTP id g42Jr2wJ013991 for ; Thu, 2 May 2002 12:53:02 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.3/8.12.3/Submit) id g42Jr19q013990 for fam-outgoing; Thu, 2 May 2002 12:53:01 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-fam@oss.sgi.com using -f Received: from sierra.seas.upenn.edu (root@sierra.seas.upenn.edu [158.130.64.180]) by oss.sgi.com (8.12.3/8.12.3) with SMTP id g42JqxwJ013987 for ; Thu, 2 May 2002 12:52:59 -0700 Received: from red.seas.upenn.edu (root@RED.SEAS.UPENN.EDU [158.130.64.176]) by sierra.seas.upenn.edu (8.9.3/8.9.3) with ESMTP id PAA17367 for ; Thu, 2 May 2002 15:53:59 -0400 (EDT) Received: from red.seas.upenn.edu (pgoyal@localhost [127.0.0.1]) by red.seas.upenn.edu (8.12.2/8.12.2) with ESMTP id g42Jrwrp028999 for ; Thu, 2 May 2002 15:53:58 -0400 (EDT) Received: (from pgoyal@localhost) by red.seas.upenn.edu (8.12.2/8.12.2/Submit) id g42Jrwdq028998 for fam@oss.sgi.com; Thu, 2 May 2002 15:53:58 -0400 (EDT) From: Pooja Goyal Message-Id: <200205021953.g42Jrwdq028998@red.seas.upenn.edu> Subject: [fam] Monitoring Subdirectories w/ Fam To: fam@oss.sgi.com Date: Thu, 2 May 2002 15:53:58 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23-upenn3.3] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-fam@oss.sgi.com Precedence: bulk Hi, I was wondering if anyone knew how to monitor subdirectories using FAM. Basically, If I ask FAM to monitor a directory, I want it to monitor all existing subdirectories within it as well. Right now I just get "subdirectory changed" however I want more detailed information like what the change was. Also, if create a new subdirectory in the directory being monitored, I want FAM to start monitoring the new subdirectory as well. Any help will be appreciated. Thanks, Pooja -- 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 Thu May 2 19:02:20 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.3/8.12.3) with ESMTP id g4322KwJ025982 for ; Thu, 2 May 2002 19:02:20 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.3/8.12.3/Submit) id g4322KX3025981 for fam-outgoing; Thu, 2 May 2002 19:02:20 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-fam@oss.sgi.com using -f Received: from nexus.adacel.com (shelob.adacel.com.au [203.36.26.146] (may be forged)) by oss.sgi.com (8.12.3/8.12.3) with SMTP id g43225wJ025975 for ; Thu, 2 May 2002 19:02:08 -0700 Received: (qmail 13389 invoked from network); 3 May 2002 01:56:51 -0000 Received: from unknown (HELO selene) (192.168.75.53) by nexus.adacel.com with SMTP; 3 May 2002 01:56:51 -0000 Message-ID: <00ae01c1f247$7a941750$354ba8c0@wodonga.adacel.com.au> From: "Michael WARDLE" To: "Pooja Goyal" , References: <200205021953.g42Jrwdq028998@red.seas.upenn.edu> Subject: Re: [fam] Monitoring Subdirectories w/ Fam Date: Fri, 3 May 2002 12:08:55 +1000 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_00AB_01C1F29B.4C0DA5A0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-fam@oss.sgi.com Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_00AB_01C1F29B.4C0DA5A0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit ----- Original Message ----- From: "Pooja Goyal" To: Sent: Friday, May 03, 2002 5:53 AM Subject: [fam] Monitoring Subdirectories w/ Fam > I was wondering if anyone knew how to monitor subdirectories using FAM. > Basically, If I ask FAM to monitor a directory, I want it to monitor all > existing subdirectories within it as well. Right now I just get > "subdirectory changed" however I want more detailed information like what > the change was. Also, if create a new subdirectory in the directory being > monitored, I want FAM to start monitoring the new subdirectory as well. > Any help will be appreciated. FAM doesn't monitor subdirectories implicitly. I think you'll have to test if a new file created is a directory, then express an interest in the new directory in your own code. I hope this helps. -- MICHAEL WARDLE SGI Desktop & Admin Software Adacel Technologies Limited ------=_NextPart_000_00AB_01C1F29B.4C0DA5A0 Content-Type: text/x-vcard; name="Michael Wardle.vcf" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="Michael Wardle.vcf" BEGIN:VCARD VERSION:2.1 N:Wardle;Michael FN:Michael Wardle ORG:Adacel Technologies;Global Software Engineering TITLE:Trainee Software Engineer TEL;WORK;VOICE:+61-2-6024-2699 TEL;CELL;VOICE:+61-415-439-838 TEL;WORK;FAX:+61-2-6024-3288 ADR;WORK:;;19 Stanley Street;Wodonga;Victoria;3690;Australia LABEL;WORK;ENCODING=3DQUOTED-PRINTABLE:19 Stanley = Street=3D0D=3D0AWodonga, Victoria 3690=3D0D=3D0AAustralia ADR;HOME:;;;Wodonga;Victoria;3690;Australia LABEL;HOME;ENCODING=3DQUOTED-PRINTABLE:Wodonga, Victoria = 3690=3D0D=3D0AAustralia X-WAB-GENDER:2 URL;HOME:http://www.endbracket.net/ URL;WORK:http://www.softwarecoding.com/ EMAIL;PREF;INTERNET:michael.wardle@adacel.com EMAIL;INTERNET:wardle@adacel.com EMAIL;INTERNET:wardle@sgi.com REV:20020503T020855Z END:VCARD ------=_NextPart_000_00AB_01C1F29B.4C0DA5A0-- -- 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 Fri May 3 17:48:28 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.3/8.12.3) with ESMTP id g440mRwJ000984 for ; Fri, 3 May 2002 17:48:27 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.3/8.12.3/Submit) id g440mRuK000983 for fam-outgoing; Fri, 3 May 2002 17:48:27 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-fam@oss.sgi.com using -f Received: from sierra.seas.upenn.edu (root@sierra.seas.upenn.edu [158.130.64.180]) by oss.sgi.com (8.12.3/8.12.3) with SMTP id g440mPwJ000979 for ; Fri, 3 May 2002 17:48:25 -0700 Received: from blue.seas.upenn.edu (root@BLUE.SEAS.UPENN.EDU [158.130.64.177]) by sierra.seas.upenn.edu (8.9.3/8.9.3) with ESMTP id UAA24154 for ; Fri, 3 May 2002 20:49:31 -0400 (EDT) Received: from blue.seas.upenn.edu (pgoyal@localhost [127.0.0.1]) by blue.seas.upenn.edu (8.12.2/8.12.2) with ESMTP id g440nUj7000688 for ; Fri, 3 May 2002 20:49:30 -0400 (EDT) Received: (from pgoyal@localhost) by blue.seas.upenn.edu (8.12.2/8.12.2/Submit) id g440nUUp000687 for fam@oss.sgi.com; Fri, 3 May 2002 20:49:30 -0400 (EDT) From: Pooja Goyal Message-Id: <200205040049.g440nUUp000687@blue.seas.upenn.edu> Subject: [fam] fam limitations To: fam@oss.sgi.com Date: Fri, 3 May 2002 20:49:30 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23-upenn3.3] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-fam@oss.sgi.com Precedence: bulk hi: could someone please tell me what the key drawbacks of using fam are ? (I believe fam does not allow a single process to monitor more than 1,000 files/directories) also what are alternative programs that can be used in place of fam ? and how does fam compare to them ? thanks! -- 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 May 6 00:34:16 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.3/8.12.3) with ESMTP id g467YGwJ011600 for ; Mon, 6 May 2002 00:34:16 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.3/8.12.3/Submit) id g467YGW1011599 for fam-outgoing; Mon, 6 May 2002 00:34:16 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-fam@oss.sgi.com using -f Received: from nexus.adacel.com (shelob.adacel.com.au [203.36.26.146] (may be forged)) by oss.sgi.com (8.12.3/8.12.3) with SMTP id g467YAwJ011596 for ; Mon, 6 May 2002 00:34:11 -0700 Received: (qmail 5958 invoked from network); 6 May 2002 07:28:45 -0000 Received: from unknown (HELO selene) (192.168.75.53) by nexus.adacel.com with SMTP; 6 May 2002 07:28:45 -0000 Message-ID: <052501c1f4d1$6d1724a0$354ba8c0@wodonga.adacel.com.au> From: "Michael WARDLE" To: "Pooja Goyal" , References: <200205040049.g440nUUp000687@blue.seas.upenn.edu> Subject: Re: [fam] fam limitations Date: Mon, 6 May 2002 17:41:25 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-fam@oss.sgi.com Precedence: bulk ----- Original Message ----- From: "Pooja Goyal" To: Sent: Saturday, May 04, 2002 10:49 AM Subject: [fam] fam limitations > could someone please tell me what the key drawbacks of using > fam are ? (I believe fam does not allow a single process to monitor more > than 1,000 files/directories) I believe this is a limitation of IMon related to a fixed event queue size, so it does not apply when other monitors (such as DNotify) are being used. Given this number is hard-coded in the IMon patch, you could also change that number to a greater one on your systems, but that is not ideal. > also what are alternative programs that can be used in place of > fam ? I don't know of any suitable alternatives. Some systems have their own mechanisms such as kqueue vnode monitoring on FreeBSD, but last I saw, kqueue could only monitor UFS/FFS filesystems, and of course it's not available on other operating systems. Having said this, I'm keen for FAM to support various low-level monitors so it can be as efficient and as widely-available as possible. Regards -- MICHAEL WARDLE SGI Desktop & Admin Software Adacel Technologies Limited -- 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 May 6 02:05:58 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.3/8.12.3) with ESMTP id g4695wwJ012601 for ; Mon, 6 May 2002 02:05:58 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.3/8.12.3/Submit) id g4695wYH012600 for fam-outgoing; Mon, 6 May 2002 02:05:58 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-fam@oss.sgi.com using -f Received: from post.webmailer.de (natwar.webmailer.de [192.67.198.70]) by oss.sgi.com (8.12.3/8.12.3) with SMTP id g4695swJ012597 for ; Mon, 6 May 2002 02:05:54 -0700 Received: from informatik.tu-muenchen.de (A41a7.pppool.de [213.6.65.167]) by post.webmailer.de (8.9.3/8.8.7) with ESMTP id LAA15155 for ; Mon, 6 May 2002 11:07:02 +0200 (MEST) Message-ID: <3CD6480C.9814BE11@informatik.tu-muenchen.de> Date: Mon, 06 May 2002 11:08:28 +0200 From: Christian Kreibich X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.18 i686) X-Accept-Language: en MIME-Version: 1.0 To: fam@oss.sgi.com Subject: Re: [fam] fam limitations References: <200205040049.g440nUUp000687@blue.seas.upenn.edu> <052501c1f4d1$6d1724a0$354ba8c0@wodonga.adacel.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-fam@oss.sgi.com Precedence: bulk Michael WARDLE wrote: > > > could someone please tell me what the key drawbacks of using > > fam are ? (I believe fam does not allow a single process to monitor > more > > than 1,000 files/directories) > > I believe this is a limitation of IMon related to a fixed event queue > size, so it does not apply when other monitors (such as DNotify) are > being used. Given this number is hard-coded in the IMon patch, you > could also change that number to a greater one on your systems, but > that is not ideal. Mhmmm I was under the impression that it's rather a limitation of dnotify, based on the maximum number of open file descriptors, is that incorrect? Cheers, Christian. -- ________________________________________________________________________ http://www.whoop.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 May 6 11:34:49 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.3/8.12.3) with ESMTP id g46IYmwJ027359 for ; Mon, 6 May 2002 11:34:49 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.3/8.12.3/Submit) id g46IYmfm027358 for fam-outgoing; Mon, 6 May 2002 11:34:48 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-fam@oss.sgi.com using -f Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by oss.sgi.com (8.12.3/8.12.3) with SMTP id g46IYiwJ027355 for ; Mon, 6 May 2002 11:34:44 -0700 Received: from localhost (alexl@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) with ESMTP id g46IZuT01279; Mon, 6 May 2002 14:35:56 -0400 X-Authentication-Warning: devserv.devel.redhat.com: alexl owned process doing -bs Date: Mon, 6 May 2002 14:35:56 -0400 (EDT) From: Alex Larsson X-X-Sender: alexl@devserv.devel.redhat.com To: Christian Kreibich cc: fam@oss.sgi.com Subject: Re: [fam] fam limitations In-Reply-To: <3CD6480C.9814BE11@informatik.tu-muenchen.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-fam@oss.sgi.com Precedence: bulk On Mon, 6 May 2002, Christian Kreibich wrote: > Michael WARDLE wrote: > > > > > could someone please tell me what the key drawbacks of using > > > fam are ? (I believe fam does not allow a single process to monitor > > more > > > than 1,000 files/directories) > > > > I believe this is a limitation of IMon related to a fixed event queue > > size, so it does not apply when other monitors (such as DNotify) are > > being used. Given this number is hard-coded in the IMon patch, you > > could also change that number to a greater one on your systems, but > > that is not ideal. > > Mhmmm I was under the impression that it's rather a limitation of > dnotify, based on the maximum number of open file descriptors, is that > incorrect? dnotify does indeed have a problem with the maximum number of open file descriptors. The maximum is larger than 1000 though, being 8192 by default in recent linux kernels and changeable by root. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Alexander Larsson Red Hat, Inc alexl@redhat.com alla@lysator.liu.se He's a war-weary shark-wrestling rock star with acid for blood. She's a sharp-shooting blonde traffic cop with an evil twin sister. They fight crime! -- 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 Fri May 17 10:12:32 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.3/8.12.3) with ESMTP id g4HHCWnC011029 for ; Fri, 17 May 2002 10:12:32 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.3/8.12.3/Submit) id g4HHCWlu011028 for fam-outgoing; Fri, 17 May 2002 10:12:32 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-fam@oss.sgi.com using -f Received: from Princeton.EDU (postoffice.Princeton.EDU [128.112.129.120]) by oss.sgi.com (8.12.3/8.12.3) with SMTP id g4HHCUnC011025 for ; Fri, 17 May 2002 10:12:30 -0700 Received: from smtpserver1.Princeton.EDU (smtpserver1.Princeton.EDU [128.112.129.65]) by Princeton.EDU (8.12.3/8.12.3) with ESMTP id g4HHBSkt028857 for ; Fri, 17 May 2002 13:11:28 -0400 (EDT) Received: from boater.Princeton.EDU (boater.Princeton.EDU [128.112.129.189]) by smtpserver1.Princeton.EDU (8.12.2/8.12.2) with ESMTP id g4HHBRQG027268 for ; Fri, 17 May 2002 13:11:27 -0400 (EDT) Date: Fri, 17 May 2002 13:11:26 -0400 (EDT) From: Ashish Gupta To: fam@oss.sgi.com Subject: [fam] fam floods network Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-fam@oss.sgi.com Precedence: bulk Hi, fam-2.6.4-11 (Redhat 7.2) is flooding the network. Whole bandwidth is consumed by fam. Earlier it was working fine without any problem. problem started when we mounted a nfs filesystem on this machine. nfs server is also running fam. any solution ?? TIA Ashish -- 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 Fri May 17 11:22:45 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.3/8.12.3) with ESMTP id g4HIMjnC012845 for ; Fri, 17 May 2002 11:22:45 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.3/8.12.3/Submit) id g4HIMiok012844 for fam-outgoing; Fri, 17 May 2002 11:22:44 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-fam@oss.sgi.com using -f Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by oss.sgi.com (8.12.3/8.12.3) with SMTP id g4HIMfnC012836 for ; Fri, 17 May 2002 11:22:41 -0700 Received: from localhost (alexl@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) with ESMTP id g4HINAU18706; Fri, 17 May 2002 14:23:10 -0400 X-Authentication-Warning: devserv.devel.redhat.com: alexl owned process doing -bs Date: Fri, 17 May 2002 14:23:10 -0400 (EDT) From: Alex Larsson X-X-Sender: alexl@devserv.devel.redhat.com To: Ashish Gupta cc: fam@oss.sgi.com Subject: Re: [fam] fam floods network In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-fam@oss.sgi.com Precedence: bulk On Fri, 17 May 2002, Ashish Gupta wrote: > Hi, > fam-2.6.4-11 (Redhat 7.2) is flooding the network. Whole bandwidth is > consumed by fam. Earlier it was working fine without any problem. problem > started when we mounted a nfs filesystem on this machine. nfs server is also > running fam. any solution ?? Did you do any changes? By default the fam server shipped with RedHat only listens to the loopback device. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Alexander Larsson Red Hat, Inc alexl@redhat.com alla@lysator.liu.se He's a maverick neurotic werewolf who hangs with the wrong crowd. She's a chain-smoking red-headed barmaid on the trail of a serial killer. They fight crime! -- 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 Fri May 17 11:57:08 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.3/8.12.3) with ESMTP id g4HIv8nC013695 for ; Fri, 17 May 2002 11:57:08 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.3/8.12.3/Submit) id g4HIv8Wa013694 for fam-outgoing; Fri, 17 May 2002 11:57:08 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-fam@oss.sgi.com using -f Received: from Princeton.EDU (postoffice.Princeton.EDU [128.112.129.120]) by oss.sgi.com (8.12.3/8.12.3) with SMTP id g4HIuvnC013687 for ; Fri, 17 May 2002 11:56:57 -0700 Received: from smtpserver2.Princeton.EDU (smtpserver2.Princeton.EDU [128.112.129.148]) by Princeton.EDU (8.12.3/8.12.3) with ESMTP id g4HIrGZs015330; Fri, 17 May 2002 14:53:16 -0400 (EDT) Received: from boater.Princeton.EDU (boater.Princeton.EDU [128.112.129.189]) by smtpserver2.Princeton.EDU (8.12.2/8.12.2) with ESMTP id g4HIrGw1002160; Fri, 17 May 2002 14:53:16 -0400 (EDT) Date: Fri, 17 May 2002 14:53:16 -0400 (EDT) From: Ashish Gupta To: Alex Larsson cc: fam@oss.sgi.com Subject: Re: [fam] fam floods network In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-fam@oss.sgi.com Precedence: bulk Hi Alex, I have not changed any configuration files for fam. Here are some files. nfserver:/etc/fam.conf insecure_compatibility = false untrusted_user = nobody local_only = false xtab_verification = true nfsclient:/etc/fam.conf insecure_compatibility = false untrusted_user = nobody local_only = false xtab_verification = true nfsserver:/etc/xinet.d/sgi_fam # default: on # description: FAM is a file monitoring daemon. It can \ # be used to get reports when files change. service sgi_fam { type = RPC UNLISTED socket_type = stream user = root group = nobody server = /usr/bin/fam wait = yes protocol = tcp rpc_version = 2 rpc_number = 391002 bind = 127.0.0.1 } nfsclient:/etc/xinetd.d/sgi_fam # default: on # description: FAM is a file monitoring daemon. It can \ # be used to get reports when files change. service sgi_fam { type = RPC UNLISTED socket_type = stream user = root group = nobody server = /usr/bin/fam wait = yes protocol = tcp rpc_version = 2 rpc_number = 391002 bind = 127.0.0.1 } # netstat -a -n | grep 32770 tcp 0 0 127.0.0.1:32770 0.0.0.0:* LISTEN udp 0 0 0.0.0.0:32770 0.0.0.0:* Ashish On Fri, 17 May 2002, Alex Larsson wrote: > On Fri, 17 May 2002, Ashish Gupta wrote: > > > Hi, > > fam-2.6.4-11 (Redhat 7.2) is flooding the network. Whole bandwidth is > > consumed by fam. Earlier it was working fine without any problem. problem > > started when we mounted a nfs filesystem on this machine. nfs server is also > > running fam. any solution ?? > > Did you do any changes? By default the fam server shipped with RedHat only > listens to the loopback device. > > -- > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Alexander Larsson Red Hat, Inc > alexl@redhat.com alla@lysator.liu.se > He's a maverick neurotic werewolf who hangs with the wrong crowd. She's a > chain-smoking red-headed barmaid on the trail of a serial killer. They fight > crime! > > -- 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 Fri May 17 15:59:42 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.3/8.12.3) with ESMTP id g4HMxgnC017898 for ; Fri, 17 May 2002 15:59:42 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.3/8.12.3/Submit) id g4HMxg5c017897 for fam-outgoing; Fri, 17 May 2002 15:59:42 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-fam@oss.sgi.com using -f Received: from devserv.devel.redhat.com (nat-pool-rdu.redhat.com [66.187.233.200]) by oss.sgi.com (8.12.3/8.12.3) with SMTP id g4HMxWnC017880 for ; Fri, 17 May 2002 15:59:32 -0700 Received: from localhost (alexl@localhost) by devserv.devel.redhat.com (8.11.6/8.11.0) with ESMTP id g4HN03f07557; Fri, 17 May 2002 19:00:03 -0400 X-Authentication-Warning: devserv.devel.redhat.com: alexl owned process doing -bs Date: Fri, 17 May 2002 19:00:03 -0400 (EDT) From: Alex Larsson X-X-Sender: alexl@devserv.devel.redhat.com To: Ashish Gupta cc: fam@oss.sgi.com Subject: Re: [fam] fam floods network In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-fam@oss.sgi.com Precedence: bulk On Fri, 17 May 2002, Ashish Gupta wrote: > Hi Alex, > > I have not changed any configuration files for fam. > Here are some files. > > nfserver:/etc/fam.conf > > insecure_compatibility = false > untrusted_user = nobody > local_only = false > xtab_verification = true > > nfsclient:/etc/fam.conf > > insecure_compatibility = false > untrusted_user = nobody > local_only = false > xtab_verification = true > > > nfsserver:/etc/xinet.d/sgi_fam > > # default: on > # description: FAM is a file monitoring daemon. It can \ > # be used to get reports when files change. > service sgi_fam > { > type = RPC UNLISTED > socket_type = stream > user = root > group = nobody > server = /usr/bin/fam > wait = yes > protocol = tcp > rpc_version = 2 > rpc_number = 391002 > bind = 127.0.0.1 This line binds the server to only listen to requests on the interface that has 127.0.0.1, i.e. the lo0. There is no way this fam will listen to network requests > } > > nfsclient:/etc/xinetd.d/sgi_fam > > # default: on > # description: FAM is a file monitoring daemon. It can \ > # be used to get reports when files change. > service sgi_fam > { > type = RPC UNLISTED > socket_type = stream > user = root > group = nobody > server = /usr/bin/fam > wait = yes > protocol = tcp > rpc_version = 2 > rpc_number = 391002 > bind = 127.0.0.1 > } > > # netstat -a -n | grep 32770 > tcp 0 0 127.0.0.1:32770 0.0.0.0:* LISTEN > udp 0 0 0.0.0.0:32770 0.0.0.0:* As can be seen here. Only port that listens is on loopback. I dunno what the udp line means though. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Alexander Larsson Red Hat, Inc alexl@redhat.com alla@lysator.liu.se He's a lounge-singing white trash Green Beret on a search for his missing sister. She's a blind goth schoolgirl with the soul of a mighty warrior. They fight crime! -- 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 Fri May 17 17:00:19 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.3/8.12.3) with ESMTP id g4I00JnC018441 for ; Fri, 17 May 2002 17:00:19 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.3/8.12.3/Submit) id g4I00JU8018440 for fam-outgoing; Fri, 17 May 2002 17:00:19 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-fam@oss.sgi.com using -f Received: from Princeton.EDU (postoffice.Princeton.EDU [128.112.129.120]) by oss.sgi.com (8.12.3/8.12.3) with SMTP id g4I007nC018436 for ; Fri, 17 May 2002 17:00:07 -0700 Received: from smtpserver2.Princeton.EDU (smtpserver2.Princeton.EDU [128.112.129.148]) by Princeton.EDU (8.12.3/8.12.3) with ESMTP id g4I007Zs029744; Fri, 17 May 2002 20:00:08 -0400 (EDT) Received: from boater.Princeton.EDU (boater.Princeton.EDU [128.112.129.189]) by smtpserver2.Princeton.EDU (8.12.2/8.12.2) with ESMTP id g4I007w1016178; Fri, 17 May 2002 20:00:07 -0400 (EDT) Date: Fri, 17 May 2002 20:00:06 -0400 (EDT) From: Ashish Gupta To: Alex Larsson cc: fam@oss.sgi.com Subject: Re: [fam] fam floods network In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-fam@oss.sgi.com Precedence: bulk I have changed /etc/xinetd.d/sgi_fam on nfsserver and bind = nfsserver's ipaddress. and netstat is showing fam was able bind to given ip. but still tcpdump is showing hundreads of nfs.access messages due to fam. My solution (although i donot like it) is to disable fam. some applications will be affected which are using fam but at least we are able to work. Thanks a lot Ashish Gupta On Fri, 17 May 2002, Alex Larsson wrote: > On Fri, 17 May 2002, Ashish Gupta wrote: > > > Hi Alex, > > > > I have not changed any configuration files for fam. > > Here are some files. > > > > nfserver:/etc/fam.conf > > > > insecure_compatibility = false > > untrusted_user = nobody > > local_only = false > > xtab_verification = true > > > > nfsclient:/etc/fam.conf > > > > insecure_compatibility = false > > untrusted_user = nobody > > local_only = false > > xtab_verification = true > > > > > > nfsserver:/etc/xinet.d/sgi_fam > > > > # default: on > > # description: FAM is a file monitoring daemon. It can \ > > # be used to get reports when files change. > > service sgi_fam > > { > > type = RPC UNLISTED > > socket_type = stream > > user = root > > group = nobody > > server = /usr/bin/fam > > wait = yes > > protocol = tcp > > rpc_version = 2 > > rpc_number = 391002 > > bind = 127.0.0.1 > > This line binds the server to only listen to requests on the interface > that has 127.0.0.1, i.e. the lo0. There is no way this fam will listen to > network requests > > > } > > > > nfsclient:/etc/xinetd.d/sgi_fam > > > > # default: on > > # description: FAM is a file monitoring daemon. It can \ > > # be used to get reports when files change. > > service sgi_fam > > { > > type = RPC UNLISTED > > socket_type = stream > > user = root > > group = nobody > > server = /usr/bin/fam > > wait = yes > > protocol = tcp > > rpc_version = 2 > > rpc_number = 391002 > > bind = 127.0.0.1 > > } > > > > # netstat -a -n | grep 32770 > > tcp 0 0 127.0.0.1:32770 0.0.0.0:* LISTEN > > udp 0 0 0.0.0.0:32770 0.0.0.0:* > > As can be seen here. Only port that listens is on loopback. > > I dunno what the udp line means though. > > -- > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Alexander Larsson Red Hat, Inc > alexl@redhat.com alla@lysator.liu.se > He's a lounge-singing white trash Green Beret on a search for his missing > sister. She's a blind goth schoolgirl with the soul of a mighty warrior. They > fight crime! > > -- 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 Thu May 23 11:50:23 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.3/8.12.3) with ESMTP id g4NIoNnC028608 for ; Thu, 23 May 2002 11:50:23 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.3/8.12.3/Submit) id g4NIoNqa028607 for fam-outgoing; Thu, 23 May 2002 11:50:23 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-fam@oss.sgi.com using -f Received: from mx1.ovh.net (b1.ovh.net [213.186.33.51]) by oss.sgi.com (8.12.3/8.12.3) with SMTP id g4NIoGnC028604 for ; Thu, 23 May 2002 11:50:17 -0700 Received: (qmail 13910 invoked by uid 503); 23 May 2002 18:51:47 -0000 Received: from unknown (HELO localhost) (80.13.113.66) by ns0.ovh.net with DES-CBC3-SHA encrypted SMTP; 23 May 2002 18:51:47 -0000 Date: Thu, 23 May 2002 20:53:34 +0200 Mime-Version: 1.0 (Apple Message framework v481) Content-Type: text/plain; charset=US-ASCII; format=flowed Subject: [fam] Using fam correctly From: "=?ISO-8859-1?Q?Unit=E9_d'Ombre?=" To: fam@oss.sgi.com Content-Transfer-Encoding: 7bit Message-Id: <6250CC48-6E7E-11D6-9347-003065BA6A54@10191.com> X-Mailer: Apple Mail (2.481) Sender: owner-fam@oss.sgi.com Precedence: bulk Hello, I'm on OSX. Someone on the Dawring Project has ported fam (quickly port) on OSX. I want to use it for my project but i have some strange behaviors with my test app : 1- Copying the test.c++ code (from the file inside the fam package) i create a new OS X application. It appears i can't send more than about 130 (sometimes 129...or 133) requests at once ; my app. suddenly freezes (no crash) and i have no messages from fam (even in debug mode). Each of my requests is for monitoring a directory. I could break this limit of 130 doing this (tr is an array) : - Collect all directories - Open fam - Fill tr (array) with 100 elements - sendRequest (with tr) - start the event loop (looking for fam events : changed, created and so on). ->for all my directories : --> fill tr with other 100 elements --> sendRequest (the last 100 elements only). Now i can monitor about 1000 directories (in fact all my files in my home directories)...but i think it's not a good approach (see (2)). Can you confirm ? 2- When i send all of my directories my event loop received changed events for all my files in my home dir. These events never stop. It's like if all my files were changed continuously. If i create of delete a file i have the appropriate message. Is it normal to have all these changed events ? Is there a way to purge the event queue ? Thx for your help. Chris. -- 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 Fri May 24 14:54:56 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.3/8.12.3) with ESMTP id g4OLsunC019953 for ; Fri, 24 May 2002 14:54:56 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.3/8.12.3/Submit) id g4OLsunb019952 for fam-outgoing; Fri, 24 May 2002 14:54:56 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-fam@oss.sgi.com using -f Received: from sgi.com (sgi-too.SGI.COM [204.94.211.39]) by oss.sgi.com (8.12.3/8.12.3) with SMTP id g4OLspnC019949 for ; Fri, 24 May 2002 14:54:51 -0700 Received: from mailout07.sul.t-online.com (mailout07.sul.t-online.com [194.25.134.83]) 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 OAA02849 for ; Fri, 24 May 2002 14:55:38 -0700 (PDT) mail_from (f_bachmann@t-online.de) Received: from fwd07.sul.t-online.de by mailout07.sul.t-online.com with smtp id 17BMsA-00059K-06; Fri, 24 May 2002 23:45:18 +0200 Received: from dante.local.net (520067937201-0001@[217.81.161.27]) by fwd07.sul.t-online.com with esmtp id 17BMs7-1yHXQOC; Fri, 24 May 2002 23:45:15 +0200 From: f_bachmann@t-online.de (Florian Bachmann) To: fam@oss.sgi.com Subject: [fam] Some Questions Date: Fri, 24 May 2002 23:45:19 +0200 User-Agent: KMail/1.4.5 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline Message-Id: <200205242345.19143.f_bachmann@t-online.de> X-Sender: 520067937201-0001@t-dialin.net Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id g4OLspnC019950 Sender: owner-fam@oss.sgi.com Precedence: bulk Hi, I am new to FAM so please forgive me if pose questions that have been asked many times. 1) What is the current status of imon? Will it be maintained for upcoming kernel releases, are there alternatives, etc. 2) Are there any reliable statistics on how many monitored files/directories FAM can handle at a time (both local and networked filesystems)? Is it really feasible to use FAM on some hundreds of files at a time, or should I just forget about that? 3) >From the INSTALL file in the distribution archive: "The install target doesn't modify your configuration files; you'll have to do this yourself". Yet, after running make install I found that /etc/rpc and /etc/inetd.conf had been modified. Hmmm.... I may be paranoid but this gives me a bad feeling. Kind regards -- Florian Bachmann -- 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 Sun May 26 16:31:50 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.3/8.12.3) with ESMTP id g4QNVonC023804 for ; Sun, 26 May 2002 16:31:50 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.3/8.12.3/Submit) id g4QNVovN023803 for fam-outgoing; Sun, 26 May 2002 16:31:50 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-fam@oss.sgi.com using -f Received: from nexus.adacel.com (shelob.adacel.com.au [203.36.26.146] (may be forged)) by oss.sgi.com (8.12.3/8.12.3) with SMTP id g4QNVanC023799 for ; Sun, 26 May 2002 16:31:39 -0700 Received: (qmail 25238 invoked from network); 26 May 2002 23:23:55 -0000 Received: from unknown (HELO adacel.com) (192.168.75.53) by nexus.adacel.com with SMTP; 26 May 2002 23:23:54 -0000 Message-ID: <3CF17238.5070903@adacel.com> Date: Mon, 27 May 2002 09:39:36 +1000 From: Michael Wardle Organization: Adacel Technologies User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc2) Gecko/20020512 Netscape/7.0b1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Florian Bachmann CC: fam@oss.sgi.com Subject: Re: [fam] Some Questions References: <200205242345.19143.f_bachmann@t-online.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-fam@oss.sgi.com Precedence: bulk Florian Bachmann wrote: > 1) > What is the current status of imon? Will it be maintained for upcoming > kernel releases, are there alternatives, etc. I believe I have answered this question a few times here, and it's also partially mentioned in the FAQ. You may want to read back thru the mailing list http://oss.sgi.com/projects/fam/mail.html and the FAQ http://oss.sgi.com/projects/fam/faq.html to see full answers to these questions. Here's a few URLs that might help you: http://oss.sgi.com/projects/fam/faq.html#what_os_imon http://oss.sgi.com/projects/fam/archive/msg00394.html http://oss.sgi.com/projects/fam/archive/msg00424.html To answer your question briefly: IMon is still alive, but I'm not maintaining it. DNotify is an alternative that's now available in official Linux kernels, so that is what I'd recommend using. I'll soon merge Alex Larsson's DNotify patch into our tree, but until then, you can get the DNotify patch from: ftp://oss.sgi.com/projects/fam/download/contrib/dnotify.patch As usual, get a copy of the FAM distribution (sources), extract the files, and run "patch -p1 < /path/to/dnotify.patch" to apply the patch. > 2) > Are there any reliable statistics on how many monitored files/directories FAM > can handle at a time (both local and networked filesystems)? Is it really > feasible to use FAM on some hundreds of files at a time, or should I just > forget about that? I think there is a limitation meaning that no more than 1024 files can be monitored simultaneously, but this may be a limitation of the kernel monitor (such as IMon) rather than a limitation of FAM. I would appreciate if somebody could provide a more definitive answer. > 3) >>From the INSTALL file in the distribution archive: "The install target doesn't > modify your configuration files; you'll have to do this yourself". Yet, after > running make install I found that /etc/rpc and /etc/inetd.conf had been > modified. Hmmm.... I may be paranoid but this gives me a bad feeling. The statement in INSTALL is incorrect. The former maintainer (Rusty) did some work with something called "editconf" that manipulated the necessary files to make FAM work thru inetd. Provided that your configuration files were modified in accordance with the instructions in INSTALL, then there's little need to worry that your version was modified. I'm planning on removing the existing "make install" target and replacing it with something simpler, but there's a few people at SGI that still need the target as it is. This topic is also mentioned in the FAM FAQ, but I apologize for the inconsistency. -- MICHAEL WARDLE SGI Desktop & Admin Software Adacel Technologies Limited -- 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 May 27 04:30:26 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.3/8.12.3) with ESMTP id g4RBUQnC004648 for ; Mon, 27 May 2002 04:30:26 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.3/8.12.3/Submit) id g4RBUQB6004647 for fam-outgoing; Mon, 27 May 2002 04:30:26 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-fam@oss.sgi.com using -f Received: from mailout06.sul.t-online.com (mailout06.sul.t-online.com [194.25.134.19]) by oss.sgi.com (8.12.3/8.12.3) with SMTP id g4RBUNnC004644 for ; Mon, 27 May 2002 04:30:24 -0700 Received: from fwd11.sul.t-online.de by mailout06.sul.t-online.com with smtp id 17CIic-0003tn-01; Mon, 27 May 2002 13:31:18 +0200 Received: from dante.local.net (520067937201-0001@[80.128.177.132]) by fwd11.sul.t-online.com with esmtp id 17CIiX-1sxpmiC; Mon, 27 May 2002 13:31:13 +0200 From: f_bachmann@t-online.de (Florian Bachmann) To: Michael Wardle Subject: Re: [fam] Some Questions Date: Mon, 27 May 2002 13:31:27 +0200 User-Agent: KMail/1.4.5 Cc: fam@oss.sgi.com References: <200205242345.19143.f_bachmann@t-online.de> <3CF17238.5070903@adacel.com> In-Reply-To: <3CF17238.5070903@adacel.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Message-Id: <200205271331.27068.f_bachmann@t-online.de> X-Sender: 520067937201-0001@t-dialin.net Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id g4RBUOnC004645 Sender: owner-fam@oss.sgi.com Precedence: bulk Thanks for your quick response. I really should have consulted the FAQ first, sorry for the inconvenience. Kind regards -- Florian Bachmann -- 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 May 27 19:50:25 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.3/8.12.3) with ESMTP id g4S2oPnC031865 for ; Mon, 27 May 2002 19:50:25 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.3/8.12.3/Submit) id g4S2oPi7031864 for fam-outgoing; Mon, 27 May 2002 19:50:25 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-fam@oss.sgi.com using -f Received: from ns.snowman.net (ns.snowman.net [63.80.4.34]) by oss.sgi.com (8.12.3/8.12.3) with SMTP id g4S2oKnC031853 for ; Mon, 27 May 2002 19:50:20 -0700 Received: from ns.snowman.net (localhost [127.0.0.1]) by ns.snowman.net (8.12.3/8.12.3/Debian -4) with ESMTP id g4S2pZjT012244 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Mon, 27 May 2002 22:51:35 -0400 Received: (from pabs@localhost) by ns.snowman.net (8.12.3/8.12.3/Debian -4) id g4S2pZWK012242 for fam@oss.sgi.com; Mon, 27 May 2002 22:51:35 -0400 Date: Mon, 27 May 2002 22:51:35 -0400 From: Paul Duncan To: fam@oss.sgi.com Subject: [fam] [ANN] FAM-Ruby 0.1.0 Message-ID: <20020528025135.GG15856@ns> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="KDt/GgjP6HVcx58l" Content-Disposition: inline User-Agent: Mutt/1.3.28i X-Info: http://www.pablotron.org/ Sender: owner-fam@oss.sgi.com Precedence: bulk --KDt/GgjP6HVcx58l Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, I just posted the initial release of my FAM bindings for the scripting language Ruby (http://www.ruby-lang.org/). Please CC me questions or comments, as I am not subscribed to the FAM mailing list. Project Page: http://www.pablotron.org/software/fam-ruby/ Download: http://www.pablotron.org/download/fam-ruby-0.1.0.tar.gz --=20 Paul Duncan pabs in #gah (OPN IRC) http://www.pablotron.org/ OpenPGP Key ID: 0x82C29562 --KDt/GgjP6HVcx58l Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE88vC3zdlT34LClWIRAjiBAKCdT9vWTbEw60XEJfIUKNk3WyD0HgCgzHuS 0y/V8eDxXmoK1daCDgIPiWg= =tRSv -----END PGP SIGNATURE----- --KDt/GgjP6HVcx58l-- -- 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 May 28 03:11:27 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.3/8.12.3) with ESMTP id g4SABRnC011255 for ; Tue, 28 May 2002 03:11:27 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.3/8.12.3/Submit) id g4SABRDg011254 for fam-outgoing; Tue, 28 May 2002 03:11:27 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-fam@oss.sgi.com using -f Received: from deborah.paradise.net.nz (deborah.paradise.net.nz [203.96.152.32]) by oss.sgi.com (8.12.3/8.12.3) with SMTP id g4SABNnC011251 for ; Tue, 28 May 2002 03:11:24 -0700 Received: from oregano.parkerpechan.co.nz (203-79-125-118.adsl.paradise.net.nz [203.79.125.118]) by deborah.paradise.net.nz (Postfix) with ESMTP id 7218FD2537 for ; Tue, 28 May 2002 01:02:23 +1200 (NZST) Received: from basil.parkerpechan.co.nz (basil.parkerpechan.co.nz [192.168.0.4]) by oregano.parkerpechan.co.nz (8.11.6/8.11.6) with ESMTP id g4RD2MZ32168 for ; Tue, 28 May 2002 01:02:22 +1200 Content-Type: text/plain; charset="us-ascii" From: Lars Pechan To: fam@oss.sgi.com Subject: [fam] GCC-3.1 compilation problems... Date: Tue, 28 May 2002 01:02:17 +1200 X-Mailer: KMail [version 1.4] MIME-Version: 1.0 Message-Id: <200205280102.18620.lars.pechan@paradise.net.nz> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id g4SABOnC011252 Sender: owner-fam@oss.sgi.com Precedence: bulk Hello, I'm trying to build fam-oss 2.6.7 using Gentoo Linux i386 with gcc3.1 and get the following output: c++ -DHAVE_CONFIG_H -I. -I. -I.. -I../include -DCONFIG_ETC_CONFIG_PATH=\"/etc/fam.conf\" -Wno-deprecated -c Scheduler.c++ Scheduler.c++:37: uninitialized const member `Scheduler::IOTypeInfo::iotype' Scheduler.c++:38: uninitialized const member `Scheduler::IOTypeInfo::iotype' make[2]: *** [Scheduler.o] Error 1 make[2]: Leaving directory `/var/tmp/portage/fam-oss-2.6.7/work/fam-2.6.7/fam' Any known workarounds or planned fixes in the pipeline? Thanks, /Lasse -- 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 May 28 07:04:59 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.3/8.12.3) with ESMTP id g4SE4xnC021892 for ; Tue, 28 May 2002 07:04:59 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.3/8.12.3/Submit) id g4SE4xWu021891 for fam-outgoing; Tue, 28 May 2002 07:04:59 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-fam@oss.sgi.com using -f Received: from deborah.paradise.net.nz (deborah.paradise.net.nz [203.96.152.32]) by oss.sgi.com (8.12.3/8.12.3) with SMTP id g4SE4tnC021887 for ; Tue, 28 May 2002 07:04:55 -0700 Received: from oregano.parkerpechan.co.nz (203-79-125-118.adsl.paradise.net.nz [203.79.125.118]) by deborah.paradise.net.nz (Postfix) with ESMTP id A68ECD3054 for ; Tue, 28 May 2002 10:45:33 +1200 (NZST) Received: from basil.parkerpechan.co.nz (basil.parkerpechan.co.nz [192.168.0.4]) by oregano.parkerpechan.co.nz (8.11.6/8.11.6) with ESMTP id g4RMjWZ08436 for ; Tue, 28 May 2002 10:45:32 +1200 Content-Type: text/plain; charset="us-ascii" From: Lars Pechan To: fam@oss.sgi.com Subject: [fam] GCC-3.1 compilation problems... Date: Tue, 28 May 2002 01:02:17 +1200 X-Mailer: KMail [version 1.4] MIME-Version: 1.0 Message-Id: <200205280102.18620.lars.pechan@paradise.net.nz> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id g4SE4unC021888 Sender: owner-fam@oss.sgi.com Precedence: bulk Hello, I'm trying to build fam-oss 2.6.7 using Gentoo Linux i386 with gcc3.1 and get the following output: c++ -DHAVE_CONFIG_H -I. -I. -I.. -I../include -DCONFIG_ETC_CONFIG_PATH=\"/etc/fam.conf\" -Wno-deprecated -c Scheduler.c++ Scheduler.c++:37: uninitialized const member `Scheduler::IOTypeInfo::iotype' Scheduler.c++:38: uninitialized const member `Scheduler::IOTypeInfo::iotype' make[2]: *** [Scheduler.o] Error 1 make[2]: Leaving directory `/var/tmp/portage/fam-oss-2.6.7/work/fam-2.6.7/fam' Any known workarounds or planned fixes in the pipeline? Thanks, /Lasse -- 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 May 28 15:56:45 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.3/8.12.3) with ESMTP id g4SMujnC032127 for ; Tue, 28 May 2002 15:56:45 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.3/8.12.3/Submit) id g4SMuj8E032126 for fam-outgoing; Tue, 28 May 2002 15:56:45 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-fam@oss.sgi.com using -f Received: from nexus.adacel.com (shelob.adacel.com.au [203.36.26.146] (may be forged)) by oss.sgi.com (8.12.3/8.12.3) with SMTP id g4SMuenC032123 for ; Tue, 28 May 2002 15:56:41 -0700 Received: (qmail 11654 invoked from network); 28 May 2002 22:48:56 -0000 Received: from unknown (HELO adacel.com) (192.168.75.53) by nexus.adacel.com with SMTP; 28 May 2002 22:48:56 -0000 Message-ID: <3CF40D13.80101@adacel.com> Date: Wed, 29 May 2002 09:04:51 +1000 From: Michael Wardle Organization: Adacel Technologies User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc2) Gecko/20020512 Netscape/7.0b1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Lars Pechan CC: fam@oss.sgi.com Subject: Re: [fam] GCC-3.1 compilation problems... References: <200205280102.18620.lars.pechan@paradise.net.nz> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-fam@oss.sgi.com Precedence: bulk Hi Lars Lars Pechan wrote: > I'm trying to build fam-oss 2.6.7 using Gentoo Linux i386 with gcc3.1 and get > the following output: > > c++ -DHAVE_CONFIG_H -I. -I. -I.. -I../include > -DCONFIG_ETC_CONFIG_PATH=\"/etc/fam.conf\" -Wno-deprecated -c > Scheduler.c++ > Scheduler.c++:37: uninitialized const member `Scheduler::IOTypeInfo::iotype' > Scheduler.c++:38: uninitialized const member `Scheduler::IOTypeInfo::iotype' > make[2]: *** [Scheduler.o] Error 1 > make[2]: Leaving directory `/var/tmp/portage/fam-oss-2.6.7/work/fam-2.6.7/fam' The latest tree builds fine with GCC 3.0.4 with default arguments, and nothing's been changed in the scheduler recently. Perhaps the -Wno-deprecated is making the problem surface. -- MICHAEL WARDLE SGI Desktop & Admin Software Adacel Technologies Limited -- 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 May 28 20:26:49 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.3/8.12.3) with ESMTP id g4T3QnnC003432 for ; Tue, 28 May 2002 20:26:49 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.3/8.12.3/Submit) id g4T3QnCL003431 for fam-outgoing; Tue, 28 May 2002 20:26:49 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-fam@oss.sgi.com using -f Received: from nexus.adacel.com (shelob.adacel.com.au [203.36.26.146] (may be forged)) by oss.sgi.com (8.12.3/8.12.3) with SMTP id g4T3QinC003428 for ; Tue, 28 May 2002 20:26:45 -0700 Received: (qmail 8616 invoked from network); 29 May 2002 03:19:00 -0000 Received: from unknown (HELO adacel.com) (192.168.75.53) by nexus.adacel.com with SMTP; 29 May 2002 03:18:59 -0000 Message-ID: <3CF44C5F.3020807@adacel.com> Date: Wed, 29 May 2002 13:34:55 +1000 From: Michael Wardle Organization: Adacel Technologies User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc2) Gecko/20020512 Netscape/7.0b1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ashish Gupta CC: fam@oss.sgi.com Subject: Re: [fam] fam floods network References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-fam@oss.sgi.com Precedence: bulk Ashish Gupta wrote: > Hi, fam-2.6.4-11 (Redhat 7.2) is flooding the network. Whole > bandwidth is consumed by fam. Earlier it was working fine without any > problem. problem started when we mounted a nfs filesystem on this > machine. nfs server is also running fam. any solution ?? 1. Configure FAM on the remote machine to accept FAM requests from your machine (assuming it is not currently). 2. Try changing the NFS polling interval to something less frequent with the -t option. Could you quantify the traffic levels you're seeing over your network? What is the bandwidth or maximum transfer rate of your network? If FAM is making your network unusable, this could be a bug. I hope this helps -- MICHAEL WARDLE SGI Desktop & Admin Software Adacel Technologies Limited -- 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 May 28 22:28:21 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.3/8.12.3) with ESMTP id g4T5SKnC006540 for ; Tue, 28 May 2002 22:28:20 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.3/8.12.3/Submit) id g4T5SK5Q006539 for fam-outgoing; Tue, 28 May 2002 22:28:20 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-fam@oss.sgi.com using -f Received: from nexus.adacel.com (shelob.adacel.com.au [203.36.26.146] (may be forged)) by oss.sgi.com (8.12.3/8.12.3) with SMTP id g4T5SGnC006536 for ; Tue, 28 May 2002 22:28:17 -0700 Received: (qmail 22911 invoked from network); 29 May 2002 05:20:33 -0000 Received: from unknown (HELO adacel.com) (192.168.75.53) by nexus.adacel.com with SMTP; 29 May 2002 05:20:32 -0000 Message-ID: <3CF468DD.8090101@adacel.com> Date: Wed, 29 May 2002 15:36:29 +1000 From: Michael Wardle Organization: Adacel Technologies User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc2) Gecko/20020512 Netscape/7.0b1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: =?ISO-8859-1?Q?Unit=E9_d=27Ombre?= CC: fam@oss.sgi.com Subject: Re: [fam] Using fam correctly References: <6250CC48-6E7E-11D6-9347-003065BA6A54@10191.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-fam@oss.sgi.com Precedence: bulk Hi Chris Here's some information that may help (a little): 1. the test module inside FAM is exactly that -- it's not a good example of how to really do it 2. i've tried to piece together some links to how FAM has been used by different applications. This is what I came up with http://oss.sgi.com/projects/fam/links.html#code -- MICHAEL WARDLE SGI Desktop & Admin Software Adacel Technologies Limited -- 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 May 29 01:45:34 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.3/8.12.3) with ESMTP id g4T8jYnC024069 for ; Wed, 29 May 2002 01:45:34 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.3/8.12.3/Submit) id g4T8jYUc024068 for fam-outgoing; Wed, 29 May 2002 01:45:34 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-fam@oss.sgi.com using -f Received: from nexus.adacel.com (shelob.adacel.com.au [203.36.26.146] (may be forged)) by oss.sgi.com (8.12.3/8.12.3) with SMTP id g4T8jNnC024061 for ; Wed, 29 May 2002 01:45:27 -0700 Received: (qmail 8440 invoked from network); 29 May 2002 08:37:38 -0000 Received: from unknown (HELO adacel.com) (192.168.75.53) by nexus.adacel.com with SMTP; 29 May 2002 08:37:38 -0000 Message-ID: <3CF4970F.10503@adacel.com> Date: Wed, 29 May 2002 18:53:35 +1000 From: Michael Wardle Organization: Adacel Technologies User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc2) Gecko/20020512 Netscape/7.0b1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Lars Pechan CC: fam@oss.sgi.com Subject: Re: [fam] GCC-3.1 compilation problems... References: <200205280102.18620.lars.pechan@paradise.net.nz> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-fam@oss.sgi.com Precedence: bulk Lars Pechan wrote: > I'm trying to build fam-oss 2.6.7 using Gentoo Linux i386 with > gcc3.1 and get the following output: > > c++ -DHAVE_CONFIG_H -I. -I. -I.. -I../include > -DCONFIG_ETC_CONFIG_PATH=\"/etc/fam.conf\" -Wno-deprecated -c > Scheduler.c++ > Scheduler.c++:37: uninitialized const member > `Scheduler::IOTypeInfo::iotype' > Scheduler.c++:38: uninitialized const member > `Scheduler::IOTypeInfo::iotype' > make[2]: *** [Scheduler.o] Error 1 > make[2]: Leaving directory > `/var/tmp/portage/fam-oss-2.6.7/work/fam-2.6.7/fam' (Line numbers from FAM 2.6.7) At line 107 of Scheduler.h, struct IOTypeInfo has a member iotype that is given a "const" modifier. At line 123, two variables of type IOTypeInfo, "read" and "write" are declared. As I'm more familiar with C than C++ (and I'm learning Java at the moment, so the exact terminologies and nuances of each is becoming a blur), there's a couple of things I'm trying to figure out... 1. Is the position of the const modifier correct? I'm accustomed to seeing it before the type. Is it possible to put the modifier elsewhere in C++? 2. Is the IOTypeInfo constructor called when "read" and "write" are first declared at line 123? If so, then this means they are actually instantiated, not declared, correct? If so, then presumably calling the constructor at lines 37 and 38 of Scheduler.c++ is trying to modify an already initialized const member. If so, how can this be overcome (other than removing the const modifier, which seems to be a bad idea)? If not, why would the error be occurring at all? -- MICHAEL WARDLE SGI Desktop & Admin Software Adacel Technologies Limited -- 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 May 29 05:59:17 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.3/8.12.3) with ESMTP id g4TCxHnC012709 for ; Wed, 29 May 2002 05:59:17 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.3/8.12.3/Submit) id g4TCxHD7012708 for fam-outgoing; Wed, 29 May 2002 05:59:17 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-fam@oss.sgi.com using -f Received: from deliverator.sgi.com (deliverator.SGI.COM [204.94.214.10]) by oss.sgi.com (8.12.3/8.12.3) with SMTP id g4TCx6nC012696 for ; Wed, 29 May 2002 05:59:06 -0700 Received: from rlyeh.corp.sgi.com (rlyeh.corp.sgi.com [134.15.21.226]) by deliverator.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 GAA03238 for ; Wed, 29 May 2002 06:00:32 -0700 (PDT) mail_from (rusty@rlyeh.corp.sgi.com) Received: (from rusty@localhost) by rlyeh.corp.sgi.com (SGI-8.9.3/8.9.3) id FAA63646; Wed, 29 May 2002 05:57:35 -0700 (PDT) From: "Rusty Ballinger" Message-Id: <10205290557.ZM265488@rlyeh.corp.sgi.com> Date: Wed, 29 May 2002 05:57:34 -0700 In-Reply-To: Michael Wardle "Re: [fam] GCC-3.1 compilation problems..." (May 29, 6:53pm) References: <200205280102.18620.lars.pechan@paradise.net.nz> <3CF4970F.10503@adacel.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: lars.pechan@paradise.net.nz, michael.wardle@adacel.com Subject: Re: [fam] GCC-3.1 compilation problems... Cc: fam@oss.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-fam@oss.sgi.com Precedence: bulk > > I'm trying to build fam-oss 2.6.7 using Gentoo Linux i386 with > > gcc3.1 and get the following output: (Hey, I'm running Gentoo at home, but it only has gcc 2.95.3. That built fam for kde with no problems.) > At line 107 of Scheduler.h, struct IOTypeInfo has a member iotype that > is given a "const" modifier. At line 123, two variables of type > IOTypeInfo, "read" and "write" are declared. ... > 1. Is the position of the const modifier correct? I'm accustomed to > seeing it before the type. Is it possible to put the modifier > elsewhere in C++? Putting it before & after the type means two different things; it's the same in C: int a, b; const int * c = &a; /* the value of c can change, but the value *pointed to* by c is const. This is the form you usually see, because usually, who cares if c itself changes? */ int * const d = &a; /* the value of d cannot change (it's const), but the value *pointed to* by d can change! This is not what you usually want, which is why you don't usually see it. */ So, two of the next four lines are allowed, and two are not. If you're not sure which, your compiler will tell you the answer. :) c = &b; *c = 1; d = &b; *d = 1; > 2. Is the IOTypeInfo constructor called when "read" and "write" are > first declared at line 123? No, the bit at the top of Scheduler.c++ is where they're defined, and you can see what's passed to their constructors there. The declaration in the header just means "somewhere in this program, there's a thing called Scheduler::IOTypeInfo::iotype, which I will define later." > If so, then this means they are > actually instantiated, not declared, correct? If so, then > presumably calling the constructor at lines 37 and 38 of > Scheduler.c++ is trying to modify an already initialized const > member. If so, how can this be overcome (other than removing the > const modifier, which seems to be a bad idea)? If not, why > would the error be occurring at all? Scheduler.h line 107 makes use of C++'s little-known obfuscation operator, which most books cover in the section on "pointers to members". Pointers to members are not like the pointers which normal, healthy, well-adjusted people (you know, like this list's subscribers) usually see. Consider the declaration: FDInfo::FDIOHandler FDInfo::*const iotype; That freakishly weird syntax means that iotype is a const pointer to a FDInfo::FDIOHandler member of the FDInfo class. It's like an offset in the *class*; you don't get an FDInfo::FDIOHandler unless you apply iotype to an FDInfo *object* using the .* or ->* operators. You can see this where it's used in Scheduler.c++: IOHandler old_handler = (fp->*(iotype->iotype)).handler; fp is an FDInfo *, and iotype is an IOTypeInfo *, so iotype->iotype is the offset of an FDInfo::FDIOHandler within the FDInfo class, and fp->*(iotype->iotype) gives you an actual FDIOHandler in fp. (handler is a member of FDIOHandler; its type is IOHandler.) The ->* operator isn't one you see every day, and thank goodness for that! Going back to the original problem... I don't see why gcc doesn't like it. It looks to me like that code is properly initializing iotype; I was thinking maybe the compiler is complaining that &FDInfo::read and &FDInfo::write are not known at the point where they're passed into the constructors & used to initialize iotype, but I don't think that can be right, as it's already seen the struct FDInfo definition before that point. There are three open bugs on gcc.gnu.org with "pointer to member", but none of them look related to this. --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 Wed May 29 06:09:20 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.3/8.12.3) with ESMTP id g4TD9KnC012884 for ; Wed, 29 May 2002 06:09:20 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.3/8.12.3/Submit) id g4TD9KRH012883 for fam-outgoing; Wed, 29 May 2002 06:09:20 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-fam@oss.sgi.com using -f Received: from post.webmailer.de (natpost.webmailer.de [192.67.198.65]) by oss.sgi.com (8.12.3/8.12.3) with SMTP id g4TD9AnC012873 for ; Wed, 29 May 2002 06:09:11 -0700 Received: from A3d48.pppool.de (A3d48.pppool.de [213.6.61.72]) by post.webmailer.de (8.9.3/8.8.7) with ESMTP id PAA09540 for ; Wed, 29 May 2002 15:10:36 +0200 (MET DST) Subject: Re: [fam] GCC-3.1 compilation problems... From: Christian Kreibich To: FAM Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1022677843.752.158.camel@Gonzo> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.1.0.99 (Preview Release) Date: 29 May 2002 15:12:28 +0200 Sender: owner-fam@oss.sgi.com Precedence: bulk Hi Michael, On Wed, 2002-05-29 at 10:53, Michael Wardle wrote: > Lars Pechan wrote: > > I'm trying to build fam-oss 2.6.7 using Gentoo Linux i386 with > > gcc3.1 and get the following output: > > > > c++ -DHAVE_CONFIG_H -I. -I. -I.. -I../include > > -DCONFIG_ETC_CONFIG_PATH=\"/etc/fam.conf\" -Wno-deprecated -c > > Scheduler.c++ > > Scheduler.c++:37: uninitialized const member > > `Scheduler::IOTypeInfo::iotype' > > Scheduler.c++:38: uninitialized const member > > `Scheduler::IOTypeInfo::iotype' > > make[2]: *** [Scheduler.o] Error 1 > > make[2]: Leaving directory > > `/var/tmp/portage/fam-oss-2.6.7/work/fam-2.6.7/fam' > > (Line numbers from FAM 2.6.7) > > At line 107 of Scheduler.h, struct IOTypeInfo has a member iotype that > is given a "const" modifier. At line 123, two variables of type > IOTypeInfo, "read" and "write" are declared. > > As I'm more familiar with C than C++ (and I'm learning Java at the > moment, so the exact terminologies and nuances of each is becoming a > blur), there's a couple of things I'm trying to figure out... > > 1. Is the position of the const modifier correct? I'm accustomed to > seeing it before the type. Is it possible to put the modifier > elsewhere in C++? C++ knows the difference between a constant pointer (that cannot be made pointing anywhere else) and a constant pointed-to object (whose contents cannot be changed). In this case, it's a constant pointer. The other confusing thing in the code involved are C++'s member pointers. Bruce Eckel's Thinking In C++ has a lot of detail about the various const flavours and member pointers. > 2. Is the IOTypeInfo constructor called when "read" and "write" are > first declared at line 123? If so, then this means they are > actually instantiated, not declared, correct? If so, then > presumably calling the constructor at lines 37 and 38 of > Scheduler.c++ is trying to modify an already initialized const > member. If so, how can this be overcome (other than removing the > const modifier, which seems to be a bad idea)? If not, why > would the error be occurring at all? Mhmmm the Scheduler's read and write IOTypeInfo members are static but not const, so it should be okay to initialize them in Scheduler.c++ (and not inside the header file), and the iotype member is a const member pointer and gets initialized properly in the constructor's initialization list of IOTypeInfo right at the start. I think everything should be okay, the only thing that surprises me a bit is that you can do Scheduler::IOTypeInfo Scheduler::read(&FDInfo::read); Scheduler::IOTypeInfo Scheduler::write(&FDInfo::write); instead of Scheduler::IOTypeInfo Scheduler::read(&Scheduler::FDInfo::read); Scheduler::IOTypeInfo Scheduler::write(&Scheduler::FDInfo::write); But I doubt that this has any influence. Then again, my knowledge of C++ has become a bit rusty :) Puzzled, Christian. -- ________________________________________________________________________ http://www.whoop.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 Wed May 29 14:37:15 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.3/8.12.3) with ESMTP id g4TLbFnC002013 for ; Wed, 29 May 2002 14:37:15 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.3/8.12.3/Submit) id g4TLbF9E001965 for fam-outgoing; Wed, 29 May 2002 14:37:15 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-fam@oss.sgi.com using -f Received: from mail.speakeasy.net (mail17.speakeasy.net [216.254.0.217]) by oss.sgi.com (8.12.3/8.12.3) with SMTP id g4TLbAnC001480 for ; Wed, 29 May 2002 14:37:10 -0700 Received: (qmail 25810 invoked from network); 29 May 2002 21:38:33 -0000 Received: from unknown (HELO marieco) ([24.196.10.48]) (envelope-sender ) by mail17.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 29 May 2002 21:38:33 -0000 Date: Wed, 29 May 2002 16:40:03 -0500 From: Nick Hudson To: fam@oss.sgi.com Subject: [fam] Fam Compile Problems Message-Id: <20020529164003.1193a2d4.nhudson@speakeasy.net> X-Mailer: Sylpheed version 0.7.6claws (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-fam@oss.sgi.com Precedence: bulk Im having problems compiling Fam with the DNotify Patch installed, I get this error: && CONFIG_FILES=include/Makefile CONFIG_HEADERS= /bin/sh ./config.status config.status: creating include/Makefile config.status: executing depfiles commands config.status: executing default-1 commands config.status: executing default-2 commands config.status: executing default-3 commands make[2]: Leaving directory `/usr/src/fam-2.6.7/include' make[2]: Entering directory `/usr/src/fam-2.6.7/include' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/usr/src/fam-2.6.7/include' Making all in support make[2]: Entering directory `/usr/src/fam-2.6.7/support' Makefile:323: no file name for `-include' cd .. && automake --gnu support/Makefile support/Makefile.am:14: CLEANFILES must be set with `=' before using `+=' ! Problem Detected ! make[2]: *** [Makefile.in] Error 1 make[2]: Leaving directory `/usr/src/fam-2.6.7/support' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/src/fam-2.6.7' make: *** [all] Error 2 Any idea on what im doing wrong. The patch is patching clean ... Thanks for the help Nick Hudson -- 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 May 29 16:04:27 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.3/8.12.3) with ESMTP id g4TN4RnC003997 for ; Wed, 29 May 2002 16:04:27 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.3/8.12.3/Submit) id g4TN4RlU003996 for fam-outgoing; Wed, 29 May 2002 16:04:27 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-fam@oss.sgi.com using -f Received: from nexus.adacel.com (shelob.adacel.com.au [203.36.26.146] (may be forged)) by oss.sgi.com (8.12.3/8.12.3) with SMTP id g4TN4NnC003993 for ; Wed, 29 May 2002 16:04:24 -0700 Received: (qmail 13566 invoked from network); 29 May 2002 22:56:37 -0000 Received: from unknown (HELO adacel.com) (192.168.75.53) by nexus.adacel.com with SMTP; 29 May 2002 22:56:37 -0000 Message-ID: <3CF56065.8010102@adacel.com> Date: Thu, 30 May 2002 09:12:37 +1000 From: Michael Wardle Organization: Adacel Technologies User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc2) Gecko/20020512 Netscape/7.0b1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nick Hudson CC: fam@oss.sgi.com Subject: Re: [fam] Fam Compile Problems References: <20020529164003.1193a2d4.nhudson@speakeasy.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-fam@oss.sgi.com Precedence: bulk Nick Hudson wrote: > Im having problems compiling Fam with the DNotify Patch installed, I get this error: [...] > cd .. && automake --gnu support/Makefile > support/Makefile.am:14: CLEANFILES must be set with `=' before using `+=' Add "CLEANFILES =" to common.am before running configure. -- MICHAEL WARDLE SGI Desktop & Admin Software Adacel Technologies Limited -- 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 Fri May 31 07:19:24 2002 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.3/8.12.3) with ESMTP id g4VEJOnC031385 for ; Fri, 31 May 2002 07:19:24 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.3/8.12.3/Submit) id g4VEJOxc031384 for fam-outgoing; Fri, 31 May 2002 07:19:24 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-fam@oss.sgi.com using -f Received: from mx01.forces.ca (mx01.forces.ca [131.137.245.201]) by oss.sgi.com (8.12.3/8.12.3) with SMTP id g4VEJBnC031375 for ; Fri, 31 May 2002 07:19:11 -0700 From: Asselstine.BD@forces.ca To: fam@oss.sgi.com Subject: [fam] FAM Client Software Date: Fri, 31 May 2002 10:20:40 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Message-Id: <20020531142018.6FBB7412D1@mx01.forces.ca> Sender: owner-fam@oss.sgi.com Precedence: bulk Hi, I've noticed that when I'm monitoring large files for changes that are being rewritten, FAM generates a lot of FAMChanged events. And rightly so. My question is this: Can my FAM Client software operate on the assumption that I'll get all of these FAMChanged Events in one shot? (Eg in a FAMPending loop.) Another way of putting it is like this: Is the FAM server a fast writer to my FAM Client's slow reader? I sent mail to owner-fam@oss.sgi.com yesterday, and I'm not sure if this is the same address or not, so I'l repeat my earlier email and expand on it: I'm writing a fileschanged command line utility that uses Fam. It works like this: You give it a list of files and it returns the filenames of altered files as they change. I've got it working with autoconf and I'm done except for a few issues. They are: 1) large files get a lot of FAMChanged Events. (explained above) 2) I'm using realpath, so symlinks are resolved, it may cause the recursive option to run infinitely. (I can add code to detect this) 3) I'm assuming the device id and inode of a monitored file or directory is unique. I think nfs breaks this assumption, but I may be wrong. (no clue) The fileschanged utility will be useful in shell scripts. Take this one for example: It takes all outgoing mail and saves it to a tar file. --- #!/bin/bash fileschanged --files-to-monitor /var/spool/mqueue | while read file ; do tar -uPvf /tmp/outgoingmail.tar $file done --- Simple eh? It can also be used in this manner: --- #!/bin/fileschanged --recursive /home/myuser /var/log/messages /var/log/httpd/access_log --- And the script will report when files have been changed. Nifty eh? And the default way to use fileschanged is like this: % fileschanged --recursive filelist where filelist is a file that looks like: --- /home/myuser /var/log/messages /var/log/httpd/access_log --- fileschanged has code in it that prevents the same file from being monitored twice. % fileschanged --recursive --files-to-monitor /var/log /var/log/messages or % fileschanged --recursive --files-to-monitor /var/log/messages /var/log both run such that /var/log/messages appears on the stdout only once when it's changed. fileschanged would be very simple if it didn`t check to see if a file is already being monitored. Here's the current --help screen. maybe it will make more sense than my examples. Usage: fileschanged [OPTION...] [FILE]... Show altered files from the list of filenames given in FILE. The standard input can be used if FILE is - or absent. -d, --show-deleted Also show deleted or moved files to stderr -f, --files-to-monitor Monitor the list of files on the command line -h, --hash-is-not-comment Don't ignore lines in FILE starting with '#' -l, --filelist (Default) Monitor the list of filenames in FILE -r, --recursive Monitor subdirectories of directories -?, --help Give this help list --usage Give a short usage message -V, --version Print program version Report bugs to . And that's it. I still need to make the info and man pages, and make an rpm but I'm just about finished. I hope I haven't recreated somebody else's wheel! Please let me know what you think about fileschanged. I can send you the code if you like -- I don't have a clue if it will work on Irix. Please respond to ``benasselstine (at) sympatico (dot) ca`` instead of the return address on this message. thx. Ben -- Source code, list archive, and docs: http://oss.sgi.com/projects/fam/ To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com