From owner-fam@oss.sgi.com Mon Apr 23 13:18:31 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.3/8.11.3) id f3NKIVO09562 for fam-outgoing; Mon, 23 Apr 2001 13:18:31 -0700 Received: from mailout02.sul.t-online.com (mailout02.sul.t-online.com [194.25.134.17]) by oss.sgi.com (8.11.3/8.11.3) with ESMTP id f3NKITM09553 for ; Mon, 23 Apr 2001 13:18:29 -0700 Received: from fwd03.sul.t-online.com by mailout02.sul.t-online.com with smtp id 14rmms-00060a-0I; Mon, 23 Apr 2001 22:18:22 +0200 Received: from servant.home.lan (320028254634-0001@[217.80.32.156]) by fwd03.sul.t-online.com with esmtp id 14rmmv-09CJQuC; Mon, 23 Apr 2001 22:18:25 +0200 Received: from there (IDENT:malte@xray.home.lan [172.16.0.2]) by servant.home.lan (8.11.0/8.11.0) with SMTP id f3NKIJk08380 for ; Mon, 23 Apr 2001 22:18:19 +0200 Message-Id: <200104232018.f3NKIJk08380@servant.home.lan> Content-Type: text/plain; charset="iso-8859-1" From: Malte.Starostik@t-online.de (Malte Starostik) To: fam@oss.sgi.com Subject: [fam] fam, xinetd, kernel 2.4.x Date: Mon, 23 Apr 2001 22:18:18 +0200 X-Mailer: KMail [version 1.2.1] X-Security-Warning: All your Base Are Belong to Us! MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Sender: 320028254634-0001@t-dialin.net Sender: owner-fam@oss.sgi.com Precedence: bulk Hi, I just read the thread about fam & rh7 in the archive and would like to share my own experience with fam and xinetd and newer kernels than 2.4.0-test9. I'm running Mandrake 7.2, which also uses xinetd (can't remember if it's the default over inetd but IIRC it is). Please CC me for answers as I'm not subscribed, could do so though, if neccessary. I'm using this as /etc/xinetd.d/sgi_fam: service sgi_fam { disable = no type = RPC rpc_version = 1-2 rpc_number = sgi_fam socket_type = stream protocol = tcp wait = yes user = root server = /usr/local/bin/fam } It's working perfectly with that (I use it with KDE). The imon patch for 2.4.0-test9 applies cleanly to all 2.4 versions I tried (several 0-tests, 0, 1, 2 and 3) and seems to work well. I use it with reiserfs plus the reiserfs-nfs patches and didn't expect any problems. There is one little buglet in linux/fs/imon/Config.in though: # # imon configuration # comment 'Inode monitor support (experimental)' tristate 'Inode monitor support (experimental)' CONFIG_IMON ^^^^^^^^ this should be bool instead of tristate as tristate allows to configure imon as a module, but doing so results in a whole bunch of undefined references when linking the filesystem code during kernel builds. BTW, Mandrake's /etc/init.d/xinetd kills xinetd with -USR2 to reload the config, so I'd propose a procedure like this for the rpm's post script: - Check with /sbin/pidof whether inetd is running - if so, patch /etc/inetd.conf and run /sbin/killall -HUP inetd - else, install /etc/xinetd.d/sgi_fam and run /sbin/killall -USR2 inetd Sorry, no time to write a real script for that now. On a totally unrelated thing, when do you expect 2.6.5 to be available? Will it include a fix for using fam concurrently as different users (non-root & root or two non-root)? This, as stated in your known bugs section doesn't work at all and renders kdesu (KDE's wrapper around su that cares about the KDE daemons and X authentication etc.) useless when KDE is compiled with fam support - it'll just hang :( If the 2.6.5 release should take a while, is this issue already fixed, are some unstable packages available? Thanks, -Malte -- 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 Apr 23 18:49:14 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.3/8.11.3) id f3O1nEC23668 for fam-outgoing; Mon, 23 Apr 2001 18:49:14 -0700 Received: from roujin.gargoylecc.com (roujin.gargoylecc.com [65.100.85.34]) by oss.sgi.com (8.11.3/8.11.3) with ESMTP id f3O1nDM23665 for ; Mon, 23 Apr 2001 18:49:13 -0700 Received: from lists.gargoylecc.com (IDENT:ringram@gargoyle.gargoylecc.com [65.100.85.35]) by roujin.gargoylecc.com (8.9.3/8.9.3) with ESMTP id KAA01597; Tue, 24 Apr 2001 10:20:24 -0600 Date: Mon, 23 Apr 2001 19:53:16 -0600 (MDT) From: Russel Ingram X-X-Sender: To: Malte Starostik cc: Subject: Re: [fam] fam, xinetd, kernel 2.4.x In-Reply-To: <200104232018.f3NKIJk08380@servant.home.lan> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-fam@oss.sgi.com Precedence: bulk On Mon, 23 Apr 2001, Malte Starostik wrote: > Hi, > > I just read the thread about fam & rh7 in the archive and would like to share > my own experience with fam and xinetd and newer kernels than 2.4.0-test9. > I'm running Mandrake 7.2, which also uses xinetd (can't remember if it's the > default over inetd but IIRC it is). Please CC me for answers as I'm not > subscribed, could do so though, if neccessary. > > I'm using this as /etc/xinetd.d/sgi_fam: > > service sgi_fam > { > disable = no > type = RPC > rpc_version = 1-2 > rpc_number = sgi_fam > socket_type = stream > protocol = tcp > wait = yes > user = root > server = /usr/local/bin/fam > } > > It's working perfectly with that (I use it with KDE). > The imon patch for 2.4.0-test9 applies cleanly to all 2.4 versions I tried > (several 0-tests, 0, 1, 2 and 3) and seems to work well. I use it with > reiserfs plus the reiserfs-nfs patches and didn't expect any problems. > There is one little buglet in linux/fs/imon/Config.in though: > > # > # imon configuration > # > > comment 'Inode monitor support (experimental)' > tristate 'Inode monitor support (experimental)' CONFIG_IMON > ^^^^^^^^ > this should be bool instead of tristate as tristate allows to configure imon > as a module, but doing so results in a whole bunch of undefined references > when linking the filesystem code during kernel builds. > > BTW, Mandrake's /etc/init.d/xinetd kills xinetd with -USR2 to reload the > config, so I'd propose a procedure like this for the rpm's post script: > - Check with /sbin/pidof whether inetd is running > - if so, patch /etc/inetd.conf and run /sbin/killall -HUP inetd > - else, install /etc/xinetd.d/sgi_fam and run /sbin/killall -USR2 inetd > > Sorry, no time to write a real script for that now. > This was perfect timing for me. I decided this morning that I was going to try applying the imon patch to the 2.4.3-xfs kernel (also from oss.sgi.com) and see if I couldn't get a working post 2.4.0 kernel with imon. I tried it and just as Malte said it doesn't compile when selected as a module. I may have read the help doc in the kernel config wrong, but I could have sworn it said that it had to be selected as a module. The compile did go through without a hitch once I switched it to be statically linked into the kernel, however (thanx Malte). Now the only question I have is where the best place to find fam/imon aware apps is. I need some that will work on the blackbox window manager. I am pretty sure blackbox will run gnome apps, but I'm not sure about KDE apps. Will I have to modify the apps I want to use myself? Thanx, Russ -- Russ Ingram Gargoyle Computer Consulting (307)742-1361 www.gargoylecc.com -- Source code, list archive, and docs: http://oss.sgi.com/projects/fam/ To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com From owner-fam@oss.sgi.com Tue Apr 24 15:36:12 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.3/8.11.3) id f3OMaCH06972 for fam-outgoing; Tue, 24 Apr 2001 15:36:12 -0700 Received: from mailout06.sul.t-online.com (mailout06.sul.t-online.com [194.25.134.19]) by oss.sgi.com (8.11.3/8.11.3) with ESMTP id f3OMaBM06969 for ; Tue, 24 Apr 2001 15:36:11 -0700 Received: from fwd04.sul.t-online.com by mailout06.sul.t-online.com with smtp id 14sBPh-0000L4-03; Wed, 25 Apr 2001 00:36:05 +0200 Received: from servant.home.lan (320028254634-0001@[217.0.37.156]) by fwd04.sul.t-online.com with esmtp id 14sBPg-1bAbZIC; Wed, 25 Apr 2001 00:36:04 +0200 Received: from there (IDENT:malte@xray.home.lan [172.16.0.2]) by servant.home.lan (8.11.0/8.11.0) with SMTP id f3OMZsk28468; Wed, 25 Apr 2001 00:35:55 +0200 Message-Id: <200104242235.f3OMZsk28468@servant.home.lan> Content-Type: text/plain; charset="iso-8859-1" From: Malte.Starostik@t-online.de (Malte Starostik) To: Russel Ingram , Malte Starostik Subject: Re: [fam] fam, xinetd, kernel 2.4.x Date: Wed, 25 Apr 2001 00:35:54 +0200 X-Mailer: KMail [version 1.2.1] Cc: References: In-Reply-To: X-Security-Warning: All your Base Are Belong to Us! MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Sender: 320028254634-0001@t-dialin.net Sender: owner-fam@oss.sgi.com Precedence: bulk On Dienstag, 24. April 2001 03:53, Russel Ingram wrote: > On Mon, 23 Apr 2001, Malte Starostik wrote: > > Hi, > > > > It's working perfectly with that (I use it with KDE). > > The imon patch for 2.4.0-test9 applies cleanly to all 2.4 versions I > > tried (several 0-tests, 0, 1, 2 and 3) and seems to work well. I use it > > with reiserfs plus the reiserfs-nfs patches and didn't expect any s/expect/experience/ of course :) > > problems. There is one little buglet in linux/fs/imon/Config.in though: > > > > comment 'Inode monitor support (experimental)' > > tristate 'Inode monitor support (experimental)' CONFIG_IMON > > ^^^^^^^^ > > this should be bool instead of tristate as tristate allows to configure > > imon as a module, but doing so results in a whole bunch of undefined > > references when linking the filesystem code during kernel builds. > > > This was perfect timing for me. I decided this morning that I was going > to try applying the imon patch to the 2.4.3-xfs kernel (also from > oss.sgi.com) and see if I couldn't get a working post 2.4.0 kernel with > imon. I tried it and just as Malte said it doesn't compile when selected > as a module. I may have read the help doc in the kernel config wrong, but > I could have sworn it said that it had to be selected as a module. Oh right, just checked. Hehe, haven't read the help about that configure option in a while :) Should be changed IMHO. > The compile did go through without a hitch once I switched it to be > statically linked into the kernel, however (thanx Malte). Now the only > question I have is where the best place to find fam/imon aware apps is. I > need some that will work on the blackbox window manager. > I am pretty sure blackbox will run gnome apps, but I'm not sure about KDE > apps. Will I have to modify the apps I want to use myself? I didn't ever run/test Blackbox myself, but I have heard of users running KDE apps on it. IIRC there are or at least were some problems, don't know about the current status. If you have any problems with KDE apps on Blackbox, feel free to file a bug report on bugs.kde.org. KDE apps should run on any window manager. Some features might be missing, if the WM isn't NETWM compliant, but if the whole app breaks, it's either a problem with the KDE libs or in the specific app. The libkio library contains the KDirWatch class will automatically use Fam, if kdelibs was built against it. Otherwise it falls back to polling or latest versions can also use Linux 2.4.x's dirnotifications. (I guess binary packages don't use either fam or dnotify, so to be sure, compile kdelibs yourself). Check with ldd $KDEDIR/lib/libkio.so - KDEDIR being the path to your KDE installation if it links to libfam For me it tells (among alot of others): libfam.so.0 => /usr/local/lib/libfam.so.0 (0x402e3000) I have no idea if any GNOME app uses Fam, you might check with some GNOME mailing list or grep the sources :) -Malte -- 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 Apr 24 15:41:49 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.3/8.11.3) id f3OMfnD07160 for fam-outgoing; Tue, 24 Apr 2001 15:41:49 -0700 Received: from smtp1.Stanford.EDU (smtp1.Stanford.EDU [171.64.14.23]) by oss.sgi.com (8.11.3/8.11.3) with ESMTP id f3OMfmM07156 for ; Tue, 24 Apr 2001 15:41:48 -0700 Received: from stanford.edu (null.Stanford.EDU [128.12.54.52]) by smtp1.Stanford.EDU (8.11.1/8.11.1) with ESMTP id f3OMfMq20192; Tue, 24 Apr 2001 15:41:23 -0700 (PDT) Message-ID: <3AE60112.4DB8FEB1@stanford.edu> Date: Tue, 24 Apr 2001 15:41:22 -0700 From: Seth Nickell Reply-To: seth@eazel.com X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.3 i686) X-Accept-Language: en MIME-Version: 1.0 To: Malte Starostik CC: Russel Ingram , fam@oss.sgi.com Subject: Re: [fam] fam, xinetd, kernel 2.4.x References: <200104242235.f3OMZsk28468@servant.home.lan> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-fam@oss.sgi.com Precedence: bulk > I have no idea if any GNOME app uses Fam, you might check with some GNOME > mailing list or grep the sources :) I added FAM support to Nautilus (the GNOME fm) a few weeks ago. -seth -- 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 Sat Apr 28 10:44:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.3/8.11.3) id f3SHixp32557 for fam-outgoing; Sat, 28 Apr 2001 10:44:59 -0700 Received: from chmls06.mediaone.net (chmls06.mediaone.net [24.147.1.144]) by oss.sgi.com (8.11.3/8.11.3) with ESMTP id f3SHivM32554 for ; Sat, 28 Apr 2001 10:44:58 -0700 Received: from h000103c16cb1.ne.mediaone.net (root@h000103c16cb1.ne.mediaone.net [66.31.94.234]) by chmls06.mediaone.net (8.11.1/8.11.1) with ESMTP id f3SHif811575 for ; Sat, 28 Apr 2001 13:44:42 -0400 (EDT) Received: from praetorian.dyn.dhs.org (moss@localhost [127.0.0.1]) by localhost (8.12.0.Beta7/8.12.0.Beta7/Debian 8.12.0.Beta7-1) with ESMTP id f3SHiurv003423 for ; Sat, 28 Apr 2001 13:44:56 -0400 Received: (from moss@localhost) by praetorian.dyn.dhs.org (8.12.0.Beta7/8.12.0.Beta7/Debian 8.12.0.Beta7-1) id f3SHitKH003421 for fam@oss.sgi.com; Sat, 28 Apr 2001 13:44:55 -0400 Date: Sat, 28 Apr 2001 13:44:55 -0400 From: James Moss To: fam@oss.sgi.com Subject: [fam] imon patch kludge Message-ID: <20010428134455.A32108@praetorian.dyn.dhs.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mojUlQ0s9EVzWg2t" Content-Disposition: inline User-Agent: Mutt/1.3.17i Sender: owner-fam@oss.sgi.com Precedence: bulk --mojUlQ0s9EVzWg2t Content-Type: multipart/mixed; boundary="RnlQjJ0d97Da+TV1" Content-Disposition: inline --RnlQjJ0d97Da+TV1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Well, I just subscribed to this list after experiencing some problems patching imon into the linux-2.4.4 source tree. The only part that I noticed failed was the patching of fs/filesystems.c. Not knowing exactly all that much about what to do to fix it, I began adding it by hand to see if I could just temporarily kludge it for the time being. I've included what I did in the patch below. I'd be interested in knowing exactly if what I've done is acceptable and if this is a valid fix. My guess is that this solution is definitely a stop gap thing since it appears most of the stuff that was previously in fs/filesystems.c has migrated elsewhere. -James Moss --RnlQjJ0d97Da+TV1 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="imon-kludge.diff" Content-Transfer-Encoding: quoted-printable --- filesystems.c~ Wed Apr 18 02:23:12 2001 +++ filesystems.c Sat Apr 28 13:42:34 2001 @@ -12,6 +12,11 @@ #include #include #include +#include + +#ifdef CONFIG_IMON +extern int init_imon(void) __init; +#endif =20 #if defined(CONFIG_NFSD_MODULE) struct nfsd_linkage *nfsd_linkage =3D NULL; @@ -38,3 +43,7 @@ return -ENOSYS; } #endif /* CONFIG_NFSD */ + +#ifdef CONFIG_IMON + int init_imon(); +#endif --RnlQjJ0d97Da+TV1-- --mojUlQ0s9EVzWg2t Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE66wGXELzfQYyO+wsRAh7IAJ9+XPQnPpR2qy2IjaDcObv2mbGvDQCdGWbi M5JGwh7MfTKAK8P93v5EqtA= =bmDE -----END PGP SIGNATURE----- --mojUlQ0s9EVzWg2t-- -- 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 Sat Apr 28 11:28:34 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.3/8.11.3) id f3SISYJ02183 for fam-outgoing; Sat, 28 Apr 2001 11:28:34 -0700 Received: from chmls20.mediaone.net (chmls20.mediaone.net [24.147.1.156]) by oss.sgi.com (8.11.3/8.11.3) with ESMTP id f3SISXM02180 for ; Sat, 28 Apr 2001 11:28:33 -0700 Received: from h000103c16cb1.ne.mediaone.net (root@h000103c16cb1.ne.mediaone.net [66.31.94.234]) by chmls20.mediaone.net (8.11.1/8.11.1) with ESMTP id f3SISH629255 for ; Sat, 28 Apr 2001 14:28:17 -0400 (EDT) Received: from praetorian.dyn.dhs.org (moss@localhost [127.0.0.1]) by localhost (8.12.0.Beta7/8.12.0.Beta7/Debian 8.12.0.Beta7-1) with ESMTP id f3SISVEF000573 for ; Sat, 28 Apr 2001 14:28:31 -0400 Received: (from moss@localhost) by praetorian.dyn.dhs.org (8.12.0.Beta7/8.12.0.Beta7/Debian 8.12.0.Beta7-1) id f3SISVdS000571 for fam@oss.sgi.com; Sat, 28 Apr 2001 14:28:31 -0400 Date: Sat, 28 Apr 2001 14:28:31 -0400 From: James Moss To: fam@oss.sgi.com Subject: [fam] imon patch kludge aftermath Message-ID: <20010428142831.A563@praetorian.dyn.dhs.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="fUYQa+Pmc3FrFX/N" Content-Disposition: inline User-Agent: Mutt/1.3.17i Sender: owner-fam@oss.sgi.com Precedence: bulk --fUYQa+Pmc3FrFX/N Content-Type: text/plain; charset=us-ascii Content-Disposition: inline While the patch I submitted does seem to fix the imon patch break, it doesn't work. Fam has resorted to polling instead of using imon when I use this patch. -James Moss --fUYQa+Pmc3FrFX/N Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE66wvPELzfQYyO+wsRAit1AJ9Oyr02zJBmp/+jgax8GQ0bQieJcgCgvC9Y vF4qGKY2ddpnBvjj1duLSR4= =YPRR -----END PGP SIGNATURE----- --fUYQa+Pmc3FrFX/N-- -- Source code, list archive, and docs: http://oss.sgi.com/projects/fam/ To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com