From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 19 Apr 2005 08:52:05 -0600 From: "Ronald G. Minnich" To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Subject: Re: [SPAM] [9fans] watch command In-Reply-To: <1573.24.6.25.223.1113912237.squirrel@www.infernopark.com> Message-ID: References: <1573.24.6.25.223.1113912237.squirrel@www.infernopark.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Topicbox-Message-UUID: 3d4f53b0-ead0-11e9-9d60-3106f5b1d025 On Tue, 19 Apr 2005 vdharani@infernopark.com wrote: > > > > Whenever a.c and b.c are changed, a text will appear on the ctl file. > > Thus, you can do something like: > > % while(){read /n/watch/ctl; mk} > > > i dont think it will work. > > let us say i just saved an intermediate version of a.c while doing a > bigger change. then the above script will kick mk process that is neither > needed nor useful. the same is the case when i save a.c but i need to > change 10 other files to reflect the change in all relevant files. > the specific example may not be useful but ... you have no idea how many times people want this stuff. But what about a file that the server can provide that provides info about metadata changes, i.e. you are reading a /srv/fsstatus and as things change you get twstat messages? ron