Path: utzoo!attcan!uunet!wuarchive!usc!ucsd!ucbvax!ENG.UMD.EDU!ziegast From: ziegast@ENG.UMD.EDU (Eric Ziegast) Newsgroups: comp.mail.mh Subject: Re: xbiff with automagic-incing Message-ID: <9010272052.AA14483@moria.eng.umd.edu> Date: 27 Oct 90 20:52:04 GMT References: <9010261417.AA21847@rodan.acs.syr.edu> Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 22 Jerry Peek writes: >Darin McGrew wrote: >> In article <72800001@uxa.cso.uiuc.edu> mark@uxa.cso.uiuc.edu writes: >> >Anyone out there care to share with me how you would use xbiff to >> >monitor ~/mail/mh/1, to consider it true? If the file dne, my xbiff >> >breaks down and never shows up (I guess it wants a file of length 0??) > >One easy thing to check is the inbox folder itself. In other words, check >the directory file //Mail/inbox. If a new message is >added to the folder, the directory file itself will be modified. I find out that xbiff may not work in the future using the method I used and the one Jerry describes above. According to our local X guru, there are two versions of xbiff. The first version only checks to see if the file size changes, or if the file is cleared. The newer version does checking which is more specific to /usr/ucb/Mail format. I found this out when I tried using "xbiff -file ~/Mail/inbox/1" on two different systems, and one worked while the other didn't. ________________________________________________________________________ Eric W. Ziegast, University of Merryland, Engineering Computing Services ziegast@eng.umd.edu - Eric@[301.405.3689]