From owner-fam@oss.sgi.com Wed Mar 1 18:56:32 2000 Received: by oss.sgi.com id ; Wed, 1 Mar 2000 18:56:22 -0800 Received: from deliverator.sgi.com ([204.94.214.10]:24375 "EHLO deliverator.sgi.com") by oss.sgi.com with ESMTP id ; Wed, 1 Mar 2000 18:56:15 -0800 Received: from rlyeh.engr.sgi.com (rlyeh.engr.sgi.com [163.154.5.94]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id SAA05095 for ; Wed, 1 Mar 2000 18:51:42 -0800 (PST) mail_from (guest@rlyeh.engr.sgi.com) Received: (from guest@localhost) by rlyeh.engr.sgi.com (980427.SGI.8.8.8/960327.SGI.AUTOCF) id SAA22804 for fam@oss.sgi.com; Wed, 1 Mar 2000 18:54:41 -0800 (PST) Date: Wed, 1 Mar 2000 18:54:41 -0800 (PST) From: guest@rlyeh.engr.sgi.com (Guest Account) Message-Id: <200003020254.SAA22804@rlyeh.engr.sgi.com> To: fam@oss.sgi.com Subject: OK, not a test. Sender: owner-fam@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;fam-outgoing Wee hee hee. From owner-fam@oss.sgi.com Thu Mar 2 00:50:14 2000 Received: by oss.sgi.com id ; Thu, 2 Mar 2000 00:49:54 -0800 Received: from deliverator.sgi.com ([204.94.214.10]:19327 "EHLO deliverator.sgi.com") by oss.sgi.com with ESMTP id ; Thu, 2 Mar 2000 00:49:25 -0800 Received: from rlyeh.engr.sgi.com (rlyeh.engr.sgi.com [163.154.5.94]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id AAA27934 for ; Thu, 2 Mar 2000 00:44:51 -0800 (PST) mail_from (rusty@rlyeh.engr.sgi.com) Received: (from rusty@localhost) by rlyeh.engr.sgi.com (980427.SGI.8.8.8/960327.SGI.AUTOCF) id AAA29570; Thu, 2 Mar 2000 00:47:25 -0800 (PST) From: "Rusty Ballinger" Message-Id: <10003020047.ZM227673@rlyeh.engr.sgi.com> Date: Thu, 2 Mar 2000 00:47:24 -0800 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: jmtcode@hotmail.com Subject: fam source 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 It took a lot longer than I thought, but fam source is now available at http://oss.sgi.com/projects/fam/. I'd be really surprised if it builds on SCO OpenServer without a fair amount of effort, but either way I'd be interested to hear how it goes. If getting it to build looks like it will take more time than you want to spend, and you just want to use the fam source for an example of polling the contents of a directory, files for the fam daemon are in fam-2.6.0/fam. (Keep in mind that polling is not what fam is all about; normally it only polls if the kernel doesn't have imon support.) Pollster.c++ keeps a list of Interests that are being polled. (Each Interest represents a single monitored file or directory.) Files are pretty simple; every time they're polled, stat() is called on them, and their modification time is compared to the time which was stored last time the file was checked. Probably more interesting to you is DirectoryScanner::done(), which determines whether files have been added or removed. It keeps a list of the directory's contents; for every element returned by readdir(), it sees whether the element is new/removed/changed. The code is actually pretty hard to follow... depending on what you want to use the code for, you might be better off if you can just get fam to build & run, and use FAMMonitorDirectory() etc. to talk to fam (see the fam(3X) man page, which is included in the source). --Rusty From owner-fam@oss.sgi.com Thu Mar 2 01:36:34 2000 Received: by oss.sgi.com id ; Thu, 2 Mar 2000 01:36:15 -0800 Received: from deliverator.sgi.com ([204.94.214.10]:25865 "EHLO deliverator.sgi.com") by oss.sgi.com with ESMTP id ; Thu, 2 Mar 2000 01:36:06 -0800 Received: from rlyeh.engr.sgi.com (rlyeh.engr.sgi.com [163.154.5.94]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id BAA01040 for ; Thu, 2 Mar 2000 01:31:32 -0800 (PST) mail_from (rusty@rlyeh.engr.sgi.com) Received: (from rusty@localhost) by rlyeh.engr.sgi.com (980427.SGI.8.8.8/960327.SGI.AUTOCF) id BAA09827 for fam@oss.sgi.com; Thu, 2 Mar 2000 01:34:31 -0800 (PST) From: "Rusty Ballinger" Message-Id: <10003020134.ZM207685@rlyeh.engr.sgi.com> Date: Thu, 2 Mar 2000 01:34:31 -0800 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: fam@oss.sgi.com Subject: whee, testing whizzy majordomo options. 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 This is to see whether the subject & footer options took effect. --Rusty From owner-fam@oss.sgi.com Thu Mar 2 01:41:14 2000 Received: by oss.sgi.com id ; Thu, 2 Mar 2000 01:41:05 -0800 Received: from pneumatic-tube.sgi.com ([204.94.214.22]:23140 "EHLO pneumatic-tube.sgi.com") by oss.sgi.com with ESMTP id ; Thu, 2 Mar 2000 01:40:53 -0800 Received: from rlyeh.engr.sgi.com (rlyeh.engr.sgi.com [163.154.5.94]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id BAA03790 for ; Thu, 2 Mar 2000 01:44:02 -0800 (PST) mail_from (rusty@rlyeh.engr.sgi.com) Received: (from rusty@localhost) by rlyeh.engr.sgi.com (980427.SGI.8.8.8/960327.SGI.AUTOCF) id BAA29032 for fam@oss.sgi.com; Thu, 2 Mar 2000 01:39:19 -0800 (PST) From: "Rusty Ballinger" Message-Id: <10003020139.ZM213419@rlyeh.engr.sgi.com> Date: Thu, 2 Mar 2000 01:39:19 -0800 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: fam@oss.sgi.com Subject: [fam] another test of the whizzy majordomo options 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 can outsmart the filter which removes test messages, I just know it. --Rusty To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com From owner-fam@oss.sgi.com Thu Mar 2 01:55:05 2000 Received: by oss.sgi.com id ; Thu, 2 Mar 2000 01:54:45 -0800 Received: from deliverator.sgi.com ([204.94.214.10]:33035 "EHLO deliverator.sgi.com") by oss.sgi.com with ESMTP id ; Thu, 2 Mar 2000 01:54:36 -0800 Received: from rlyeh.engr.sgi.com (rlyeh.engr.sgi.com [163.154.5.94]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id BAA01975 for ; Thu, 2 Mar 2000 01:50:02 -0800 (PST) mail_from (guest@rlyeh.engr.sgi.com) Received: (from guest@localhost) by rlyeh.engr.sgi.com (980427.SGI.8.8.8/960327.SGI.AUTOCF) id BAA27169 for fam@oss.sgi.com; Thu, 2 Mar 2000 01:53:02 -0800 (PST) Date: Thu, 2 Mar 2000 01:53:02 -0800 (PST) From: guest@rlyeh.engr.sgi.com (Guest Account) Message-Id: <200003020953.BAA27169@rlyeh.engr.sgi.com> To: fam@oss.sgi.com Subject: [fam] this might be a test Sender: owner-fam@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;fam-outgoing Perhaps someday this list will have something other than test messages. --Rusty -- To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com From owner-fam@oss.sgi.com Thu Mar 2 06:14:46 2000 Received: by oss.sgi.com id ; Thu, 2 Mar 2000 06:14:37 -0800 Received: from tardis.uts.ohio-state.edu ([128.146.116.116]:28322 "EHLO tardis.uts.ohio-state.edu") by oss.sgi.com with ESMTP id ; Thu, 2 Mar 2000 06:14:13 -0800 Received: from lennier.uts.ohio-state.edu (lennier.uts.ohio-state.edu [128.146.116.7]) by tardis.uts.ohio-state.edu (8.9.1/8.9.1) with ESMTP id JAA13323 for ; Thu, 2 Mar 2000 09:14:11 -0500 (EST) Received: (from rfunk@localhost) by lennier.uts.ohio-state.edu (8.8.8+Sun/8.8.8) id JAA29388 for fam@oss.sgi.com; Thu, 2 Mar 2000 09:14:10 -0500 (EST) From: Rob Funk Message-Id: <200003021414.JAA29388@lennier.uts.ohio-state.edu> Subject: [fam] fam still too trusting? To: fam@oss.sgi.com Date: Thu, 2 Mar 2000 09:14:10 -0500 (EST) X-Face: "@@t%Tp%P[K&^Z1/]q70]C%d'=\$yoa]&jttNbd#nh_uP?0{p.IFN'N+HztsAU!i~b6MS~1 ;DRL#`"zX~!t%Ki8+x&"G|pni0/'wi}78(94"Ud%jH{hzEWc/{F.v\OBMr-!)6x|BBACbObZpW^}w> #P{s4m~_#vGsg$-wHd^u$BV@7|=b44]uvE>7HWz(:5$ygT>^/SsLid||U]}:5"H08!w,Rg;Vr8PE7f N:\hr_*Rh49hXUdLt`;%ChC6kbJUl39=$Y;GF4VJJ2rJ_o{mNfL?Zr$J". X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 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 just read the fam FAQ, and noticed the following: | Is fam secure? | | fam has long had a known security weakness which allows clients to | learn the names of files and directories on the system. This version | of fam does not have that problem. Connections from local clients | are treated as untrusted unless the client is able to communicate | over a unix domain socket readable only by the client's claimed | UID. So far so good.... but then: | Connections from remote clients are treated as untrusted unless | they originate from a privileged port, and requests are only | serviced if they fall on filesystems which have been exported to the | requesting host. If I'm interpreting this correctly, anybody on the net that has root on their computer will be treated as trusted by fam on my computer. Remote connections should ALWAYS be treated as untrusted. If I'm misinterpreting, could you please clarify the FAQ? Also, it would be nice to get away from RPC services, since they are so difficult to block from the outside world. At the very least, services (such as fam) that are intended for local use should only listen on the loopback interface. -- Rob Funk The Ohio State University University Technology Services / Workstation Support http://wks.uts.ohio-state.edu/ -- To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com From owner-fam@oss.sgi.com Thu Mar 2 12:24:54 2000 Received: by oss.sgi.com id ; Thu, 2 Mar 2000 12:24:34 -0800 Received: from pneumatic-tube.sgi.com ([204.94.214.22]:3116 "EHLO pneumatic-tube.sgi.com") by oss.sgi.com with ESMTP id ; Thu, 2 Mar 2000 12:24:33 -0800 Received: from rlyeh.engr.sgi.com (rlyeh.engr.sgi.com [163.154.5.94]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id MAA08416 for ; Thu, 2 Mar 2000 12:27:43 -0800 (PST) mail_from (rusty@rlyeh.engr.sgi.com) Received: (from rusty@localhost) by rlyeh.engr.sgi.com (980427.SGI.8.8.8/960327.SGI.AUTOCF) id MAA28225; Thu, 2 Mar 2000 12:22:33 -0800 (PST) From: "Rusty Ballinger" Message-Id: <10003021222.ZM230122@rlyeh.engr.sgi.com> Date: Thu, 2 Mar 2000 12:22:33 -0800 In-Reply-To: Rob Funk "[fam] fam still too trusting?" (Mar 2, 9:14am) References: <200003021414.JAA29388@lennier.uts.ohio-state.edu> 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: rfunk@wks.uts.ohio-state.edu Subject: Re: [fam] fam still too trusting? 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 > | Connections from remote clients are treated as untrusted unless > | they originate from a privileged port, and requests are only > | serviced if they fall on filesystems which have been exported to the > | requesting host. > > If I'm interpreting this correctly, anybody on the net that has root > on their computer will be treated as trusted by fam on my computer. Sort of; it's anybody who has root on a computer that you've NFS-exported the filesystem to. fam will believe them when they say "UID so-and-so wants to monitor this file," but if the file they're asking for doesn't fall on a filesystem that they could have mounted, fam tells them the file doesn't exist. > Also, it would be nice to get away from RPC services, since they are > so difficult to block from the outside world. At the very least, > services (such as fam) that are intended for local use should only > listen on the loopback interface. Yeah... there's an only-slightly-documented way to get fam to run local-only (see the INSTALL file--you have to take it out of inetd.conf and put it in an init script--and it still registers with the portmapper), but I don't think fam is intended to be only for local use. "In theory," it shouldn't matter where your filesystem is mounted from; you ask fam to monitor it, and fam tries to pass your request on to fam on the host serving the files so that you still get notification when your files changed without having to poll over NFS. --Rusty -- To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com From owner-fam@oss.sgi.com Fri Mar 3 03:25:20 2000 Received: by oss.sgi.com id ; Fri, 3 Mar 2000 03:25:11 -0800 Received: from bodo.ct.chemie.tu-darmstadt.de ([130.83.135.50]:61499 "EHLO bodo.ct.chemie.tu-darmstadt.de") by oss.sgi.com with ESMTP id ; Fri, 3 Mar 2000 03:24:53 -0800 Received: from rootshell.ct.chemie.tu-darmstadt.de (pc01.ct.chemie.tu-darmstadt.de [130.83.135.150]) by bodo.ct.chemie.tu-darmstadt.de (8.9.2/8.9.0) with ESMTP id MAA23482 for ; Fri, 3 Mar 2000 12:24:41 +0100 (CET) Received: (from henning@localhost) by rootshell.ct.chemie.tu-darmstadt.de (8.9.3/8.9.3) id MAA00699 for fam@oss.sgi.com; Fri, 3 Mar 2000 12:25:23 +0100 Date: Fri, 3 Mar 2000 12:25:23 +0100 From: Henning Meier-Geinitz To: fam@oss.sgi.com Subject: [fam] fam-2.6.0 configure problem Message-ID: <20000303122523.A588@rootshell.ct.chemie.tu-darmstadt.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-fam@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;fam-outgoing Hi, I just downloaded fam-2.6.0.tar.gz, untarred it and ran configure (on an Irix-5.3 Indy): [...] checking for echo... /sbin/echo checking for echo -e flag... foo: Unknown operator [configure stopped, no makefile was generated] This is line 2629 of configure: if test `$ECHO -e foo` = 'foo'; then ECHO="$ECHO -e" fi I think two more " will do the trick, the following works fo me: if test "`$ECHO -e foo`" = 'foo'; then ECHO="$ECHO -e" fi Later on compiling with gcc 2.95.2 I get the following errors: make all-recursive make[1]: Entering directory `/u2/src/fam-2.6.0' Making all in include make[2]: Entering directory `/u2/src/fam-2.6.0/include' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/u2/src/fam-2.6.0/include' Making all in libfam make[2]: Entering directory `/u2/src/fam-2.6.0/libfam' /bin/sh ../libtool --mode=compile c++ -DHAVE_CONFIG_H -I. -I. -I.. -I../include -Wall -g -MD -c Client.c++ rm -f .libs/Client.lo c++ -DHAVE_CONFIG_H -I. -I. -I.. -I../include -Wall -g -MD -c -DPIC Client.c++ -o .libs/Client.lo cc1plus: warning: `-g' not supported by this configuration of GCC Client.c++: In method `Client::Client(long int, int, int)': Client.c++:66: warning: comparison between signed and unsigned Client.c++:73: warning: comparison between signed and unsigned Client.c++:118: implicit declaration of function `int snprintf(...)' Client.c++:138: warning: comparison between signed and unsigned Client.c++:160: warning: comparison between signed and unsigned Client.c++: In method `int Client::readEvent(bool)': Client.c++:392: implicit declaration of function `int bzero(...)' ../include/BTree.h: In method `BTree::Node::~Node()': ../include/BTree.h:293: instantiated from `BTree::~BTree()' Client.c++:198: instantiated from here ../include/BTree.h:182: warning: comparison between signed and unsigned ../include/BTree.h: In method `BTree::Node::~Node()': ../include/BTree.h:293: instantiated from `BTree::~BTree()' Client.c++:199: instantiated from here ../include/BTree.h:182: warning: comparison between signed and unsigned ../include/BTree.h: In method `struct BTree::Closure BTree::insert(BTree::Node *, const int &, void *const &)': ../include/BTree.h:381: instantiated from `BTree::insert(const int &, void *const &)' Client.c++:347: instantiated from here ../include/BTree.h:419: warning: comparison between signed and unsigned ../include/BTree.h: In method `bool BTree::Node::insert(unsigned int, const BTree::Closure &)': ../include/BTree.h:425: instantiated from `BTree::insert(BTree::Node *, const int &, void *const &)' ../include/BTree.h:381: instantiated from `BTree::insert(const int &, void *const &)' Client.c++:347: instantiated from here ../include/BTree.h:219: warning: comparison between signed and unsigned ../include/BTree.h: In method `BTree::Node::Node(BTree::Node *, unsigned int)': ../include/BTree.h:429: instantiated from `BTree::insert(BTree::Node *, const int &, void *const &)' ../include/BTree.h:381: instantiated from `BTree::insert(const int &, void *const &)' Client.c++:347: instantiated from here ../include/BTree.h:168: warning: comparison between signed and unsigned ../include/BTree.h: In method `void * BTree::find(const int &) const': Client.c++:354: instantiated from here ../include/BTree.h:304: warning: comparison between signed and unsigned ../include/BTree.h: In method `struct BTree::Closure BTree::insert(BTree::Node *, const int &, const bool &)': ../include/BTree.h:381: instantiated from `BTree::insert(const int &, const bool &)' Client.c++:365: instantiated from here ../include/BTree.h:419: warning: comparison between signed and unsigned ../include/BTree.h: In method `bool BTree::Node::insert(unsigned int, const BTree::Closure &)': ../include/BTree.h:425: instantiated from `BTree::insert(BTree::Node *, const int &, const bool &)' ../include/BTree.h:381: instantiated from `BTree::insert(const int &, const bool &)' Client.c++:365: instantiated from here ../include/BTree.h:219: warning: comparison between signed and unsigned ../include/BTree.h: In method `BTree::Node::Node(BTree::Node *, unsigned int)': ../include/BTree.h:429: instantiated from `BTree::insert(BTree::Node *, const int &, const bool &)' ../include/BTree.h:381: instantiated from `BTree::insert(const int &, const bool &)' Client.c++:365: instantiated from here ../include/BTree.h:168: warning: comparison between signed and unsigned ../include/BTree.h: In method `bool BTree::find(const int &) const': Client.c++:372: instantiated from here ../include/BTree.h:304: warning: comparison between signed and unsigned ../include/BTree.h: In method `enum BTree::Status BTree::remove(BTree::Node *, const int &)': ../include/BTree.h:462: instantiated from `BTree::remove(const int &)' Client.c++:378: instantiated from here ../include/BTree.h:596: warning: comparison between signed and unsigned ../include/BTree.h: In method `void BTree::Node::join(const BTree::Closure &, BTree::Node *)': ../include/BTree.h:518: instantiated from `BTree::underflow(BTree::Node *, unsigned int)' ../include/BTree.h:568: instantiated from `BTree::remove_rightmost(BTree::Node *)' ../include/BTree.h:602: instantiated from `BTree::remove(BTree::Node *, const int &)' ../include/BTree.h:462: instantiated from `BTree::remove(const int &)' Client.c++:378: instantiated from here ../include/BTree.h:266: warning: comparison between signed and unsigned ../include/BTree.h: In method `enum BTree::Status BTree::remove(BTree::Node *, const int &)': ../include/BTree.h:462: instantiated from `BTree::remove(const int &)' Client.c++:379: instantiated from here ../include/BTree.h:596: warning: comparison between signed and unsigned ../include/BTree.h: In method `void BTree::Node::join(const BTree::Closure &, BTree::Node *)': ../include/BTree.h:518: instantiated from `BTree::underflow(BTree::Node *, unsigned int)' ../include/BTree.h:568: instantiated from `BTree::remove_rightmost(BTree::Node *)' ../include/BTree.h:602: instantiated from `BTree::remove(BTree::Node *, const int &)' ../include/BTree.h:462: instantiated from `BTree::remove(const int &)' Client.c++:379: instantiated from here ../include/BTree.h:266: warning: comparison between signed and unsigned make[2]: *** [Client.lo] Error 1 make[2]: Leaving directory `/u2/src/fam-2.6.0/libfam' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/u2/src/fam-2.6.0' make: *** [all-recursive-am] Error 2 Any ideas? Ciao, Henning -- To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com From owner-fam@oss.sgi.com Fri Mar 3 07:12:32 2000 Received: by oss.sgi.com id ; Fri, 3 Mar 2000 07:12:23 -0800 Received: from gryphon.gsfc.nasa.gov ([128.183.147.222]:32275 "HELO gryphon.gsfc.nasa.gov") by oss.sgi.com with SMTP id ; Fri, 3 Mar 2000 07:11:58 -0800 Received: hostdomain _ id for Fri, 3 Mar 2000 10:18:26 -0500 From: cec@gryphon.gsfc.nasa.gov (Dr. Charles E. Campbell) Message-Id: <200003031518.KAA09939@gryphon.gsfc.nasa.gov> Subject: [fam] fam - configure script bug To: fam@oss.sgi.com Date: Fri, 3 Mar 100 10:18:25 -0500 (EST) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1364 Sender: owner-fam@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;fam-outgoing Hello! I've just gotten through configure, but it was a bit of a fight; the following patch fixes the problem. Problem: script would terminate on (Irix 5.3) if test `$ECHO -e foo` = 'foo'; then because it would expand to if test -e foo = 'foo' ; then and the test would terminate the script complaining of unknown operator "foo". The complaint was misleading, the real problem appears to be that "-e" is an unsupported option to test. Regards, Charles E. Campbell, Jr. --------------------------------------------------------------------- *** oconfigure Fri Mar 3 10:15:17 2000 --- configure Fri Mar 3 10:12:33 2000 *************** *** 2626,2632 **** echo $ac_n "checking for echo -e flag""... $ac_c" 1>&6 echo "configure:2629: checking for $ECHO -e flag" >&5 ! if test `$ECHO -e foo` = 'foo'; then ECHO="$ECHO -e" fi --- 2626,2632 ---- echo $ac_n "checking for echo -e flag""... $ac_c" 1>&6 echo "configure:2629: checking for $ECHO -e flag" >&5 ! if test "`$ECHO -e foo`" = 'foo'; then ECHO="$ECHO -e" fi --------------------------------------------------------------------- -- Charles E Campbell, Jr, PhD _ __ __ Goddard Space Flight Center / /_/\_\_/ / cec@NgrOyphSon.gPsfAc.nMasa.gov /_/ \/_//_/ PGP public key: http://www.erols.com/astronaut/pgp.html/ -- To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com From owner-fam@oss.sgi.com Fri Mar 3 07:21:42 2000 Received: by oss.sgi.com id ; Fri, 3 Mar 2000 07:21:33 -0800 Received: from gryphon.gsfc.nasa.gov ([128.183.147.222]:40211 "HELO gryphon.gsfc.nasa.gov") by oss.sgi.com with SMTP id ; Fri, 3 Mar 2000 07:21:20 -0800 Received: hostdomain _ id for Fri, 3 Mar 2000 10:27:45 -0500 From: cec@gryphon.gsfc.nasa.gov (Dr. Charles E. Campbell) Message-Id: <200003031527.KAA10260@gryphon.gsfc.nasa.gov> Subject: [fam] unable to make fam To: fam@oss.sgi.com Date: Fri, 3 Mar 100 10:27:45 -0500 (EST) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1270 Sender: owner-fam@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;fam-outgoing Hello! I have cc and CC (sgi's, in /usr/bin). I don't know where the lib64 stuff comes from. --------------------------------------------------------------------- No suffix list. cd . \ && CONFIG_FILES= CONFIG_HEADERS=config.h \ /bin/sh ./config.status creating config.h config.h is unchanged make all-recursive No suffix list. Making all in include No suffix list. Making all in libfam /bin/sh ../libtool --mode=compile /usr/bin/CC -DHAVE_CONFIG_H -I. -I. -I.. -I../include -fullwarn -woff 1209,1355 -g -mips3 -n32 -MDupdate Makedepend -ptused -c Client.c++ mkdir .libs /usr/bin/CC -DHAVE_CONFIG_H -I. -I. -I.. -I../include -fullwarn -woff 1209,1355 -g -mips3 -n32 -MDupdate Makedepend -ptused -c -DPIC Client.c++ -o .libs/Client.lo CC ERROR: CC is not installed in /usr/bin/../lib64/cmplrs/CC *** Error code 1 (bu21) *** Error code 1 (bu21) *** Error code 1 (bu21) --------------------------------------------------------------------- Regards, Charles E. Campbell, Jr. -- Charles E Campbell, Jr, PhD _ __ __ Goddard Space Flight Center / /_/\_\_/ / cec@NgrOyphSon.gPsfAc.nMasa.gov /_/ \/_//_/ PGP public key: http://www.erols.com/astronaut/pgp.html/ -- To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com From owner-fam@oss.sgi.com Fri Mar 3 07:37:32 2000 Received: by oss.sgi.com id ; Fri, 3 Mar 2000 07:37:22 -0800 Received: from adms20.fnal.gov ([131.225.125.125]:38672 "EHLO adms20.fnal.gov") by oss.sgi.com with ESMTP id ; Fri, 3 Mar 2000 07:36:56 -0800 Received: from fnal.gov (localhost [127.0.0.1]) by adms20.fnal.gov (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id JAA00559 for ; Fri, 3 Mar 2000 09:32:46 -0600 (CST) Message-ID: <38BFDB1D.5F490B67@fnal.gov> Date: Fri, 03 Mar 2000 09:32:45 -0600 From: Anthony Parker Organization: BDMS CAD Fermilab X-Mailer: Mozilla 4.61C-SGI [en] (X11; I; IRIX 6.2 IP22) X-Accept-Language: en MIME-Version: 1.0 To: fam@oss.sgi.com Subject: [fam] Compiling on IRIX 5.3 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 >From the mail list archive I see that several people have had trouble building on IRIX 5.3. I have a similar problem. We are planning to upgrade several 5.3 systems, but will not be able to for some time. I do not have a compiler on any 5.3 machine, and would rather not have to go and setup GNU just for this. Has/Does anyone have binaries for IRIX 5.3, 6.2 ... available ? Anyone have any Idea when an sgi patch will be available ? Thanks -- Tony Parker HEAD P.E.O.N / Mechanical Design / CAD Support E-mail: awparker@fnal.gov Home: awparker@hinckleynet.com Fermi National Accelerator Laboratory Fax: 630-840-2677 P.O. Box 500 M.S. 340 Batavia , Ill. 60510 Phone: 630-840-4476 -- To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com From owner-fam@oss.sgi.com Fri Mar 3 12:59:04 2000 Received: by oss.sgi.com id ; Fri, 3 Mar 2000 12:58:54 -0800 Received: from dynacs-houston.jsc.nasa.gov ([198.27.47.20]:9476 "EHLO dynacs-houston.jsc.nasa.gov") by oss.sgi.com with ESMTP id ; Fri, 3 Mar 2000 12:58:37 -0800 Received: from dynacs-houston.jsc.nasa.gov ([198.27.47.9]) by dynacs-houston.jsc.nasa.gov (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id OAA11191; Fri, 3 Mar 2000 14:55:16 -0600 (CST) Message-ID: <38C02782.F29E5261@dynacs-houston.jsc.nasa.gov> Date: Fri, 03 Mar 2000 14:58:47 -0600 From: "Robert F. Phillips II" Reply-To: phillips@dynacs-houston.jsc.nasa.gov X-Mailer: Mozilla 4.05 (Macintosh; I; 68K) MIME-Version: 1.0 To: fam@oss.sgi.com Subject: [fam] Problem with configure Content-Type: text/plain; charset=us-ascii; x-mac-type="54455854"; x-mac-creator="4D4F5353" Content-Transfer-Encoding: 7bit Sender: owner-fam@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;fam-outgoing I am maintaining a Silicon Graphics O2 workstation running IRIX 6.3 with almost all known patches. I downloaded the fam source for installation on said system. When attempting to run the configuration script (./configure), I encountered the following: checking for echo -e flag... foo: Unknown operator I traced the problem to line 2629 of the file, finding the following: if test `$ECHO -e foo` = 'foo'; then $ECHO returns /sbin/echo; however, IRIX 6.3 on this workstation does not appear to support the -e option in echo. As a result, I believe the test resolves down to: if test -e foo = foo; then since `/sbin/echo -e foo` returns "-e foo". However, the results from the /sbin/echo command are not protected from the test command, thus test tries to operate on the whole expression up to the semi-colon, and errors off. I was able to fix the problem (tested as well) by simply enclosing `$ECHO -e foo` within double quotes: if test "`$ECHO -e foo`" = 'foo'; then You may wish to incorporate this or something similar into the configure script. -- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + Robert F. Phillips II E-mail: phillips@dynacs-houston.jsc.nasa.gov + + Dynacs Engineering Co., INC + + 1110 NASA Road One, Suite 650 Voice: (281)-333-4419 ext 111 + + Houston, TX 77058 Fax: (281)-333-4423 + ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ I'm not paranoid; I KNOW MicroSoft is trying to get money out of me! -- To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com From owner-fam@oss.sgi.com Sat Mar 4 00:18:33 2000 Received: by oss.sgi.com id ; Sat, 4 Mar 2000 00:18:13 -0800 Received: from deliverator.sgi.com ([204.94.214.10]:44916 "EHLO deliverator.sgi.com") by oss.sgi.com with ESMTP id ; Sat, 4 Mar 2000 00:17:49 -0800 Received: from nodin.corp.sgi.com (fddi-nodin.corp.sgi.com [198.29.75.193]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id AAA18710 for ; Sat, 4 Mar 2000 00:13:14 -0800 (PST) mail_from (rusty@rlyeh.engr.sgi.com) Received: from rlyeh.engr.sgi.com (rlyeh.engr.sgi.com [163.154.5.94]) by nodin.corp.sgi.com (980427.SGI.8.8.8/980728.SGI.AUTOCF) via ESMTP id AAA15655 for ; Sat, 4 Mar 2000 00:17:18 -0800 (PST) Received: (from rusty@localhost) by rlyeh.engr.sgi.com (980427.SGI.8.8.8/960327.SGI.AUTOCF) id AAA29840; Sat, 4 Mar 2000 00:13:51 -0800 (PST) From: "Rusty Ballinger" Message-Id: <10003040013.ZM228861@rlyeh.engr.sgi.com> Date: Sat, 4 Mar 2000 00:13:51 -0800 In-Reply-To: Anthony Parker "[fam] Compiling on IRIX 5.3" (Mar 3, 9:32am) References: <38BFDB1D.5F490B67@fnal.gov> 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: Anthony Parker Subject: Re: [fam] Compiling on IRIX 5.3 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 > Has/Does anyone have binaries for IRIX 5.3, 6.2 ... available ? I can build you 5.3 and/or 6.2 binaries, if you can wait a week or two. (My wife & I are having a baby tomorrow, so I will be out!) However, this version of fam probably won't do you much good without a compiler. Here's why: The previous version of libfam does perform any authentication; that is, an application talking to fam through libfam doesn't prove to the fam daemon that it is who it says it is. That wouldn't matter, except that the previous version of libfam was only available as a static archive, not a shared library. That means every client application which was compiled with libfam has the non-authenticating fam communication built in. That means when you install the new fam (which treats clients as untrusted until they authenticate themselves), your existing fam clients (like everything in the desktop) won't attempt to authenticate themselves, and will only be able to monitor files which can be stat'ed by "nobody" (or whoever you set as the untrusted user in your fam.conf). This means either "nobody" (and any rogue fam client) will be able to monitor your files (in which case there's not much reason to switch to the new version), or your existing fam clients will pretty much be broken (in which case... there's not much reason to switch to the new version). If you still want to pursue it, one thing you might try once you have binaries is to set up fam so that it runs with the insecure-compatibility configuration option (so your existing clients will still work), but local-only (so it won't accept connections from remote hosts), and then make sure you don't have an open guest account etc. (And don't monitor remote filesystems if you can help it, as fam will have to poll over NFS because fam on the NFS server won't talk to it.) This approach might make sense if you really want to run the desktop etc. on a machine that isn't behind a firewall. > Anyone have any Idea when an sgi patch will be available ? This version of fam is in 6.5.8, which ships in May. I don't know, but I assume a patch for 6.2 will be available around then, or sometime before. (And I expect the patch itself will make life ugly for everyone; it'll have to contain every fam client distributed by SGI, and will break any home-grown or third-party fam client that isn't recompiled with the new libfam... Blehh.) --Rusty -- To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com From owner-fam@oss.sgi.com Sat Mar 4 00:25:03 2000 Received: by oss.sgi.com id ; Sat, 4 Mar 2000 00:24:43 -0800 Received: from deliverator.sgi.com ([204.94.214.10]:23669 "EHLO deliverator.sgi.com") by oss.sgi.com with ESMTP id ; Sat, 4 Mar 2000 00:24:35 -0800 Received: from rlyeh.engr.sgi.com (rlyeh.engr.sgi.com [163.154.5.94]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id AAA19082 for ; Sat, 4 Mar 2000 00:20:01 -0800 (PST) mail_from (rusty@rlyeh.engr.sgi.com) Received: (from rusty@localhost) by rlyeh.engr.sgi.com (980427.SGI.8.8.8/960327.SGI.AUTOCF) id AAA24063; Sat, 4 Mar 2000 00:22:31 -0800 (PST) From: "Rusty Ballinger" Message-Id: <10003040022.ZM208525@rlyeh.engr.sgi.com> Date: Sat, 4 Mar 2000 00:22:31 -0800 In-Reply-To: cec@gryphon.gsfc.nasa.gov (Dr. Charles E. Campbell) "[fam] unable to make fam" (Mar 3, 10:27am) References: <200003031527.KAA10260@gryphon.gsfc.nasa.gov> 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: cec@gryphon.gsfc.nasa.gov Subject: Re: [fam] unable to make fam 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 have cc and CC (sgi's, in /usr/bin). I don't know where the lib64 > stuff comes from. ... > /usr/bin/CC -DHAVE_CONFIG_H -I. -I. -I.. -I../include -fullwarn -woff > 1209,1355 -g -mips3 -n32 -MDupdate Makedepend -ptused -c -DPIC Client.c++ > -o .libs/Client.lo > CC ERROR: CC is not installed in /usr/bin/../lib64/cmplrs/CC > *** Error code 1 (bu21) > *** Error code 1 (bu21) > *** Error code 1 (bu21) This is just a random guess, but if you edit the configure script, and remove the "-mips3 -n32", does it work? (This is on 5.3, right?) The configure script definitely needs some work. --Rusty -- To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com From owner-fam@oss.sgi.com Mon Mar 6 10:16:26 2000 Received: by oss.sgi.com id ; Mon, 6 Mar 2000 10:16:16 -0800 Received: from mailbox2.ucsd.edu ([132.239.1.54]:1269 "EHLO mailbox2.ucsd.edu") by oss.sgi.com with ESMTP id ; Mon, 6 Mar 2000 10:16:02 -0800 Received: from cherokee (cherokee.ucsd.edu [132.239.20.70]) by mailbox2.ucsd.edu (8.9.3/8.9.3) with ESMTP id KAA16495 for ; Mon, 6 Mar 2000 10:16:01 -0800 (PST) Received: from cheyenne.ucsd.edu (cheyenne.ucsd.edu [132.239.20.23]) by cherokee (8.9.3+Sun/SOEGW-PSEUDO-4.3-SOL-8.6.x) via ESMTP id KAA14022; Mon, 6 Mar 2000 10:15:34 -0800 (PST) for Received: (from abalogh@localhost) by cheyenne.ucsd.edu (8.9.3+Sun/8.9.1) id KAA21572 for fam@oss.sgi.com; Mon, 6 Mar 2000 10:19:23 -0800 (PST) Date: Mon, 6 Mar 2000 10:19:23 -0800 (PST) From: Andras Balogh Message-Id: <200003061819.KAA21572@cheyenne.ucsd.edu> To: fam@oss.sgi.com Subject: [fam] broken pipe Sender: owner-fam@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;fam-outgoing After replacing the old fam with the new I see a new error message in the log file. It reads: > fam[9336]: fd 6 write error: Broken pipe What can be the problem? Andras -- To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com From owner-fam@oss.sgi.com Mon Mar 6 16:25:59 2000 Received: by oss.sgi.com id ; Mon, 6 Mar 2000 16:25:50 -0800 Received: from mailbox2.ucsd.edu ([132.239.1.54]:48591 "EHLO mailbox2.ucsd.edu") by oss.sgi.com with ESMTP id ; Mon, 6 Mar 2000 16:25:38 -0800 Received: from dim.ucsd.edu (dim.ucsd.edu [132.239.16.7]) by mailbox2.ucsd.edu (8.9.3/8.9.3) with ESMTP id QAA12021; Mon, 6 Mar 2000 16:25:31 -0800 (PST) Received: (from foster@localhost) by dim.ucsd.edu (8.8.8+Sun/8.8.8) id QAA08199; Mon, 6 Mar 2000 16:25:31 -0800 (PST) Date: Mon, 6 Mar 2000 16:25:31 -0800 (PST) From: David Foster Message-Id: <200003070025.QAA08199@dim.ucsd.edu> To: fam@oss.sgi.com Subject: [fam] Problems compiling fam (IRIX 6.5.4) Cc: dfoster@ucsd.edu, spl@alex.ucsd.edu X-Sun-Charset: US-ASCII Sender: owner-fam@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;fam-outgoing I have encountered two problems compiling the current fam 2.6.0 under IRIX 6.5.4; I have tried both gcc 2.95.2 and IRIX MIPSpro 7.3 C++ compilers, both with the same results: 1) fd_set undefined in (led to parsing error in select() prototype) I added "#include " before include of in: ./libfam/Client.c++ ./fam/Activity.c++ and compiling proceeds. 2) Error in declaration in fam/Scheduler.h: Making all in fam make[2]: Entering directory `/auto/giga12/user/foster/Programs/fam/fam-2.6.0/fam' Makefile:364: no file name for `-include' c++ -DHAVE_CONFIG_H -I. -I. -I.. -I../include -DCONFIG_ETC_CONFIG_PATH=\"/usr/local/etc/fam.conf\" -Wall -g -MD -c Activity.c++ In file included from Activity.c++:31: ***************************************************************************************** Scheduler.h:97: ANSI C++ forbids data member `handler' with same name as enclosing class make[2]: *** [Activity.o] Error 1 ***************************************************************************************** make[2]: Leaving directory `/auto/giga12/user/foster/Programs/fam/fam-2.6.0/fam'make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/auto/giga12/user/foster/Programs/fam/fam-2.6.0' make: *** [all-recursive-am] Error 2 I would really like to get this compiled and installed to avoid the vulnerability in fam...any help greatly appreciated. David Foster ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ David Foster National Center for Microscopy and Imaging Research dfoster@ucsd.edu UCSD/Department of Neuroscience (858) 534-7968 http://www-ncmir.ucsd.edu/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -- To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com From owner-fam@oss.sgi.com Tue Mar 7 08:05:43 2000 Received: by oss.sgi.com id ; Tue, 7 Mar 2000 08:05:23 -0800 Received: from nano.unl.edu ([129.93.8.3]:58116 "EHLO nano.unl.edu") by oss.sgi.com with ESMTP id ; Tue, 7 Mar 2000 08:05:09 -0800 Received: from alltel.net (localhost [127.0.0.1]) by nano.unl.edu (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id KAA05653 for ; Tue, 7 Mar 2000 10:04:07 -0600 (CST) Message-ID: <38C52876.F6876E5F@alltel.net> Date: Tue, 07 Mar 2000 10:04:07 -0600 From: "Dana E. Poulain" X-Mailer: Mozilla 4.6C-SGI [en] (X11; U; IRIX 6.2 IP22) X-Accept-Language: en MIME-Version: 1.0 To: fam@oss.sgi.com Subject: [fam] Fam 2.6.0 on IRIX 6.2 Content-Type: multipart/mixed; boundary="------------26E1EF14A61B956FF45639C4" Sender: owner-fam@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;fam-outgoing This is a multi-part message in MIME format. --------------26E1EF14A61B956FF45639C4 Content-Type: multipart/alternative; boundary="------------69C2FCFAC0D6118161465A48" --------------69C2FCFAC0D6118161465A48 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit During installation of fam 2.6.0 on an R5000 IP22 Indy running IRIX 6.2, I've encountered the following difficulties: (1) Running "./configure" fails when checking "echo -e" with the notice checking for echo -e flag... foo: Unknown operator (2) Upon commenting out the "echo -e" lines, "./configure" completes successfully, but then fails during the compilation of "Client.c++" /usr/bin/CC -DHAVE_CONFIG_H -I. -I. -I.. -I../include -fullwarn -woff 1209,1355 -g -mips3 -n32 -MDupdate Makedepend -ptused -c -DPIC Client.c++ -o .libs/Client.lo "../include/Boolean.h", line 31: error(1084): invalid combination of type specifiers typedef int bool; ^ "../include/Boolean.h", line 32: error(1040): expected an identifier const bool true(1), false(0); ^ "../include/Boolean.h", line 32: error(1079): expected a type specifier const bool true(1), false(0); ^ ... more errors along same lines Note: "config.h" and "config.log" are attached. -- Dana E. Poulain Center for Electro-Optics dpoulain@unl.edu -- Ph.D.,P.E. University of Nebraska TEL 402-472-8567 Research Assistant 248 WSEC, Box 880511 FAX 402-472-5083 Professor Lincoln, NE 68588-0511 WWW excimer.unl.edu --------------69C2FCFAC0D6118161465A48 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit During installation of fam 2.6.0 on an R5000 IP22 Indy running IRIX 6.2,
I've encountered the following difficulties:

(1) Running "./configure" fails when checking "echo -e" with the notice

        checking for echo -e flag... foo: Unknown operator

(2) Upon commenting out the "echo -e" lines, "./configure" completes successfully,
      but then fails during the compilation of "Client.c++"

        /usr/bin/CC -DHAVE_CONFIG_H -I. -I. -I.. -I../include -fullwarn -woff
        1209,1355 -g -mips3 -n32 -MDupdate Makedepend -ptused -c  -DPIC
        Client.c++ -o .libs/Client.lo

        "../include/Boolean.h", line 31: error(1084): invalid combination of type specifiers
        typedef int bool;
                         ^
        "../include/Boolean.h", line 32: error(1040): expected an identifier
        const bool true(1), false(0);
                        ^
        "../include/Boolean.h", line 32: error(1079): expected a type specifier
        const bool true(1), false(0);
                                ^
        ... more errors along same lines

Note:  "config.h" and "config.log" are attached.
 
 
  

-- 
Dana E. Poulain         Center for Electro-Optics       dpoulain@unl.edu
  -- Ph.D.,P.E.         University of Nebraska          TEL 402-472-8567
Research Assistant      248 WSEC, Box 880511            FAX 402-472-5083
  Professor             Lincoln, NE 68588-0511          WWW excimer.unl.edu
  --------------69C2FCFAC0D6118161465A48-- --------------26E1EF14A61B956FF45639C4 Content-Type: text/plain; charset=us-ascii; name="config.h" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="config.h" /* config.h. Generated automatically by configure. */ /* config.h.in. Generated automatically from configure.in by autoheader. */ /* Define if the C++ compiler supports a built-in bool type. */ #define HAVE_BOOL 0 /* Define if the C++ compiler supports namespaces. */ #define HAVE_NAMESPACE 0 /* Define if we have nfs_clnt.h */ #define HAVE_SYS_FS_NFS_CLNT_H 1 /* Define if the system has imon and IMONIOC_ ioctl flags. */ #define HAVE_IMON 1 /* Define if we have statvfs. Otherwise, statfs will be used. */ #define HAVE_STATVFS 1 /* Define if we have stat.st_fstype (a char array). */ #define HAVE_STAT_ST_FSTYPE_STRING 1 /* Define if we have syssgi. */ #define HAVE_SYSSGI 1 /* Define if we have sgi nohang. */ #define HAVE_SGI_NOHANG 0 /* Define if we have _daemonize. */ #define HAVE_DAEMONIZE 1 /* Define if we have prmap_sgi_t */ #define HAVE_PRMAP_SGI_T 0 /* Define if we have MNTTYPE_NFS2 */ #define HAVE_MNTTYPE_NFS2 1 /* Define if we have MNTTYPE_NFS3 */ #define HAVE_MNTTYPE_NFS3 1 /* Define if we have MNTTYPE_CACHEFS */ #define HAVE_MNTTYPE_CACHEFS 1 /* Define if we have a prototype for bindresvport(). */ #define HAVE_BINDRESVPORT_PROTO 0 /* Define if mountlist is a struct in rpcsvc/mount.h containing the member ** ml_host. */ #define HAVE_MOUNTLIST_STRUCT 1 /* Define if mountlist is a pointer-to-struct in rpcsvc/mount.h containing ** the member ml_hostname. */ #define HAVE_MOUNTLIST_PTR 0 /* Define if we have getgrmember. */ #define HAVE_GETGRMEMBER 1 /* Define if you have /etc/xtab in the IRIX format. */ #define HAVE_IRIX_XTAB_VERIFICATION 1 /* Name of package */ #define PACKAGE "fam" /* Version number of package */ #define VERSION "2.6.0" --------------26E1EF14A61B956FF45639C4 Content-Type: text/plain; charset=us-ascii; name="config.log" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="config.log" This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. configure:566: checking for a BSD compatible install configure:619: checking whether build environment is sane configure:676: checking whether make sets ${MAKE} configure:722: checking for working aclocal configure:735: checking for working autoconf configure:748: checking for working automake configure:761: checking for working autoheader configure:774: checking for working makeinfo configure:811: checking for CC configure:849: checking for c++ configure:881: checking whether the C++ compiler (/usr/bin/CC ) works configure:897: /usr/bin/CC -o conftest conftest.C 1>&5 configure:923: checking whether the C++ compiler (/usr/bin/CC ) is a cross-compiler configure:928: checking whether we are using GNU C++ configure:956: checking whether /usr/bin/CC accepts -g configure:990: checking for ranlib configure:1030: checking for a BSD compatible install configure:1083: checking whether make sets ${MAKE} configure:1185: checking host system type configure:1206: checking build system type configure:1226: checking for gcc configure:1339: checking whether the C compiler (cc ) works configure:1355: cc -o conftest conftest.c 1>&5 configure:1381: checking whether the C compiler (cc ) is a cross-compiler configure:1386: checking whether we are using GNU C configure:1414: checking whether cc accepts -g configure:1484: checking for non-GNU ld configure:1520: checking if the linker (/usr/bin/ld) is GNU ld configure:1536: checking for BSD-compatible nm configure:1573: checking whether ln -s works configure:1618: /usr/bin/CC -c -g conftest.C 1>&5 ltconfig:579: checking whether we are using GNU C ltconfig:587: cc -E conftest.c ltconfig:601: checking for object suffix ltconfig:602: cc -c -g conftest.c 1>&5 ltconfig:795: checking if cc supports -c -o file.o ltconfig:796: cc -c -g -o out/conftest2.o conftest.c 1>&5 ltconfig:828: checking if cc supports -c -o file.lo ltconfig:829: cc -c -g -c -o conftest.lo conftest.c 1>&5 ltconfig:924: checking if cc static flag -non_shared works ltconfig:925: cc -o conftest -g -non_shared conftest.c 1>&5 ld: FATAL 9: I/O error (/usr/lib/nonshared/crt1.o): No such file or directory ltconfig:1557: checking if global_symbol_pipe works ltconfig:1558: cc -c -g conftest.c 1>&5 ltconfig:1561: eval "/usr/bin/nm -B conftest.o | sed -n -e 's/^.*[ ]\([BCDEGRST]\)[ ][ ]*\(\)\([_A-Za-z][_A-Za-z0-9]*\)$/\1 \2\3 \3/p' > conftest.nm" ltconfig:1613: cc -o conftest -g conftest.c conftstm.o 1>&5 configure:1755: checking for tar configure:1792: checking how to run the C++ preprocessor configure:1810: /usr/bin/CC -E conftest.C >/dev/null 2>conftest.out configure:1836: checking for sys/imon.h configure:1846: /usr/bin/CC -E conftest.C >/dev/null 2>conftest.out configure:1870: checking for linux/imon.h configure:1880: /usr/bin/CC -E conftest.C >/dev/null 2>conftest.out "configure", line 1876: error(4003): could not open source file "linux/imon.h" #include ^ 1 catastrophic error detected in the compilation of "conftest.C". Compilation terminated. configure: failed program was: #line 1875 "configure" #include "confdefs.h" #include configure:1925: checking for sys/statvfs.h configure:1935: /usr/bin/CC -E conftest.C >/dev/null 2>conftest.out configure:1965: checking for sys/syssgi.h configure:1975: /usr/bin/CC -E conftest.C >/dev/null 2>conftest.out configure:2005: checking for sys/fs/nfs_clnt.h configure:2015: /usr/bin/CC -E conftest.C >/dev/null 2>conftest.out configure:2053: checking SGI_NOHANG configure:2062: /usr/bin/CC -c -g conftest.C 1>&5 "configure", line 2058: error(3114): identifier "SGI_NOHANG" is undefined int i = SGI_NOHANG; ^ "configure", line 2058: warning(3262): variable "i" declared and never referenced int i = SGI_NOHANG; ^ 1 error detected in the compilation of "conftest.C". configure: failed program was: #line 2055 "configure" #include "confdefs.h" #include int main() { int i = SGI_NOHANG; ; return 0; } configure:2086: checking for _daemonize configure:2117: /usr/bin/CC -o conftest -g conftest.C 1>&5 configure:2145: checking getgrmember configure:2160: /usr/bin/CC -o conftest -g conftest.C 1>&5 configure:2190: checking for stat.st_fstype string configure:2199: /usr/bin/CC -c -g conftest.C 1>&5 "configure", line 2195: warning(3262): variable "s" declared and never referenced struct stat st; char *s = st.st_fstype; ^ configure:2224: checking for mountlist struct configure:2237: /usr/bin/CC -c -g conftest.C 1>&5 "configure", line 2233: warning(3665): variable "ml" is used before its value is set mountlist ml; char *h = ml.ml_name; ^ "configure", line 2233: warning(3262): variable "h" declared and never referenced mountlist ml; char *h = ml.ml_name; ^ configure:2305: checking mntent.h for MNTTYPE_NFS configure:2314: /usr/bin/CC -c -g conftest.C 1>&5 "configure", line 2310: warning(3262): variable "foo" declared and never referenced const char *foo = MNTTYPE_NFS; ^ configure:2333: checking mntent.h for MNTTYPE_NFS2 configure:2342: /usr/bin/CC -c -g conftest.C 1>&5 "configure", line 2338: warning(3262): variable "foo" declared and never referenced const char *foo = MNTTYPE_NFS2; ^ configure:2364: checking mntent.h for MNTTYPE_NFS3 configure:2373: /usr/bin/CC -c -g conftest.C 1>&5 "configure", line 2369: warning(3262): variable "foo" declared and never referenced const char *foo = MNTTYPE_NFS3; ^ configure:2395: checking mntent.h for MNTTYPE_CACHEFS configure:2404: /usr/bin/CC -c -g conftest.C 1>&5 "configure", line 2400: warning(3262): variable "foo" declared and never referenced const char *foo = MNTTYPE_CACHEFS; ^ configure:2426: checking netinet/in.h for bindresvport() configure:2435: /usr/bin/CC -c -g conftest.C 1>&5 "configure", line 2431: error(3114): identifier "bindresvport" is undefined int p = 0; struct sockaddr_in s; bindresvport(p, &s); ^ 1 error detected in the compilation of "conftest.C". configure: failed program was: #line 2428 "configure" #include "confdefs.h" #include int main() { int p = 0; struct sockaddr_in s; bindresvport(p, &s); ; return 0; } configure:2460: checking for prmap_sgi_t configure:2469: /usr/bin/CC -c -g conftest.C 1>&5 "configure", line 2465: error(3225): class "prmap_sgi" has no member "pr_lockcnt" prmap_sgi_t f; f.pr_lockcnt = 0; ^ 1 error detected in the compilation of "conftest.C". configure: failed program was: #line 2462 "configure" #include "confdefs.h" #include int main() { prmap_sgi_t f; f.pr_lockcnt = 0; ; return 0; } configure:2494: checking for built-in bool configure:2503: /usr/bin/CC -c -g conftest.C 1>&5 "configure", line 2499: error(3114): identifier "bool" is undefined bool foo = true; if(foo) foo = false; ^ "configure", line 2499: error(3114): identifier "true" is undefined bool foo = true; if(foo) foo = false; ^ "configure", line 2499: error(3114): identifier "false" is undefined bool foo = true; if(foo) foo = false; ^ 3 errors detected in the compilation of "conftest.C". configure: failed program was: #line 2496 "configure" #include "confdefs.h" int main() { bool foo = true; if(foo) foo = false; ; return 0; } configure:2528: checking for C++ namespace support configure:2540: /usr/bin/CC -o conftest -g conftest.C 1>&5 "configure", line 2537: error(3114): identifier "namespace" is undefined namespace foo { int bar(void) { return 0; } } int main(void) { return foo::bar(); } ^ "configure", line 2537: error(3158): expected a ";" namespace foo { int bar(void) { return 0; } } int main(void) { return foo::bar(); } ^ 2 errors detected in the compilation of "conftest.C". configure: failed program was: #line 2533 "configure" #include "confdefs.h" #ifdef __cplusplus extern "C" void exit(int); #endif namespace foo { int bar(void) { return 0; } } int main(void) { return foo::bar(); } configure:2596: checking for echo --------------26E1EF14A61B956FF45639C4-- -- To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com From owner-fam@oss.sgi.com Tue Mar 7 11:38:05 2000 Received: by oss.sgi.com id ; Tue, 7 Mar 2000 11:37:56 -0800 Received: from deliverator.sgi.com ([204.94.214.10]:62256 "EHLO deliverator.sgi.com") by oss.sgi.com with ESMTP id ; Tue, 7 Mar 2000 11:37:35 -0800 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id LAA13637 for ; Tue, 7 Mar 2000 11:32:59 -0800 (PST) mail_from (wessmith@cthulhu.engr.sgi.com) Received: from capella.engr.sgi.com (capella.engr.sgi.com [163.154.5.91]) by cthulhu.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id LAA75414; Tue, 7 Mar 2000 11:37:18 -0800 (PST) mail_from (wessmith@cthulhu.engr.sgi.com) Received: from engr.sgi.com (capella.engr.sgi.com [163.154.5.91]) by capella.engr.sgi.com (980427.SGI.8.8.8/980728.SGI.AUTOCF) via ESMTP id LAA32280; Tue, 7 Mar 2000 11:37:16 -0800 (PST) Message-ID: <38C55A6B.1350D25C@engr.sgi.com> Date: Tue, 07 Mar 2000 11:37:15 -0800 From: Wesley Smith X-Mailer: Mozilla 4.7C-SGI [en] (X11; I; IRIX 6.5-ALPHA-1286276320 IP32) X-Accept-Language: en MIME-Version: 1.0 To: "Dana E. Poulain" CC: fam@oss.sgi.com Subject: Re: [fam] Fam 2.6.0 on IRIX 6.2 References: <38C52876.F6876E5F@alltel.net> 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 "Dana E. Poulain" wrote: > > During installation of fam 2.6.0 on an R5000 IP22 Indy running IRIX > 6.2, > I've encountered the following difficulties: > > (1) Running "./configure" fails when checking "echo -e" with the > notice > > checking for echo -e flag... foo: Unknown operator > > (2) Upon commenting out the "echo -e" lines, "./configure" completes > successfully, Others on the mailing list have suggested changing the line in configure to read: if test "`$ECHO -e foo`" = 'foo'; then > but then fails during the compilation of "Client.c++" > > /usr/bin/CC -DHAVE_CONFIG_H -I. -I. -I.. -I../include > -fullwarn -woff > 1209,1355 -g -mips3 -n32 -MDupdate Makedepend -ptused -c > -DPIC > Client.c++ -o .libs/Client.lo > > "../include/Boolean.h", line 31: error(1084): invalid > combination of type specifiers > typedef int bool; > ^ > "../include/Boolean.h", line 32: error(1040): expected an > identifier > const bool true(1), false(0); > ^ > "../include/Boolean.h", line 32: error(1079): expected a type > specifier > const bool true(1), false(0); > ^ > ... more errors along same lines > > Note: "config.h" and "config.log" are attached. These errors are consistent with the errors that you would get if bool was already defined, and the code tried to redefine it. But that the configure script checked for this case: > configure:2503: /usr/bin/CC -c -g conftest.C 1>&5 > "configure", line 2499: error(3114): identifier "bool" is undefined > bool foo = true; if(foo) foo = false; > ^ > > "configure", line 2499: error(3114): identifier "true" is undefined > bool foo = true; if(foo) foo = false; > ^ > > "configure", line 2499: error(3114): identifier "false" is undefined > bool foo = true; if(foo) foo = false; > ^ > > 3 errors detected in the compilation of "conftest.C". > configure: failed program was: > #line 2496 "configure" > #include "confdefs.h" > > int main() { > bool foo = true; if(foo) foo = false; > ; return 0; } And found that the compiler didn't predefine "bool". So why is it already defined later??? You might try setting the HAVE_BOOL option in the config.h to 1, then doing a "make clean ; make" and see what happens. If that doesn't work, please send info about which version of the compiler you're using. -- Wesley Smith wessmith@engr.sgi.com (650)933-4536 -- To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com From owner-fam@oss.sgi.com Tue Mar 14 22:35:34 2000 Received: by oss.sgi.com id ; Tue, 14 Mar 2000 22:35:25 -0800 Received: from deliverator.sgi.com ([204.94.214.10]:45693 "EHLO deliverator.sgi.com") by oss.sgi.com with ESMTP id ; Tue, 14 Mar 2000 22:35:03 -0800 Received: from nodin.corp.sgi.com (fddi-nodin.corp.sgi.com [198.29.75.193]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id WAA23290 for ; Tue, 14 Mar 2000 22:30:26 -0800 (PST) mail_from (rusty@rlyeh.engr.sgi.com) Received: from rlyeh.engr.sgi.com (rlyeh.engr.sgi.com [163.154.5.94]) by nodin.corp.sgi.com (980427.SGI.8.8.8/980728.SGI.AUTOCF) via ESMTP id WAA76741 for ; Tue, 14 Mar 2000 22:34:32 -0800 (PST) Received: (from rusty@localhost) by rlyeh.engr.sgi.com (980427.SGI.8.8.8/960327.SGI.AUTOCF) id WAA54210 for fam@oss.sgi.com; Tue, 14 Mar 2000 22:31:45 -0800 (PST) From: "Rusty Ballinger" Message-Id: <10003142231.ZM237679@rlyeh.engr.sgi.com> Date: Tue, 14 Mar 2000 22:31:44 -0800 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: fam@oss.sgi.com Subject: [fam] fam-oss-2.6.1 available 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 See http://oss.sgi.com/projects/fam/ChangeLog for the included fixes. Mostly it's fixes to the configure script, although there was one big stupid breakage of the FAM API (perpetrated by me) which is fixed too. --Rusty -- To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com From owner-fam@oss.sgi.com Tue Mar 21 23:17:12 2000 Received: by oss.sgi.com id ; Tue, 21 Mar 2000 23:16:53 -0800 Received: from deliverator.sgi.com ([204.94.214.10]:10865 "EHLO deliverator.sgi.com") by oss.sgi.com with ESMTP id ; Tue, 21 Mar 2000 23:16:27 -0800 Received: from nodin.corp.sgi.com (fddi-nodin.corp.sgi.com [198.29.75.193]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id XAA27282 for ; Tue, 21 Mar 2000 23:11:48 -0800 (PST) mail_from (rusty@rlyeh.engr.sgi.com) Received: from rlyeh.engr.sgi.com (rlyeh.engr.sgi.com [163.154.5.94]) by nodin.corp.sgi.com (980427.SGI.8.8.8/980728.SGI.AUTOCF) via ESMTP id XAA87655 for ; Tue, 21 Mar 2000 23:16:26 -0800 (PST) Received: (from rusty@localhost) by rlyeh.engr.sgi.com (980427.SGI.8.8.8/960327.SGI.AUTOCF) id XAA03487; Tue, 21 Mar 2000 23:13:12 -0800 (PST) From: "Rusty Ballinger" Message-Id: <10003212313.ZM296614@rlyeh.engr.sgi.com> Date: Tue, 21 Mar 2000 23:13:11 -0800 In-Reply-To: "Andrew Morton" "fam & imon" (Mar 21, 6:52am) References: <38D71C1E.AE0E8BF1@asiapacificm01.nt.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: morton@nortelnetworks.com Subject: [fam] Re: fam & imon 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 > You guys were very quiet about this patch.... Yeah... that wasn't exactly the plan, but there are several not-very-good reasons for it. The biggest is that, at the moment, the imon-for-Linux patch is almost certainly unusable, and fam isn't very interesting without imon. Hopefully in the next day or two I will be able to spend some time trying it out, but I've been thinking that for about a week now. > Do the GNOME & KDE folks know about this? Sort of; I sent mail to a few GNOME & KDE people, and Rebecca Underwood talked to them at LinuxWorld Expo last month, so they know it's out there, but if they don't jump on it, it's our fault, not theirs. I'm not subscribed to any of their development lists, and I'm not actively pushing it the way it should be pushed. There are all kinds of things we should be doing, but we can only do them a bit at a time, so it's all going pretty slowly. (Hey, the KDE people had support for fam in their KDirWatch class even before fam was available (!), but I haven't been able to fiddle with it yet.) The two biggest things that are missing right now, I think, are a working imon for Linux, and examples/tutorials on using fam in Qt and GTK+ code. > If they are interested (and bear in mind that they're resistant to > linux-only stuff) then I believe this should be pushed along a bit. Actually, I hope fam won't be linux-only; I talked to a guy last week who pointed me at an imon-like facility which had been implemented in FreeBSD by a friend of his, and which is apparently already in the kernel. If fam is able to make use of that, it might be running with kernel support on FreeBSD before Linux! > I'd be interested in working on this in 2-4 weeks time. I suggest that > the kernel patch should be made really, really thin - much more so than > at present. Then most of the functionality can be moved into a module. Any improvements you want to make to the imon patch would be great! Right now most of what imon does is already in a module, but the way it hooks into the filesystem code is "sub-optimal" (and there are quite a few places where it intrudes into the filesystem code). I agree that the less that slops out of the module, the better. It seems like everything (or almost everything) imon does should be able to be contained, although I'm not sure about the start- and stop-exec events, as they're handled differently. > Hopefully the Gnome/KDE world has enough manpower to look after the user > space library. (which, except for porting to other platforms, shouldn't take much work.) > If the mainline patch is tiny and buyin from the GUI teams is shown, the > hard man@transmeta _may_ accept the enabling hooks in the mainstream > release. Yes, that's exactly the way I'm hoping it will go. --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 Fri Mar 24 04:30:05 2000 Received: by oss.sgi.com id ; Fri, 24 Mar 2000 04:29:55 -0800 Received: from deliverator.sgi.com ([204.94.214.10]:59507 "EHLO deliverator.sgi.com") by oss.sgi.com with ESMTP id ; Fri, 24 Mar 2000 04:29:33 -0800 Received: from nodin.corp.sgi.com (fddi-nodin.corp.sgi.com [198.29.75.193]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id EAA23699 for ; Fri, 24 Mar 2000 04:24:53 -0800 (PST) mail_from (rusty@rlyeh.engr.sgi.com) Received: from rlyeh.engr.sgi.com (rlyeh.engr.sgi.com [163.154.5.94]) by nodin.corp.sgi.com (980427.SGI.8.8.8/980728.SGI.AUTOCF) via ESMTP id EAA53132 for ; Fri, 24 Mar 2000 04:27:41 -0800 (PST) Received: (from rusty@localhost) by rlyeh.engr.sgi.com (980427.SGI.8.8.8/960327.SGI.AUTOCF) id EAA30961 for fam@oss.sgi.com; Fri, 24 Mar 2000 04:26:14 -0800 (PST) From: "Rusty Ballinger" Message-Id: <10003240426.ZM329079@rlyeh.engr.sgi.com> Date: Fri, 24 Mar 2000 04:26:12 -0800 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: fam@oss.sgi.com Subject: [fam] fam 2.6.2 (and imon 0.0.1!) available 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 There aren't any big bug fixes in this version of fam--mostly just improvements to the configure script, and a couple of things to make it easier to tell whether you've got imon support on Linux. Also, I finally got around to testing (and fixing) the imon kernel patch for Linux. It has at least one bug (monitoring a directory, and then renaming the directory, doesn't cause delete events for its contents until the directory or its contents are modified) but other than that, it works, including start- and stop-exec events. If you try it out, and it works for you, think nice thoughts about Roger Chickering, not me. (If it *doesn't* work for you... that would be my fault.) Here's the change log for fam-oss-2.6.2, as well as for 2.6.1 since I forgot to include it when I sent the 2.6.1 message. fam-oss-2.6.2 "Fixed" error message in SYSLOG when clients terminate. (The behavior is the same; now it just doesn't log an error message.) Thanks to Andras Balogh. Configure script changes: - It's better about caching the results of its tests. - If it thinks you don't have imon support, it prints out a big warning message with some advice. - The dumb tests for uname = IRIX are still dumb, but less broken; now they catch uname IRIX64, too. - Added a "support" subdir and a sample test for reimplementations of stuff that's missing on different platforms (like snprintf on 6.3), but at the moment it's empty because I didn't finish incorporating the patch which Wesley Smith sent Rolf Schreiber for compiling on IRIX 6.3. fam-oss-2.6.1 Stupid, gratuitous breakage of the FAM API introduced by Rusty in 2.6.0 has been fixed. (FAMPending and FAMNextEvent no longer worked as advertised when they got an EOF.) Thanks to Wesley Smith. The "echo -e" configure script fix is included. Thanks to Henning Meier-Geinitz, Charles E. Campbell, Robert F. Phillips II, and others. "-n32 -mips3" is no longer hard-coded in the configure script for compiling on IRIX. Now there's a better chance of the ABI being chosen correctly, and if you want to control it, you can set the ABI in your CXXFLAGS environment variable instead of having to edit the nasty configure script. Added ii_files/*.ii to CLEANFILES in some of the Makefile.am's so that SGI compiler prelinker files get cleaned up by "make clean". (Matters if you want to switch between ABIs.) The version number changed from 2.6.0 to oss-2.6.1. The "oss" is just to emphasize that the version numbers between fam-bundled-with-IRIX and fam-open-source are not comparable. (The fam which will be in IRIX 6.5.8 calls itself "fam 2.6.0", but it has some of the same fixes as the open-source 2.6.1.) I will be sorry later that I wasn't smarter about the version numbers at the start. This version does not contain a fix for the SYSLOG message when a client shuts down, and does not yet include the patch which Wesley Smith sent Rolf Schreiber for compiling on IRIX 6.3. --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 Mar 28 23:24:15 2000 Received: by oss.sgi.com id ; Tue, 28 Mar 2000 23:23:54 -0800 Received: from smtprch1.nortelnetworks.com ([192.135.215.14]:25477 "EHLO smtprch1.nortel.com") by oss.sgi.com with ESMTP id ; Tue, 28 Mar 2000 23:23:33 -0800 Received: from zrchb213.us.nortel.com (actually zrchb213) by smtprch1.nortel.com; Wed, 29 Mar 2000 01:15:55 -0600 Received: from zctwb003.asiapac.nortel.com ([47.152.32.111]) by zrchb213.us.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id HXWM3CNK; Wed, 29 Mar 2000 01:15:30 -0600 Received: from pwold011.asiapac.nortel.com ([47.181.193.45]) by zctwb003.asiapac.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id HNN1JJ5X; Wed, 29 Mar 2000 17:15:29 +1000 Received: from uow.edu.au (IDENT:akpm@localhost [127.0.0.1]) by pwold011.asiapac.nortel.com (8.9.3/8.9.3) with ESMTP id RAA15021; Wed, 29 Mar 2000 17:15:25 +1000 Message-ID: <38E1AD8D.8F398591@uow.edu.au> Date: Wed, 29 Mar 2000 07:15:25 +0000 X-Sybari-Space: 00000000 00000000 00000000 From: Andrew Morton X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.3.99-pre2 i686) X-Accept-Language: en MIME-Version: 1.0 To: rusty@sgi.com CC: fam@oss.sgi.com Subject: [fam] Re: fam & imon References: "Andrew Morton" "fam & imon" (Mar 21, 6:52am), <38D71C1E.AE0E8BF1@asiapacificm01.nt.com> <10003212313.ZM296614@rlyeh.engr.sgi.com> 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 Rusty Ballinger wrote: > > > You guys were very quiet about this patch.... > > Yeah... that wasn't exactly the plan, Hi, Rusty. Thanks for the reply. Unfortunately my stated intention to look at imon in "2-4 weeks time" isn't looking good at present :-( Am I right in my understanding that this facility tells interested userland applications two main things: 1: That an executable is currently being executed and 2: That an inode has been altered? If so, I'm wondering how much value number 1 provides. For desktop file browsers, number 2 is more important? Also, there are many, many other applications which could benefit from number 2. Any sort of app which monitors logfiles or spool directories. 'tail -f', come to that. If I'm not missing something, have you considered splitting off feature 1 and submitting only the inode-mod feature? If this reduces the intrusiveness of the kernel patch this may ease its path into the mainstream release. -- -akpm- -- 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 Mar 29 15:30:31 2000 Received: by oss.sgi.com id ; Wed, 29 Mar 2000 15:30:12 -0800 Received: from deliverator.sgi.com ([204.94.214.10]:24880 "EHLO deliverator.sgi.com") by oss.sgi.com with ESMTP id ; Wed, 29 Mar 2000 15:29:48 -0800 Received: from nodin.corp.sgi.com (nodin.corp.sgi.com [192.26.51.193]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id PAA27105 for ; Wed, 29 Mar 2000 15:25:08 -0800 (PST) mail_from (rusty@rlyeh.engr.sgi.com) Received: from rlyeh.engr.sgi.com (rlyeh.engr.sgi.com [163.154.5.94]) by nodin.corp.sgi.com (980427.SGI.8.8.8/980728.SGI.AUTOCF) via ESMTP id PAA24573 for ; Wed, 29 Mar 2000 15:29:47 -0800 (PST) Received: (from rusty@localhost) by rlyeh.engr.sgi.com (980427.SGI.8.8.8/960327.SGI.AUTOCF) id PAA03198; Wed, 29 Mar 2000 15:26:34 -0800 (PST) From: "Rusty Ballinger" Message-Id: <10003291526.ZM3199@rlyeh.engr.sgi.com> Date: Wed, 29 Mar 2000 15:26:34 -0800 In-Reply-To: Andrew Morton "[fam] Re: fam & imon" (Mar 29, 7:15am) References: "Andrew Morton" "fam & imon" (Mar 21 6:52am) <38D71C1E.AE0E8BF1@asiapacificm01.nt.com> <10003212313.ZM296614@rlyeh.engr.sgi.com> <38E1AD8D.8F398591@uow.edu.au> 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: andrewm@uow.edu.au Subject: Re: [fam] Re: fam & imon 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 > Unfortunately my stated intention to look at imon in "2-4 weeks time" > isn't looking good at present :-( Well, it can't be any worse than my stated intention to look at imon "in the next day or two." (I did start fiddling with the 2.3.42 patch in a 2.3.99-pre3 tree, and promptly broke it.) > Am I right in my understanding that this facility tells interested > userland applications two main things: > > 1: That an executable is currently being executed and > > 2: That an inode has been altered? > > If so, I'm wondering how much value number 1 provides. For desktop file > browsers, number 2 is more important? Yeah, the start/stop exec stuff isn't nearly as useful. You get notified when the number of running instances of a program changes from 0 to 1 or back again, or when at least one instance is running when you start monitoring it. I think all it's used for in IRIX is changing desktop icons to indicate whether a program is running, which is about all you *can* use it for, because you don't know who's running the program, or with what arguments; you don't receive notification when additional instances start up, etc. > If I'm not missing something, have you considered splitting off feature > 1 and submitting only the inode-mod feature? If this reduces the > intrusiveness of the kernel patch this may ease its path into the > mainstream release. That's a good idea, and no, I hadn't considered it. The start/stop-exec notification certainly isn't essential, and I don't think there's a way to contain it in the imon module, which probably does make it an impediment to the eventual acceptance of the rest of the imon stuff. --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 Thu Mar 30 11:25:45 2000 Received: by oss.sgi.com id ; Thu, 30 Mar 2000 11:25:35 -0800 Received: from nat-su-33.valinux.com ([198.186.202.33]:16715 "EHLO raster.su.valinux.com") by oss.sgi.com with ESMTP id ; Thu, 30 Mar 2000 11:25:25 -0800 Received: (from raster@localhost) by raster.su.valinux.com (8.9.3/8.9.3) id MAA28961 for fam@oss.sgi.com; Thu, 30 Mar 2000 12:24:13 -0800 Message-Id: <200003302024.MAA28961@raster.su.valinux.com> Date: Thu, 30 Mar 2000 12:24:13 -0800 (PST) From: raster@rasterman.com Reply-To: raster@rasterman.com Subject: [fam] patch to fix fam to compile when imon isn't there.... To: fam@oss.sgi.com MIME-Version: 1.0 Content-Type: MULTIPART/mixed; BOUNDARY="17446913-1804289383-954447853=:28777" Sender: owner-fam@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;fam-outgoing --17446913-1804289383-954447853=:28777 Content-Type: TEXT/plain; CHARSET=US-ASCII here's a patch to make sure fam actrually compiles if you cant patch your kenrel with imon....... :) (NB - any idea on a backport to 2.2.14/15 ? ) :) -- --------------- Codito, ergo sum - "I code, therefore I am" -------------------- The Rasterman (Carsten Haitzler) raster@rasterman.com raster@valinux.com raster@enlightenment.org raster@linux.com raster@zip.com.au --17446913-1804289383-954447853=:28777 Content-Type: TEXT/plain; CHARSET=US-ASCII Content-Description: patch --- fam-oss-2.6.2/fam/IMonNone.c++~ Thu Mar 23 16:30:16 2000 +++ fam-oss-2.6.2/fam/IMonNone.c++ Thu Mar 30 12:05:46 2000 @@ -21,6 +21,7 @@ // Temple Place - Suite 330, Boston MA 02111-1307, USA. #include "IMon.h" +#include "Log.h" int IMon::imon_open() { --17446913-1804289383-954447853=:28777-- -- 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 Mar 30 16:46:23 2000 Received: by oss.sgi.com id ; Thu, 30 Mar 2000 16:46:03 -0800 Received: from nat-su-33.valinux.com ([198.186.202.33]:4427 "EHLO mandrake.net") by oss.sgi.com with ESMTP id ; Thu, 30 Mar 2000 16:45:34 -0800 Received: (from raster@localhost) by mandrake.net (8.9.3/8.8.7) id RAA03597 for fam@oss.sgi.com; Thu, 30 Mar 2000 17:44:25 -0800 Message-Id: <200003310144.RAA03597@mandrake.net> Date: Thu, 30 Mar 2000 17:44:25 -0800 (PST) From: raster@rasterman.com Reply-To: raster@rasterman.com Subject: [fam] refcounting..... To: 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 does fam refcount "watches" ie - if i ask fam to monitor a directory twice does it wait till i ask it twice to stop monitoring? (just wondering as i'm writign my abstraction layer right now and i wodner if i need to refcount watches myself) als will it send 1 or 2 changed events if i asked twice? hmmm i guess it will send 2 - one per famrequest id right? thats a guess.. :) -- --------------- Codito, ergo sum - "I code, therefore I am" -------------------- The Rasterman (Carsten Haitzler) raster@rasterman.com raster@valinux.com raster@enlightenment.org raster@linux.com raster@zip.com.au -- 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 Mar 30 16:55:53 2000 Received: by oss.sgi.com id ; Thu, 30 Mar 2000 16:55:44 -0800 Received: from pneumatic-tube.sgi.com ([204.94.214.22]:35340 "EHLO pneumatic-tube.sgi.com") by oss.sgi.com with ESMTP id ; Thu, 30 Mar 2000 16:55:18 -0800 Received: from rlyeh.engr.sgi.com (rlyeh.engr.sgi.com [163.154.5.94]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id QAA04772 for ; Thu, 30 Mar 2000 16:58:54 -0800 (PST) mail_from (rusty@rlyeh.engr.sgi.com) Received: (from rusty@localhost) by rlyeh.engr.sgi.com (980427.SGI.8.8.8/960327.SGI.AUTOCF) id QAA09592 for fam@oss.sgi.com; Thu, 30 Mar 2000 16:53:42 -0800 (PST) From: "Rusty Ballinger" Message-Id: <10003301653.ZM9612@rlyeh.engr.sgi.com> Date: Thu, 30 Mar 2000 16:53:41 -0800 In-Reply-To: raster@rasterman.com "[fam] refcounting....." (Mar 30, 5:44pm) References: <200003310144.RAA03597@mandrake.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: fam@oss.sgi.com Subject: Re: [fam] refcounting..... 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 > ie - if i ask fam to monitor a directory twice does it wait till i ask > it twice to stop monitoring? (just wondering as i'm writign my > abstraction layer right now and i wodner if i need to refcount watches > myself) als will it send 1 or 2 changed events if i asked twice? hmmm i > guess it will send 2 - one per famrequest id right? thats a guess.. :) Yeah, I just tried the little test program, and if you ask it to monitor the same directory twice, you get two events for each file. When you ask it to stop monitoring, I think that's done per fam-request too, so you'd have to ask it to stop monitoring twice as well. --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 Thu Mar 30 17:14:23 2000 Received: by oss.sgi.com id ; Thu, 30 Mar 2000 17:14:14 -0800 Received: from nat-su-33.valinux.com ([198.186.202.33]:60745 "EHLO mandrake.net") by oss.sgi.com with ESMTP id ; Thu, 30 Mar 2000 17:13:50 -0800 Received: (from raster@localhost) by mandrake.net (8.9.3/8.8.7) id SAA04204; Thu, 30 Mar 2000 18:12:40 -0800 Message-Id: <200003310212.SAA04204@mandrake.net> Date: Thu, 30 Mar 2000 18:12:40 -0800 (PST) From: raster@rasterman.com Reply-To: raster@rasterman.com Subject: Re: [fam] refcounting..... To: rusty@sgi.com cc: rusty@rlyeh.engr.sgi.com, fam@oss.sgi.com In-Reply-To: <10003301653.ZM9612@rlyeh.engr.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 On 30 Mar, Rusty Ballinger scribbled: -> > ie - if i ask fam to monitor a directory twice does it wait till i ask -> > it twice to stop monitoring? (just wondering as i'm writign my -> > abstraction layer right now and i wodner if i need to refcount watches -> > myself) als will it send 1 or 2 changed events if i asked twice? hmmm i -> > guess it will send 2 - one per famrequest id right? thats a guess.. :) -> -> Yeah, I just tried the little test program, and if you ask it to monitor -> the same directory twice, you get two events for each file. When you -> ask it to stop monitoring, I think that's done per fam-request too, so -> you'd have to ask it to stop monitoring twice as well. just makign sure... :) that means i have to really refcoutn AND keep track of per req id... yay! :) thank god it works ok :) -- --------------- Codito, ergo sum - "I code, therefore I am" -------------------- The Rasterman (Carsten Haitzler) raster@rasterman.com raster@valinux.com raster@enlightenment.org raster@linux.com raster@zip.com.au -- 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 Mar 30 19:05:15 2000 Received: by oss.sgi.com id ; Thu, 30 Mar 2000 19:05:06 -0800 Received: from pneumatic-tube.sgi.com ([204.94.214.22]:15894 "EHLO pneumatic-tube.sgi.com") by oss.sgi.com with ESMTP id ; Thu, 30 Mar 2000 19:04:44 -0800 Received: from rlyeh.engr.sgi.com (rlyeh.engr.sgi.com [163.154.5.94]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id TAA06874 for ; Thu, 30 Mar 2000 19:08:24 -0800 (PST) mail_from (rusty@rlyeh.engr.sgi.com) Received: (from rusty@localhost) by rlyeh.engr.sgi.com (980427.SGI.8.8.8/960327.SGI.AUTOCF) id TAA09566 for fam@oss.sgi.com; Thu, 30 Mar 2000 19:03:11 -0800 (PST) From: "Rusty Ballinger" Message-Id: <10003301903.ZM9960@rlyeh.engr.sgi.com> Date: Thu, 30 Mar 2000 19:03:10 -0800 In-Reply-To: raster@rasterman.com "[fam] patch to fix fam to compile when imon isn't there...." (Mar 30, 12:24pm) References: <200003302024.MAA28961@raster.su.valinux.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: fam@oss.sgi.com Subject: Re: [fam] patch to fix fam to compile when imon isn't there.... 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 a patch to make sure fam actrually compiles if you cant patch > your kenrel with imon....... :) Dohh!! Thanks. (I broke that in 2.6.2, trying to be helpful.) I'm still fairly optimistic that at some point, there will be a ChangeLog entry which doesn't say "fixing problem caused by rusty in last version..." > (NB - any idea on a backport to 2.2.14/15 ? ) I just put a barely-tested 2.2.13 patch at ftp://oss.sgi.com/projects/fam/download/imon-0.0.1-2.2.13.gz. I haven't tried applying it to a 2.2.14 tree; let me know how that goes. The 2.2.13 version still has the same problem as the 2.3.42 version, where if you're monitoring a directory, and the directory is renamed, you don't get delete events for its contents until its contents are otherwise modified, which sucks. NOTE that if you apply the patch, and want to rebuild fam, you'll have to rerun fam's configure script (remove your config.cache first), and probably do a "make clean" (or at least rm fam/IMon.o) before building, because dependency tracking is broken/disabled in the makefiles. --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 Thu Mar 30 20:22:06 2000 Received: by oss.sgi.com id ; Thu, 30 Mar 2000 20:21:56 -0800 Received: from behemoth.vergenet.net ([198.186.202.43]:7692 "EHLO behemoth.su.varesearch.com") by oss.sgi.com with ESMTP id ; Thu, 30 Mar 2000 20:21:44 -0800 Received: (from raster@localhost) by behemoth.su.varesearch.com (8.9.3/8.9.3) id UAA06886; Thu, 30 Mar 2000 20:23:35 -0800 Message-Id: <200003310423.UAA06886@behemoth.su.varesearch.com> Date: Thu, 30 Mar 2000 20:23:26 -0800 (PST) From: raster@rasterman.com Reply-To: raster@rasterman.com Subject: Re: [fam] patch to fix fam to compile when imon isn't there.... To: rusty@sgi.com cc: rusty@rlyeh.engr.sgi.com, fam@oss.sgi.com In-Reply-To: <10003301903.ZM9960@rlyeh.engr.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 On 30 Mar, Rusty Ballinger scribbled: -> > here's a patch to make sure fam actrually compiles if you cant patch -> > your kenrel with imon....... :) -> -> Dohh!! Thanks. (I broke that in 2.6.2, trying to be helpful.) -> -> I'm still fairly optimistic that at some point, there will be a ChangeLog -> entry which doesn't say "fixing problem caused by rusty in last version..." -> -> > (NB - any idea on a backport to 2.2.14/15 ? ) -> -> I just put a barely-tested 2.2.13 patch at -> ftp://oss.sgi.com/projects/fam/download/imon-0.0.1-2.2.13.gz. I haven't -> tried applying it to a 2.2.14 tree; let me know how that goes. must have just gone up - it wasnt there eralier today when i downloaded it :) i'll give it a shot.. i wont be testing renaming for a while... just adds, deletes and changes are my priority right now.. :) -> The 2.2.13 version still has the same problem as the 2.3.42 version, where -> if you're monitoring a directory, and the directory is renamed, you don't -> get delete events for its contents until its contents are otherwise -> modified, which sucks. poke me with a glowing hot iron rod.... but for renames shouldn't I get a Move event? for the base dir that is... ? -> NOTE that if you apply the patch, and want to rebuild fam, you'll have to -> rerun fam's configure script (remove your config.cache first), and probably -> do a "make clean" (or at least rm fam/IMon.o) before building, because -> dependency tracking is broken/disabled in the makefiles. yup - i guessed at that... i do it out of habit anyway... :) -- --------------- Codito, ergo sum - "I code, therefore I am" -------------------- The Rasterman (Carsten Haitzler) raster@rasterman.com raster@valinux.com raster@enlightenment.org raster@linux.com raster@zip.com.au -- Source code, list archive, and docs: http://oss.sgi.com/projects/fam/ To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com