From owner-fam@oss.sgi.com Wed Aug 23 00:12:34 2000 Received: by oss.sgi.com id ; Wed, 23 Aug 2000 00:12:23 -0700 Received: from pneumatic-tube.sgi.com ([204.94.214.22]:18045 "EHLO pneumatic-tube.sgi.com") by oss.sgi.com with ESMTP id ; Wed, 23 Aug 2000 00:12:04 -0700 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 AAA01323 for ; Wed, 23 Aug 2000 00:18:21 -0700 (PDT) mail_from (rusty@rlyeh.engr.sgi.com) Received: (from rusty@localhost) by rlyeh.engr.sgi.com (SGI-8.9.3/8.9.3) id AAA12925; Wed, 23 Aug 2000 00:10:17 -0700 (PDT) From: "Rusty Ballinger" Message-Id: <10008230010.ZM12865@rlyeh.engr.sgi.com> Date: Wed, 23 Aug 2000 00:10:16 -0700 In-Reply-To: Lyle Kempler "fam" (Aug 19, 11:52pm) References: X-Face: #)4}U4e`O6YEe%oBzE}>ycmT!Xt?Myiqo~|p3Wh'UuQ[N7)&4\4?8:1n)bmPX]b@#k94%!VojpODdmk:sCr1b\-aXD&P:wjBqupMB:ag6}BwVseJZM@K{$E|0J9}&,Rpdg{&N4/Y8&PTm6>|r[,gI2T*qN!`AZhl>Bdy7JR`dDvP(/pz.}?Q@dg':mlV`RX51Z_ZG?Gta|Q!iA[MaOh Reply-To: rusty@sgi.com X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: kempler@utdallas.edu Subject: [fam] Re: 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 (cc'ing the fam mailing list in case other people may have feedback on adding a way to get stat information from fam & a way to ask fam for only the first n files when monitoring a large directory.) > Raster told me he didn't see a ton of use of the ability to sort, but he > like to be able to store metadata.. of course, efm style. I told him that'd > be bad, so I suggested arbitrary metadata per file. We also agreed fam > should be capable of providing file permissions, since it's already > stat()ing the file on behalf of the process, as well as providing any other > useful information that can be obtained from stat(). Yes. (It's funny, at every layer from imon -> fam -> application, the amount of information which is discarded.) I agree, anything that fam learns from stat() should be available to its clients. Here are some random notes on adding this to the API & the protocol between fam & its clients: - I can't break binary compatibility with the existing API (so no adding members to the FAMEvent struct, changing arguments to FAMMonitorFile(), etc.), but I'm happy to add new structs & functions. Unlike the current API & protocol, whatever we add should be flexible enough that people can add things in the future without having to come up with horrible new function names like FAMOpen4(). - If you want extended events, there ought to be a way to tell fam which additional attributes you want. (If you want everything fam can get from stat(), you ought to be able to get it; but if all you want is one field, you shouldn't have to shuffle the rest of the data across the socket.) It seems reasonable to me that these settings be per-connection rather than per-request. - One potential use of the extended information is inside fam itself. When fam starts monitoring files/directories which are mounted from a remote host, it tries to ask fam on the remote machine to monitor those files (much better than polling over NFS). If the remote fam can supply all the stat info that the local fam needs, the local fam shouldn't have to stat the files. (Neat!) - Since fam clients might be across the network from fam, the stat info has to be portable. (How do we handle a client on a machine with a 32-bit off_t famming a large file on a machine with a 64-bit off_t, for example?) - As the amount of information fam provides to clients goes up, so does the risk of a buggy fam being a useful tool for hostile clients. I think fam is secure but it's one more thing to lose sleep over if you're so inclined. > His main reason against fam sorting the directory is that it couldn't > respond to the process until it read the whole directory. That's legitimate > IMHO, but I still want to find a way to do it so fam can return just the > first 15 files. Know of a way to get the fs to return it sorted, without > requiring imon? Raster suggested that you query fam at run-time for extra > features only provided by imon, i.e., the ability to get the first 15 files > alphabetically-sorted. No... & I think most (all?) fs's don't even store them sorted in an order which is useful to people; ls -1f on both xfs & ext2 gives you the files in whatever order the filesystem found most useful to store them in. I think this means that *any* process (even in kernel space) has to traverse the entire directory before giving you any portion of a sorted list. (And I believe imon doesn't do this, in case you're saying it already does!) Also, it seems like when you ask for "the first 15 files", keep in mind the kinds of filters & ordering a decent file manager will give you: sort by size, by type first & name second, by modification date, reverse, only show me *.txt, include hidden files, etc. Anything which is going to give you "the first 15 files" ought to be flexible enough to let you specify the sort criteria, file globs for filtering, and the locale. (Is there some existing library which does this? Seems like a generally useful facility.) Now, in the case where fam is looking at a 1000-file directory, a lot of traffic can be saved if it can pass back only the "first" 15 files... so this flexibility, although hard to do, might be worth the effort. (On the other hand, what's a client application going to do once it's got the first 15 files? Ask for the remaining 985, I think... But still, if the application can remain responsive while this is happening, and without simply processing n events per visit from the main select() loop, that's an improvement.) --Rusty -- Source code, list archive, and docs: http://oss.sgi.com/projects/fam/ To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com From owner-fam@oss.sgi.com Wed Aug 23 00:29:23 2000 Received: by oss.sgi.com id ; Wed, 23 Aug 2000 00:29:14 -0700 Received: from nat-dsl-161.valinux.com ([198.186.202.161]:64774 "EHLO behemoth.su.varesearch.com") by oss.sgi.com with ESMTP id ; Wed, 23 Aug 2000 00:28:51 -0700 Received: (from raster@localhost) by behemoth.su.varesearch.com (8.9.3/8.9.3) id AAA01615; Wed, 23 Aug 2000 00:34:01 -0700 Message-Id: <200008230734.AAA01615@behemoth.su.varesearch.com> Date: Wed, 23 Aug 2000 00:34:01 -0700 (PDT) From: raster@rasterman.com Reply-To: raster@rasterman.com Subject: Re: [fam] Re: fam To: rusty@sgi.com cc: rusty@rlyeh.engr.sgi.com, kempler@utdallas.edu, fam@oss.sgi.com In-Reply-To: <10008230010.ZM12865@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 23 Aug, Rusty Ballinger scribbled: -> -> > His main reason against fam sorting the directory is that it couldn't -> > respond to the process until it read the whole directory. That's legitimate -> > IMHO, but I still want to find a way to do it so fam can return just the -> > first 15 files. Know of a way to get the fs to return it sorted, without -> > requiring imon? Raster suggested that you query fam at run-time for extra -> > features only provided by imon, i.e., the ability to get the first 15 files -> > alphabetically-sorted. -> -> No... & I think most (all?) fs's don't even store them sorted in an order -> which is useful to people; ls -1f on both xfs & ext2 gives you the files in -> whatever order the filesystem found most useful to store them in. I think -> this means that *any* process (even in kernel space) has to traverse the -> entire directory before giving you any portion of a sorted list. (And I -> believe imon doesn't do this, in case you're saying it already does!) -> -> Also, it seems like when you ask for "the first 15 files", keep in mind the -> kinds of filters & ordering a decent file manager will give you: sort by -> size, by type first & name second, by modification date, reverse, only show -> me *.txt, include hidden files, etc. Anything which is going to give you -> "the first 15 files" ought to be flexible enough to let you specify the sort -> criteria, file globs for filtering, and the locale. (Is there some existing -> library which does this? Seems like a generally useful facility.) -> -> Now, in the case where fam is looking at a 1000-file directory, a lot of -> traffic can be saved if it can pass back only the "first" 15 files... so -> this flexibility, although hard to do, might be worth the effort. (On the -> other hand, what's a client application going to do once it's got the first -> 15 files? Ask for the remaining 985, I think... But still, if the -> application can remain responsive while this is happening, and without -> simply processing n events per visit from the main select() loop, that's an -> improvement.) actually i see zero use for pre-sorted files - it just puts complexity in fam that wont cover all cases - then fam has to also sit and wait till it's read all 1000 or whaetvere file sfirst then sort THEN dump to the app - no - i think it's bad. it shoudl be up to the client to figure what it wants to do with the files it gets. it can so anything it wants then and save pre-processing the list which won't save processing - it just shifts it to fam and then limits it to what fam can do. :) -- --------------- 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 Fri Aug 25 12:55:18 2000 Received: by oss.sgi.com id ; Fri, 25 Aug 2000 12:55:09 -0700 Received: from newman.bch.uc.edu ([129.137.195.205]:25948 "EHLO smtp.uc.edu") by oss.sgi.com with ESMTP id ; Fri, 25 Aug 2000 12:54:34 -0700 Received: from cicero.ra.uc.edu (t14-21.ra.uc.edu [129.137.229.77]) by smtp.uc.edu (8.9.2/8.9.2) with ESMTP id OAA19941 for ; Fri, 25 Aug 2000 14:21:34 -0400 (EDT) Received: (from ebg@localhost) by cicero.ra.uc.edu (8.9.3/8.9.3) id QAA01462 for fam@oss.sgi.com; Fri, 25 Aug 2000 16:11:36 -0400 Date: Fri, 25 Aug 2000 16:11:35 -0400 From: "E. Brian Gast" To: fam@oss.sgi.com Subject: [fam] imon patch for 2.4.0-test6 kernels Message-ID: <20000825161135.A1449@cicero.ra.uc.edu> 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 all, I've made an imon patch for the 2.4.0-test6 kernel which can be grabbed from http://www.eng.uc.edu/~egast/imon/imon-0.0.1-2.4.0-test6.gz. A few notes of disclamer: This was my first time in kernel-land, and although everything seems to be working from the (somewhat limited) testing I've done, it should probably be looked at and tested by others. Also, this is a straight move from the 2.3.42 kernel patch -- same bugs should still apply. Is anyone currently doing active development on imon? Like I said, I really don't have any kernel experience, but this has kind of got me interested... Brian -- 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 Aug 25 13:21:38 2000 Received: by oss.sgi.com id ; Fri, 25 Aug 2000 13:21:28 -0700 Received: from deliverator.sgi.com ([204.94.214.10]:64046 "EHLO deliverator.sgi.com") by oss.sgi.com with ESMTP id ; Fri, 25 Aug 2000 13:21:12 -0700 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 NAA02161 for ; Fri, 25 Aug 2000 13:12:55 -0700 (PDT) mail_from (rusty@rlyeh.engr.sgi.com) Received: (from rusty@localhost) by rlyeh.engr.sgi.com (SGI-8.9.3/8.9.3) id NAA04656; Fri, 25 Aug 2000 13:18:45 -0700 (PDT) From: "Rusty Ballinger" Message-Id: <10008251318.ZM4703@rlyeh.engr.sgi.com> Date: Fri, 25 Aug 2000 13:18:45 -0700 In-Reply-To: "E. Brian Gast" "[fam] imon patch for 2.4.0-test6 kernels" (Aug 25, 4:11pm) References: <20000825161135.A1449@cicero.ra.uc.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: gasteb@email.uc.edu Subject: Re: [fam] imon patch for 2.4.0-test6 kernels 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've made an imon patch for the 2.4.0-test6 kernel which can be grabbed from > http://www.eng.uc.edu/~egast/imon/imon-0.0.1-2.4.0-test6.gz. Great! I will add this to the download area today! > A few notes of disclamer: This was my first time in kernel-land, and although > everything seems to be working from the (somewhat limited) testing I've done, > it should probably be looked at and tested by others. Also, this is a straight > move from the 2.3.42 kernel patch -- same bugs should still apply. I doubt your disclaimers can be any more vigorous than the ones already there... > Is anyone currently doing active development on imon? Like I said, I really > don't have any kernel experience, but this has kind of got me interested... I think Mark Bowyer is doing/will do? a version for Solaris, but the Linux version has been languishing for some months. Any chance you want to rewrite the hooks into the filesystem code? :) --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 Sat Aug 26 22:09:43 2000 Received: by oss.sgi.com id ; Sat, 26 Aug 2000 22:09:33 -0700 Received: from svn.net ([167.160.200.10]:14085 "EHLO svn.net") by oss.sgi.com with ESMTP id ; Sat, 26 Aug 2000 22:09:03 -0700 Received: from wantelbos (bastian@pm3-124.svn.net [167.160.201.124]) by svn.net (8.10.0/8.10.0) with SMTP id e7R5ACM21377 for ; Sat, 26 Aug 2000 22:10:12 -0700 From: Waldo Bastian To: fam@oss.sgi.com Subject: [fam] Problems running fam as root Date: Sat, 26 Aug 2000 22:02:55 -0700 Content-Type: text/plain MIME-Version: 1.0 Message-Id: <0008262202550D.07794@wantelbos> Content-Transfer-Encoding: 8bit Sender: owner-fam@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;fam-outgoing HIya, I experience problems when using fam clients as root. I get this error: Aug 26 21:33:33 wantelbos fam[6713]: localclient chown: Operation not permitted I tried starting fam with some more debug info (fam -d) and now the problem seems to have disappeared. When I get the above problem, the client application hangs waiting for some response from the fam daemon, see backtrace: #0 0x40e05154 in __libc_read () from /lib/libc.so.6 #1 0x40d0b1d0 in FAMDebugLevel () from /usr/local/lib/libfam.so.0 #2 0x40d04d0f in FAMOpen2 (fc=0x804c910, appName=0x0) at fam.c++:80 #3 0x40d04e81 in FAMOpen (fc=0x804c910) at fam.c++:100 #4 0x4005cbf1 in KDirWatch::KDirWatch (this=0x804cb28, _freq=500) at kdirwatch.cpp:99 #5 0x400c205f in Kded::build (this=0x804ca18) at kded.cpp:79 #6 0x400c2b6f in main (argc=2, argv=0xbffff884) at kded.cpp:265 #7 0x40d89a5e in __libc_start_main (main=0x8048534
, argc=2, argv=0xbffff884, init=0x80484e0 <_init>, fini=0x804869c <_fini>, rtld_fini=0x4000aa20 <_dl_fini>, stack_end=0xbffff87c) at ../sysdeps/generic/libc-start.c:92 Cheers, Waldo -- KDE/Linux, made for people, made by people. -- Source code, list archive, and docs: http://oss.sgi.com/projects/fam/ To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com From owner-fam@oss.sgi.com Sun Aug 27 17:29:10 2000 Received: by oss.sgi.com id ; Sun, 27 Aug 2000 17:28:59 -0700 Received: from deliverator.sgi.com ([204.94.214.10]:33875 "EHLO deliverator.sgi.com") by oss.sgi.com with ESMTP id ; Sun, 27 Aug 2000 17:28:33 -0700 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 RAA27113 for ; Sun, 27 Aug 2000 17:20:15 -0700 (PDT) mail_from (rusty@rlyeh.engr.sgi.com) Received: from rlyeh.engr.sgi.com ([163.154.5.94]) by nodin.corp.sgi.com (980427.SGI.8.8.8/980728.SGI.AUTOCF) via ESMTP id RAA98238 for ; Sun, 27 Aug 2000 17:26:07 -0700 (PDT) Received: (from rusty@localhost) by rlyeh.engr.sgi.com (SGI-8.9.3/8.9.3) id RAA20447; Sun, 27 Aug 2000 17:22:57 -0700 (PDT) From: "Rusty Ballinger" Message-Id: <10008271722.ZM20493@rlyeh.engr.sgi.com> Date: Sun, 27 Aug 2000 17:22:56 -0700 In-Reply-To: Waldo Bastian "[fam] Problems running fam as root" (Aug 26, 10:02pm) References: <0008262202550D.07794@wantelbos> 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: bastian@kde.org Subject: Re: [fam] Problems running fam as root 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 experience problems when using fam clients as root. I get this error: > > Aug 26 21:33:33 wantelbos fam[6713]: localclient chown: Operation not > permitted Hey, this is interesting. It looks like this happens when a non-root client starts first, and is polling files, and then a root client connects. There's only one place where fam does a chown--when it's creating the UNIX domain socket for communication with a local client. (If it bails while doing that, that probably explains why the client is hanging on a read.) This makes me think fam is still running as the first client's UID when creating the socket, which is horribly wrong. I am about three months behind on putting out a version which incorporates Christian Kreibich's patch for building fam on Solaris, so maybe I will finish that this week & fix this bug while I'm at it. Thanks for reporting this. > I tried starting fam with some more debug info (fam -d) and now the problem > seems to have disappeared. (The problem doesn't seem to happen when only the root client is running, so that might be what happened when you took a closer look.) --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 Sun Aug 27 19:57:50 2000 Received: by oss.sgi.com id ; Sun, 27 Aug 2000 19:57:40 -0700 Received: from newman.bch.uc.edu ([129.137.195.205]:8012 "EHLO smtp.uc.edu") by oss.sgi.com with ESMTP id ; Sun, 27 Aug 2000 19:57:12 -0700 Received: from cicero.ra.uc.edu (t07-06.ra.uc.edu [129.137.228.150]) by smtp.uc.edu (8.9.2/8.9.2) with ESMTP id VAA17753; Sun, 27 Aug 2000 21:24:10 -0400 (EDT) Received: (from ebg@localhost) by cicero.ra.uc.edu (8.9.3/8.9.3) id XAA03509; Sun, 27 Aug 2000 23:14:12 -0400 Date: Sun, 27 Aug 2000 23:13:56 -0400 From: "E. Brian Gast" To: rusty@sgi.com Cc: fam@oss.sgi.com Subject: Re: [fam] imon patch for 2.4.0-test6 kernels Message-ID: <20000827231356.A3470@cicero.ra.uc.edu> Mail-Followup-To: rusty@sgi.com, fam@oss.sgi.com References: <20000825161135.A1449@cicero.ra.uc.edu> <10008251318.ZM4703@rlyeh.engr.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <10008251318.ZM4703@rlyeh.engr.sgi.com>; from rusty@rlyeh.engr.sgi.com on Fri, Aug 25, 2000 at 01:18:45PM -0700 Sender: owner-fam@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;fam-outgoing On Fri, Aug 25, 2000 at 01:18:45PM -0700, Rusty Ballinger wrote: > > > Is anyone currently doing active development on imon? Like I said, I really > > don't have any kernel experience, but this has kind of got me interested... > > I think Mark Bowyer is doing/will do? a version for Solaris, but the Linux > version has been languishing for some months. Any chance you want to rewrite > the hooks into the filesystem code? :) Well, I spent some time this weekend looking through things, and I think I've found a good reason to learn more about the Linux kernel. There are some more areas that I need to research first, such as wrapfs, and then I'll send a message to the list asking for comments on possible designs. I guess one of the most important things is making imon acceptable for inclusion into the main kernel? Also, the 2.4.0-test6 patch does work on -test7. Brian -- Source code, list archive, and docs: http://oss.sgi.com/projects/fam/ To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com From owner-fam@oss.sgi.com Sun Aug 27 21:08:10 2000 Received: by oss.sgi.com id ; Sun, 27 Aug 2000 21:08:01 -0700 Received: from svn.net ([167.160.200.10]:5903 "EHLO svn.net") by oss.sgi.com with ESMTP id ; Sun, 27 Aug 2000 21:07:26 -0700 Received: from wantelbos (bastian@pm3-154.svn.net [167.160.201.154]) by svn.net (8.10.0/8.10.0) with SMTP id e7S48oM13577; Sun, 27 Aug 2000 21:08:50 -0700 From: Waldo Bastian To: rusty@sgi.com Subject: Re: [fam] Problems running fam as root Date: Sun, 27 Aug 2000 21:01:23 -0700 Content-Type: text/plain Cc: fam@oss.sgi.com References: <0008262202550D.07794@wantelbos> <10008271722.ZM20493@rlyeh.engr.sgi.com> In-Reply-To: <10008271722.ZM20493@rlyeh.engr.sgi.com> MIME-Version: 1.0 Message-Id: <00082721012305.00969@wantelbos> Content-Transfer-Encoding: 8bit Sender: owner-fam@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;fam-outgoing On Sun, 27 Aug 2000, Rusty Ballinger wrote: > > I experience problems when using fam clients as root. I get this error: > > > > Aug 26 21:33:33 wantelbos fam[6713]: localclient chown: Operation not > > permitted > > Hey, this is interesting. It looks like this happens when a non-root > client starts first, and is polling files, and then a root client connects. > There's only one place where fam does a chown--when it's creating the UNIX > domain socket for communication with a local client. (If it bails while > doing that, that probably explains why the client is hanging on a read.) > This makes me think fam is still running as the first client's UID when > creating the socket, which is horribly wrong. Yup, that seems to be in line with the behaviour I've seen. Cheers, Waldo -- KDE/Linux, made for people, made by people. -- Source code, list archive, and docs: http://oss.sgi.com/projects/fam/ To unsubscribe: echo unsubscribe fam | mail majordomo@oss.sgi.com